dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
24
share rss forum feed

TheMG
Premium
join:2007-09-04
Canada
kudos:3
Reviews:
·NorthWest Tel

1 edit
reply to firstness

Re: [AB] Telus routing Edmonton-Seattle traffic through Chicago

I've noticed this in Alberta too. It seems all traffic from Telus in Alberta gets routed through Chicago for whatever reason.

Example (these traces were done from the Telus connection at my parent's house in Grande Prairie, Alberta):

Tracing route to seattle.voip.ms [69.147.236.82]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  192.168.1.254
  2    18 ms     6 ms    14 ms  10.145.238.1
  3    59 ms    59 ms    59 ms  CHCGILDTGR01.bb.telus.com [154.11.13.186]
  4    54 ms    57 ms    56 ms  173.182.200.66
  5    65 ms    71 ms    71 ms  69.174.121.89
  6    68 ms    71 ms    71 ms  69.174.120.146
  7   110 ms   107 ms   107 ms  te0-1.cr1.sea1.us.packetexchange.net [69.174.120.21]
  8   103 ms   112 ms   103 ms  72.37.232.234
  9   104 ms   102 ms   103 ms  69.147.236.82.rdns.ubiquityservers.com [69.147.236.82]
 
Trace complete.
 

And another...
Tracing route to c-208-146-44-143.managed-ded.premium-seattle.nfoservers.com [208.146.44.143]
over a maximum of 30 hops:
 
  1     1 ms    <1 ms    <1 ms  192.168.1.254
  2    11 ms     7 ms     7 ms  10.145.238.1
  3    61 ms    53 ms    52 ms  chcgildtgr00.bb.telus.com [154.11.11.34]
  4    46 ms    46 ms    46 ms  173.182.200.2
  5    53 ms    53 ms    53 ms  te0-2-0-1.ccr22.ord01.atlas.cogentco.com [154.54.29.21]
  6    58 ms    58 ms    59 ms  te0-1-0-3.ccr22.mci01.atlas.cogentco.com [154.54.5.173]
  7    70 ms    70 ms    70 ms  te2-7.ccr02.den01.atlas.cogentco.com [154.54.87.93]
  8    81 ms    81 ms    81 ms  te0-1-0-1.ccr21.slc01.atlas.cogentco.com [154.54.3.14]
  9   109 ms   109 ms   109 ms  te4-6.ccr02.sea01.atlas.cogentco.com [154.54.80.9]
 10   103 ms   102 ms   102 ms  te4-2.ccr01.sea03.atlas.cogentco.com [154.54.41.146]
 11   106 ms   105 ms   105 ms  Internap-Network-Services.demarc.cogentco.com [38.104.124.82]
 12    98 ms   103 ms   107 ms  border9.t8-1-bbnet2.sef.pnap.net [63.251.160.83]
 13   104 ms   109 ms   105 ms  c-208-146-44-143.managed-ded.premium-seattle.nfoservers.com [208.146.44.143]
 
Trace complete.
 

Like, WTF? It's not like Telus doesn't have a network towards the west. Network map below is straight from Telus website (»about.telus.com/community/englis···_network ):



So what is it with Seattle-bound traffic from Alberta being routed through Chicago? Doesn't make any sense at all.

34764170

join:2007-09-06
Etobicoke, ON

said by TheMG:

Like, WTF? It's not like Telus doesn't have a network towards the west. Network map below is straight from Telus website

So what is it with Seattle-bound traffic from Alberta being routed through Chicago? Doesn't make any sense at all.

The map is an indication of where they have fibre, where they interconnect with other carriers to exchange wireline/wireless voice traffic, etc. but isn't an indication as to how and where they peer with their IP transit network. Telus' has extremely limited peering in Seattle and only does private peering. They don't have any public peering in Seattle as they do in Chicago, New York and San Jose. That results in some pretty awful routes going to networks on the west coast.