"Premium bandwidth" which AWS/Amazon markets to less understanding developers is almost a scam. By now, software developers think data centers, ISPs and others part of the peering on the internet pay per GB transferred, because all the clouds charge them like that.

▲

plantain 12 hours ago | parent | next [-]

Try a single threaded download from Hetzner Finland versus eu-north-1 to a remote (i.e. Australia) destination and you'll see premium bandwidth is very real. Google Cloud Storage significantly more so than AWS.

Sure you can just ram more connections through the lossy links from budget providers or use obscure protocols, but there's a real difference.

Whether it's fairly priced, I suspect not.

	▲	abigail95 8 hours ago \| parent \| next [-]
		I just tested it and TCP gets the maximum expected value given the bandwidth delay product from a server in Falkenstein to my home in Australia, from 124 megabits on macOS to 940 megabits on Linux. Can you share your tuning parameters on each host? If you aren't doing exactly the same thing on AWS as you are on Hetzner you will see different results. Bypassing the TCP issue I can see nothing indicating low network quality, a single UDP iperf3 pass maintains line rate speed without issue. Edit: My ISP peers with Hetzner, as do many others. If you think it's "lossy" I'm sure someone in network ops would want to know about it. If you're getting random packet loss across two networks you can have someone look into it on both ends.
	▲	Hikikomori 3 hours ago \| parent \| prev \| next [-]
		AWS like most do hot potato routing, not so premium when it exits instantly. This is usually a tcp tuning problem rather than bandwidth being premium.
	▲	12 hours ago \| parent \| prev [-]
		[deleted]

▲

Hikikomori 4 hours ago | parent | prev [-]

I mean transit is usually billed like that, or rather a commit.