5Did the following command on one of my Australian VPS this morning.
$ mtr -n --report www.aussiehq.com.au HOST: my-vps-in-bne Loss% Snt Last Avg Best Wrst StDev 1. 202.60.89.xx 0.0% 10 0.0 0.0 0.0 0.1 0.0 2. 118.127.9.xx 0.0% 10 267.6 262.3 256.3 267.6 4.3 3. 202.60.84.78 0.0% 10 270.8 265.5 258.5 275.2 5.4 4. 203.88.112.4 0.0% 10 274.9 268.7 262.4 274.9 4.1 5. 203.88.112.153 10.0% 10 271.8 268.0 262.8 271.8 3.1
My VPS is hosted with someone who has servers with DedicatedServers.com.au in Brisbane, doing a traceroute to the home page of AussieHQ in Canberra, one of the largest hosting companies in Australia. I believe the first hop is the host node for thise OpenVZ VE, and the second hop would be the router at DedicatedServers.
It’s interesting to observe the fluctuation of latency between the host node and the router throughout the day. It’s usually pretty bad in the morning — all the way up to 300ms, and then the round-trip latency drops to a few milliseconds in the evenings. Massively oversold bandwidth I guess (won’t name the names yet). Even my sites hosted in California feels faster in Australia.
That’s pretty awful congestion, yuk.
Uber bandwidth limits are no good if you can’t use it :-)
Yes. Overselling bandwidth is bad regardless whether it’s in US or in Australia. However I am surprised that there’s any overselling on the first hop between the host computer and the next router in the loop — inside an Australian DC. You probably know more about this than I do. I am just trying to point out that the argument “host in Australia for low latency” is mute, if the pipe is congested.
I’m doubtful that it’s between the VE host and the first router considering it should be 100mbps.
Although if someone bought colo with a fixed pipe, say 10m/bits and the pipe is full, then it could look like that.
What’s the inbound or reverse traceroute look like?
Here’s the reverse traceback from my home ADSL connect (Exetel, Sydney POP).
(6) to (7) would be from Sydney to Brisbane. (9) is my VPS. The latency looks pretty similar from this view.
Doesn’t look good. Still, it does look to be specific to a local LAN/VLAN or host as opposed to a wider issue with the DC etc.