bitplumber.net

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.com

Translating “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 msec

2 te4-2.ccr01.pdx02.atlas.cogentco.com (154.54.0.86) [AS 174] 0 msec 1 msec 1 msec

3 te7-3.ccr01.boi01.atlas.cogentco.com (154.54.40.102) [AS 174] 11 msec

te4-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.com

Translating “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 msec

2 te4-2.ccr01.pdx02.atlas.cogentco.com (154.54.0.86) [AS 174] 0 msec 1 msec 1 msec

3 te3-4.ccr01.smf01.atlas.cogentco.com (154.54.40.109) [AS 174] 12 msec

te4-3.ccr01.smf01.atlas.cogentco.com (154.54.40.113) [AS 174] 13 msec 12 msec

4 te3-3.ccr01.slc01.atlas.cogentco.com (66.28.4.193) [AS 174] 25 msec

te4-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, DC

Query: trace

Addr: 66.28.1.10

trace 66.28.1.10

Type 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 msec

2 vl3507.mpd03.dca01.atlas.cogentco.com (66.28.67.225) 4 msec 4 msec 0 msec

3 te0-3-0-0.ccr21.dca01.atlas.cogentco.com (154.54.40.61) 0 msec 0 msec 4 msec

4 te0-2-0-4.ccr21.ord01.atlas.cogentco.com (154.54.40.194) 28 msec

te0-1-0-4.ccr21.ord01.atlas.cogentco.com (154.54.40.190) 20 msec

te0-2-0-4.ccr21.ord01.atlas.cogentco.com (154.54.40.194) 24 msec

5 te0-0-0-3.ccr21.mci01.atlas.cogentco.com (154.54.2.217) 32 msec

te0-2-0-7.ccr21.ord01.atlas.cogentco.com (154.54.29.102) 32 msec 32 msec

6 te4-4.mpd02.den01.atlas.cogentco.com (154.54.7.130) 48 msec

te0-3-0-0.ccr21.mci01.atlas.cogentco.com (154.54.7.185) 44 msec 44 msec

7 te4-4.mpd02.den01.atlas.cogentco.com (154.54.7.130) 56 msec

te3-2.ccr01.slc01.atlas.cogentco.com (154.54.3.14) 60 msec 64 msec

8 te3-2.ccr01.slc01.atlas.cogentco.com (154.54.3.14) 64 msec

te7-3.ccr01.smf01.atlas.cogentco.com (66.28.4.194) 72 msec

te4-2.ccr01.smf01.atlas.cogentco.com (154.54.1.101) 76 msec

9 te7-3.ccr01.smf01.atlas.cogentco.com (66.28.4.194) 100 msec 80 msec 80 msec

10 te3-3.ccr01.pdx02.atlas.cogentco.com (154.54.40.110) 84 msec

te4-3.ccr01.pdx02.atlas.cogentco.com (154.54.40.114) 84 msec 84 msec

11 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

eprosenx Uncategorized