I'd called tech support earlier, but the gentleman that I spoke with wasn't able to provide any information or was willing to create a ticket for this.
WITHIN the Shaw network, I've got 200ms ping times.
The Shaw rep I spoke with tells me that that's an acceptable ping time and that there's nothing that can be done. I have a static IP, and those get subject to different routing rules in Alberta, and as a result my ping times are higher than if I had I dynamic IP.
What brought this to my attention this morning was trying to access one of our servers in Amsterdam, and it was *really* slow. Negligible packet loss, but high latency.
Pulled up "mtr" and "traceroute" to see what was going on, and was surprised to see that I'm 190-200ms before I even leave the Shaw network. 200ms from Vancouver Island, to Edmonton. What the hell?
traceroute to host.nl.howlingfrog.com (220.127.116.11), 30 hops max, 60 byte packets
1 * * *
2 rd1bb-tge0-2-0-0-29.no.shawcable.net (18.104.22.168) 14.746 ms 14.849 ms 14.873 ms
3 rc2bb-tge0-5-0-11.vc.shawcable.net (22.214.171.124) 20.543 ms 20.582 ms 20.705 ms
4 rc2wh-tge0-14-0-10.vc.shawcable.net (126.96.36.199) 27.814 ms 27.904 ms 27.931 ms
5 rc2so-tge0-9-1-0.cg.shawcable.net (188.8.131.52) 36.022 ms 36.053 ms 36.145 ms
6 184.108.40.206 (220.127.116.11) 51.556 ms 44.601 ms 44.805 ms
7 18.104.22.168 (22.214.171.124) 79.697 ms 77.769 ms 77.816 ms
8 rc3so-tge0-11-0-17.cg.shawcable.net (126.96.36.199) 113.830 ms 105.222 ms 111.696 ms
9 rc3ar-tge0-6-0-12.ed.shawcable.net (188.8.131.52) 200.769 ms 192.641 ms 192.693 ms
10 ams-ix.ae1.cr1.ams2.nl.nlayer.net (184.108.40.206) 191.402 ms 190.494 ms 190.822 ms
11 as46652.ae4-1932.ar2.ams2.nl.nlayer.net (220.127.116.11) 192.448 ms 191.058 ms 203.605 ms
12 * * *
13 * * *
... (we have pings firewalled out on the server)
I've done multiple traceroutes this morning, and this one showed the least amount of bouncing around inside of the Shaw network. Other traceroutes showed paths of "Nanaimo -> Vancouver -> Calgary -> Edmonton -> New York -> Calgary -> Edmonton -> Amsterdam".
One thing I have been able to determine is that the paths that get the *worst* routing within Shaw, are the ones that connect to "nlayer.net" over in Amsterdam. When I connect to other servers we have at the same facility and we get routed through "telia.net", I'm at ~30ms within the Shaw network, and rarely over 150ms to the final destination.
So... someone from Shaw please explain to me... how is "200ms *within* the Shaw network" considered reasonable?
When I've spoken to techs at Shaw Business Support in the past they'd advised me to contact them if I ever saw it take more than 100ms to leave the Shaw network, and here I have someone today on the phone telling me that 200ms is acceptable and that I should just lump it.