3 ms·
> That's fine. Since the problem isn't last-mile, but interconnection, the per-GB cost is miniscule. I'll estimate $0.025/GB, but that's way too high, just to a
by tzs 13y ago
> That's fine. Since the problem isn't last-mile, but interconnection, the per-GB cost is miniscule. I'll estimate $0.025/GB, but that's way too high, just to avoid getting to the point where one might realistically quibble over the real cost.
That's half the per-GB cost that Amazon and Microsoft charge for S3 and Azure transfers to the internet for those customers using the highest volume below the "call for pricing" level, and so get the lowest published rate. I don't offhand see any reason to expect Amazon and S3 to be paying more for bandwidth than last-mile providers do, nor for them to be marking it up to their customers more. Are you sure $0.025/GB is too high?
- nknighthb 13y agoVery, very sure. I can pay far, far less than AWS and Microsoft charge for bandwidth in any US datacenter managing my own equipment. Meanwhile, HN-darling Digital Ocean charges their VPS customers just $0.02/GB on overage. That's right, for overage above the 1-9TB they include with their plans, DO charges less than I'm estimating the cost to be for massive providers to exchange traffic at far larger and more cost-effective scales. Linode charges $0.10/GB, and that's still less than AWS charges for the first 10TB. And again, that's after the 3-20(!)TB Linode's plans include in the base cost. Bandwidth is cheap. The US has all the fiber capacity between POPs that it needs. Adding or upgrading interconnects between Comcast and Cogent/Level3/whoever is not laying fiber across the countryside, it's buying switches or turning on ports and running cables from one cage in a datacenter to another cage in the same friggin' datacenter.