mikeyur

Shaw/Cogent Routing Nightmare. Chicago and back, every time.

Discussion created by mikeyur on Oct 4, 2016
Latest reply on Oct 19, 2016 by tbjeff

Arggh. Another month, another west coast routing issue. This time with Cogent.

 

Any traffic going to/from Cogent on the west coast takes a nice trip through Chicago. I contacted my hosting provider in Seattle to address this with Cogent and here's the response they received:

 

"Cogent is routing to this (24.85.xxx.xxx) to Shaw in Chicago, because it is the best route Cogent is learning for 24.84.0.0/14.
Cogent can not change the routing for 24.84.0.0/14, because that IP (24.85.xxx.xxx) is not a Cogent IP address."

 

Quick look at the Cogent looking glass for Seattle and this is the route you get:

 

 

traceroute to 24.85.xxx.xxx (24.85.xxx.xxx), 30 hops max, 60 byte packets
1 gi0-0-0-19.3.agr11.sea01.atlas.cogentco.com (66.250.250.57) 1.029 ms 1.032 ms
2 te0-3-0-4.ccr21.sea01.atlas.cogentco.com (154.54.0.89) 0.645 ms 0.664 ms
3 be2084.ccr21.sea02.atlas.cogentco.com (154.54.0.254) 0.964 ms 0.938 ms
4 be2085.ccr21.slc01.atlas.cogentco.com (154.54.2.198) 21.181 ms 21.151 ms
5 be3038.ccr22.den01.atlas.cogentco.com (154.54.42.98) 31.271 ms be3037.ccr21.den01.atlas.cogentco.com (154.54.41.146) 31.781 ms
6 be3035.ccr21.mci01.atlas.cogentco.com (154.54.5.90) 42.696 ms be3036.ccr22.mci01.atlas.cogentco.com (154.54.31.90) 42.845 ms
7 be2832.ccr42.ord01.atlas.cogentco.com (154.54.44.170) 55.069 ms be2831.ccr41.ord01.atlas.cogentco.com (154.54.42.166) 54.630 ms
8 be2766.ccr41.ord03.atlas.cogentco.com (154.54.46.178) 54.857 ms be2765.ccr41.ord03.atlas.cogentco.com (154.54.45.18) 54.908 ms
9 38.88.205.10 (38.88.205.10) 53.233 ms 53.233 ms
10 rc3ec-be6-1.il.shawcable.net (66.163.65.69) 53.183 ms rc3ec-hge0-19-0-0.il.shawcable.net (66.163.65.113) 53.257 ms
11 rc3no-be13.cg.shawcable.net (66.163.75.65) 63.279 ms 63.227 ms
12 rc1st-be11-1.vc.shawcable.net (66.163.72.70) 50.853 ms 61.827 ms
13 dx2rh-te0-1-0-s1.vc.int.shawcable.net (64.59.148.126) 60.327 ms 60.503 ms
14 * *

 

The reverse gets you something like this (server hosted in SEA) - [happy to share the IPs via private message]:

 

traceroute to xxx.xxx.xx.xx (xxx.xxx.xx.xx), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 8.833 ms 8.776 ms 10.302 ms
2 10.65.64.1 (10.65.64.1) 32.195 ms 36.682 ms 24.139 ms
3 rc1bb-tge0-9-0-6-1.vc.shawcable.net (64.59.148.121) 25.815 ms 29.396 ms 15.526 ms
4 rc1wt-be90.wa.shawcable.net (66.163.76.66) 25.857 ms 28.018 ms 20.057 ms
5 be4476.ccr21.sea02.atlas.cogentco.com (38.88.252.161) 89.867 ms 80.700 ms 78.749 ms
6 xx.xx.xx.xx (xx.xx.xx.xx) 89.804 ms 85.199 ms 81.384 ms
7 xxx.xxx.xx.xx (xxx.xxx.xx.xx) 88.473 ms 89.691 ms 89.760 ms

 

 

I have another server within Vancouver with a provider who uses Cogent for transit, and the route is the same as the looking glass, except a couple extra hops for the initial Vancouver to Seattle route.

Outcomes