Cogent Eastbound route out of Portland to Boise and a new POP
It would appear that Cogent finally has a long-awaited route Eastbound out of Portland. I just noticed it on their web site today and a quick traceroute confirms there is now connectivity to Boise.
INET-A#traceroute ccr01.boi01.atlas.cogentco.comTranslating “ccr01.boi01.atlas.cogentco.com”…domain server (xx.xx.xx.xx) [OK]Type escape sequence to abort.Tracing the route to lo0.ccr01.boi01.atlas.cogentco.com (66.28.1.10)1 gi1-xx.10xx.ccr01.pdx01.atlas.cogentco.com (38.104.104.xx) [AS 174] 0 msec 1 msec 0 msec2 te4-2.ccr01.pdx02.atlas.cogentco.com (154.54.0.86) [AS 174] 0 msec 1 msec 1 msec3 te7-3.ccr01.boi01.atlas.cogentco.com (154.54.40.102) [AS 174] 11 msecte4-3.ccr01.boi01.atlas.cogentco.com (154.54.40.98) [AS 174] 12 msec *INET-A#
I then noticed that traffic Eastbound beyond Boise to Salt Lake still prefers going through Sacramento.
INET-A#traceroute ccr01.slc01.atlas.cogentco.comTranslating “ccr01.slc01.atlas.cogentco.com”…domain server (xx.xx.xx.xx) [OK]Type escape sequence to abort.Tracing the route to lo0.ccr01.slc01.atlas.cogentco.com (66.28.1.114)1 gi1-xx.10xx.ccr01.pdx01.atlas.cogentco.com (38.104.104.xx) [AS 174] 1 msec 1 msec 0 msec2 te4-2.ccr01.pdx02.atlas.cogentco.com (154.54.0.86) [AS 174] 0 msec 1 msec 1 msec3 te3-4.ccr01.smf01.atlas.cogentco.com (154.54.40.109) [AS 174] 12 msecte4-3.ccr01.smf01.atlas.cogentco.com (154.54.40.113) [AS 174] 13 msec 12 msec4 te3-3.ccr01.slc01.atlas.cogentco.com (66.28.4.193) [AS 174] 25 msecte4-1.ccr01.slc01.atlas.cogentco.com (154.54.1.102) [AS 174] 25 msec *INET-A#
Further investigation using Cogent’s looking glass tool from Washington DC shows me that either their network map is incorrect, or they currently have a circuit down from Boise to Salt Lake (or for some weird traffic engineering reason my traceroutes are not hitting it). Routing from DC to Boise through PDX is not exactly what I would consider “optimal”. 😉
Looking Glass Results: Washington, DCQuery: traceAddr: 66.28.1.10trace 66.28.1.10Type escape sequence to abort.Tracing the route to lo0.ccr01.boi01.atlas.cogentco.com (66.28.1.10)1 fa0-8.na01.b005944-0.dca01.atlas.cogentco.com (66.250.56.189) 4 msec 4 msec 4 msec2 vl3507.mpd03.dca01.atlas.cogentco.com (66.28.67.225) 4 msec 4 msec 0 msec3 te0-3-0-0.ccr21.dca01.atlas.cogentco.com (154.54.40.61) 0 msec 0 msec 4 msec4 te0-2-0-4.ccr21.ord01.atlas.cogentco.com (154.54.40.194) 28 msecte0-1-0-4.ccr21.ord01.atlas.cogentco.com (154.54.40.190) 20 msecte0-2-0-4.ccr21.ord01.atlas.cogentco.com (154.54.40.194) 24 msec5 te0-0-0-3.ccr21.mci01.atlas.cogentco.com (154.54.2.217) 32 msecte0-2-0-7.ccr21.ord01.atlas.cogentco.com (154.54.29.102) 32 msec 32 msec6 te4-4.mpd02.den01.atlas.cogentco.com (154.54.7.130) 48 msecte0-3-0-0.ccr21.mci01.atlas.cogentco.com (154.54.7.185) 44 msec 44 msec7 te4-4.mpd02.den01.atlas.cogentco.com (154.54.7.130) 56 msecte3-2.ccr01.slc01.atlas.cogentco.com (154.54.3.14) 60 msec 64 msec8 te3-2.ccr01.slc01.atlas.cogentco.com (154.54.3.14) 64 msecte7-3.ccr01.smf01.atlas.cogentco.com (66.28.4.194) 72 msecte4-2.ccr01.smf01.atlas.cogentco.com (154.54.1.101) 76 msec9 te7-3.ccr01.smf01.atlas.cogentco.com (66.28.4.194) 100 msec 80 msec 80 msec10 te3-3.ccr01.pdx02.atlas.cogentco.com (154.54.40.110) 84 msecte4-3.ccr01.pdx02.atlas.cogentco.com (154.54.40.114) 84 msec 84 msec11 te4-3.ccr01.boi01.atlas.cogentco.com (154.54.40.98) 96 msec *te7-3.ccr01.boi01.atlas.cogentco.com (154.54.40.102) 92 msec
Cogent has talked about an Eastbound route for some time now so I am jazzed to see it is finally happening! Here is to hoping that Boise <-> Salt Lake link comes online very soon!
Whoh, hold the phone- I just noticed that my route to Boise is going the ccr01.PDX02.atlas.cogentco.com. That’s new! Previously they only had a single router in Portland in the Pittock building. A quick check of their POP list in Portland reveals that they are saying 707 SW Washington St is a POP which is the Bank of California building. That’s even better news as they are now one of (or perhaps the only?) carrier that has multiple routes out of town with core routers in multiple facilities. I can’t say that I know for sure of any carrier in town with core routers in more than one facility.
-Eric
Then you get silly stuff like this. hop 18 here is in the next cabinet to me.
5. gi1-2.ccr01.pdx01.atlas.cogentco.com 0.0% 5 1.1 13.1 1.0 61.3 26.9
6. te4-2.ccr01.pdx02.atlas.cogentco.com 0.0% 5 1.2 1.2 1.1 1.2 0.0
7. te3-4.ccr01.smf01.atlas.cogentco.com 0.0% 5 12.8 12.8 12.7 12.8 0.0
8. te4-2.ccr01.oak01.atlas.cogentco.com 0.0% 5 15.1 24.8 15.1 63.0 21.3
9. te0-0-0-5.mpd22.sfo01.atlas.cogentco.com 0.0% 5 16.2 16.1 16.1 16.2 0.0
10. te9-4.mpd01.sjc01.atlas.cogentco.com 0.0% 4 17.6 64.0 17.1 204.3 93.5
11. te8-1.mpd01.sjc03.atlas.cogentco.com 0.0% 4 17.6 17.7 17.6 17.7 0.1
12. te-3-3.car3.SanJose1.Level3.net 0.0% 4 17.4 18.3 17.3 20.5 1.5
13. vlan60.csw1.SanJose1.Level3.net 0.0% 4 18.0 17.6 17.3 18.0 0.4
14. 4.69.153.17 0.0% 4 17.2 17.3 17.2 17.6 0.2
15. ae-7-7.ebr1.Seattle1.Level3.net 0.0% 4 36.9 38.1 35.7 42.2 2.8
16. ae-11-51.car1.Seattle1.Level3.net 0.0% 4 34.8 34.8 34.6 35.2 0.2
17. 4.53.150.46 0.0% 4 23.8 23.7 23.7 23.8 0.1
18. corv-car1-gw.nero.net 0.0% 4 25.5 26.1 25.4 27.9 1.2
19. ob1.oregonstate.edu 0.0% 4 27.0 26.6 26.4 27.0 0.3
20. crt1.oregonstate.edu 0.0% 4 26.3 26.6 26.3 27.2 0.4
21. drt2.oregonstate.edu 0.0% 4 27.0 26.5 26.2 27.0 0.4
22. http://www.orst.edu
@Bill Blackford
oops. No this trace doesn’t come back through the Pittock. My mistake. Unless that 4.x address is the Level3-facing interface on NERO’s Pittock box.
Eric –
I think you may be a bit off on this one, I think they may actually only have one IP POP now, every traceroute I have tried as of now goes through pdx02 and not pdx01. I think they just stuck pdx01 on the end of the stick that is a new main pop of PDX02. sea02 is the same way, it is just a stub from sea01 that has all the long-haul (both SEA01 and SEA02 are in the westin building though).