Traceroute to blizzard: home modem to shaw calgary IP slower than calgary IP to washington?!?

[sesopenko]

I ran a traceroute to blizzard and checked the geolocation of the IP addresses along the way and I'm seeing something strange.

I'm acquiring 30ms of latency from my calgary modem to a calgary shaw ip (up to 66.163.76.9) but then going all of the way from Calgary to Washington, only 1ms is added to the connection.  How come I'm acquiring 30ms of latency before I even leave the city but going all of the way from Calgary to Washington takes only 1ms? The gateway for my IP address adds a whole 10ms before I even get out of the local subnet of my internet connection.

Can anybody look into this?  There's something fishy going on here.

C:\Users\sesop>tracert us.patch.battle.net

Tracing route to us.patch.battle.net [137.221.106.19]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.10.1
2 9 ms 10 ms 8 ms 70.77.96.1
3 11 ms 12 ms 10 ms rc3so-be117-1.cg.shawcable.net [64.59.134.169]
4 31 ms 31 ms 31 ms rc1wt-be82.wa.shawcable.net [66.163.76.9]
5 30 ms 32 ms 30 ms rc6wt-tge0-10-0-10.wa.shawcable.net [66.163.68.66]
6 96 ms 90 ms 61 ms ae1-br01-eqse2.as57976.net [137.221.73.33]
7 63 ms 98 ms 70 ms xe-0-0-0-1-br01-eqsv5.as57976.net [137.221.65.40]
8 61 ms 61 ms 61 ms et-0-0-29-br02-eqsv5.as57976.net [137.221.65.117]
9 61 ms 61 ms 71 ms xe-0-0-1-1-br02-eqla1.as57976.net [137.221.65.6]
10 62 ms 61 ms 71 ms et-0-0-29-br01-eqla1.as57976.net [137.221.65.0]
11 64 ms 63 ms 65 ms et-0-0-2-br01-swlv10.as57976.net [137.221.65.69]
12 61 ms 60 ms 60 ms et-0-0-0-pe04-swlv10.as57976.net [137.221.83.87]
13 61 ms 61 ms 61 ms las-swlv10-ia-bons-04.as57976.net [137.221.66.23]
14 61 ms 61 ms 60 ms 137.221.105.15
15 61 ms 61 ms 60 ms 137.221.106.19

[mdk]

> Calgary to Washington

That is Washington State, not Washington, District of Columbia.

I see similar "slow" PiNG responses to the first Shaw router in my city:

  2    21 ms    10 ms     8 ms  96.54.224.1

but no increase in latency when crossing the border into the IP-address that you referenced:

  5    12 ms    13 ms    11 ms  rc1wt-be82.wa.shawcable.net [66.163.76.9]

Note that PING and TRACEROUTE IP-packets can be classified (by the Shaw routers) as being "low-priority" or "noise" traffic, rather than actual "customer" packets. To prevent possible "denial of service" attacks, some routers are programmed to NOT respond to PING / TRACEROUTE.