Funky CC Routing

NodeBytes

Dedi Addict
Colostore -> CC Buffalo


2 67.214.170.217.gw.colostore.net (67.214.170.217) 0.256 ms 0.245 ms 0.229 ms
3 gi1-29.ccr01.sbn01.atlas.cogentco.com (38.104.216.161) 0.877 ms 1.437 ms 1.429 ms
4 te3-2.ccr01.tol01.atlas.cogentco.com (154.54.45.126) 4.418 ms 4.408 ms te4-3.ccr01.tol01.atlas.cogentco.com (154.54.7.153) 4.351 ms
5 te7-2.ccr02.cle04.atlas.cogentco.com (154.54.45.133) 7.011 ms te3-8.ccr02.cle04.atlas.cogentco.com (154.54.43.122) 6.599 ms te4-7.ccr02.cle04.atlas.cogentco.com (154.54.5.230) 6.998 ms
6 te4-1.ccr01.buf02.atlas.cogentco.com (154.54.27.85) 11.727 ms te3-2.ccr01.buf02.atlas.cogentco.com (154.54.43.118) 11.824 ms 11.788 ms
7 38.122.36.46 (38.122.36.46) 13.069 ms 25.636 ms 25.608 ms
8 . (172.245.12.226) 14.855 ms 15.407 ms *
9 host.colocrossing.com (198.23.151.74) 15.790 ms 16.280 ms 15.050 ms
10 198.46.142.3 (198.46.142.3) 22.834 ms 22.825 ms 22.809 ms

From CC Buffalo -> Colostore

 


Code:
1  10.32.1.128 (10.32.1.128)  0.053 ms  0.028 ms  0.023 ms
 2  host.colocrossing.com (198.23.151.73)  0.798 ms  0.656 ms  0.962 ms
 3  host.colocrossing.com (192.3.9.141)  0.683 ms  0.674 ms  0.646 ms
 4  buf-b1-link.telia.net (213.248.96.41)  0.284 ms te7-4.ccr01.buf02.atlas.cogentco.com (38.122.36.45)  0.396 ms buf-b1-link.telia.net (213.248.96.41)  0.244 ms
 5  216.156.0.253.ptr.us.xo.net (216.156.0.253)  18.632 ms  18.522 ms nyk-bb1-link.telia.net (80.91.246.37)  14.688 ms
 6  nyk-b5-link.telia.net (213.155.135.19)  9.585 ms 207.88.14.6.ptr.us.xo.net (207.88.14.6)  13.232 ms  13.234 ms
 7  te3-8.ccr01.sbn01.atlas.cogentco.com (154.54.45.125)  11.343 ms  11.328 ms 207.88.184.146.ptr.us.xo.net (207.88.184.146)  13.294 ms
 8  vlan70.csw2.NewYork1.Level3.net (4.69.155.126)  27.003 ms border6.po2-bbnet2.chg.pnap.net (64.94.32.75)  13.192 ms 38.104.216.162 (38.104.216.162)  11.317 ms
 9  ae-82-82.ebr2.NewYork1.Level3.net (4.69.148.41)  21.738 ms giglinx-44.border6.chg.pnap.net (69.25.148.66)  14.133 ms sbisw01.sustainabledatacenters.com (67.214.170.218)  11.831 ms
10  45.smart-dns.net (206.212.240.45)  14.512 ms  14.470 ms ae-46-46.ebr2.NewYork2.Level3.net (4.69.201.30)  21.859 ms
11  ae-2-2.ebr1.Chicago1.Level3.net (4.69.132.65)  21.771 ms ---.sb.----.com (--.--.---.---)  11.837 ms  12.113 ms
 
Last edited by a moderator:

drmike

100% Tier-1 Gogent
Yeah CC's Buffalo location is a laughable routing mess.  Okay, I haven't checked things in a month or more there.

"we have Level3 in our mix"  --- but watch the packets fly wrong directions and avoid Level3 directly out of CC's location or directly inbound too.  This has been happening since L3 was demoted and "Gogent" was added and XO.  Weird that they have "Gogent" but seems to only be accessible via XO's horrid route-to

The latency even with the silliness isn't noticeable big increase between those two locations.  Could be a lot worse.  
 

drmike

100% Tier-1 Gogent
Yeah I have been staring at their info on HE for eons.

What should I note this time? :) Other than that big drop in IPv4 Prefixes Announced and Originated...
 

NodeBytes

Dedi Addict
1.) It's all IPv4

2.) Most of it Piggybacks off the DC's BGP blend. (Not a huge problem, but with their scale they could do their own peering/BGP).

3.) The XO Crap is killing me and a lot of routes that could be shorter/more efficient on HE or Cogent.

Telia -> Cogent -> XO -> Cogent -> Level3 -> DC. Such a mess.
 
Last edited by a moderator:

drmike

100% Tier-1 Gogent
Good points.  To be honest, I've never made sense of how they handle their routing.  The upstream graphic is umm, semi odd.

" Most of it Piggybacks off the DC's BGP blend. "   I've suspected this.   What truly confirms that?  I do see some of the datacenters in the upstream graph which is one clue :)  Anything else?

Yes, Colocrossing is strictly IPv4.   People have been whining for years about that and running the IPv6 jokes their way just as long.

XO routing.... well from Buffalo to anywhere, do you see anything other than Telia to XO out of there?  Last time I looked/cared, all I saw was Telia to XO with Cogent often appearing thereafter on outbound...

"Telia -> Cogent -> XO -> Cogent -> Level3 -> DC"

Again, Cogent has the packets early and wastes fussing with XO.  Weird since bonesheads claim they have Cogent and XO and Level3 bandwidth (maybe more claims these days?).   From what I see, doesn't appear so.  Looks like in Buffalo that they have Telia for sure on the outbound.  Inbound they accept Cogent (as per your routes).  I see on inbound they accept XO directly in also.  From Choopa in NJ, they accept into Buffalo over Telia too.

The network wasn't like this 10 months ago it was noticeably better.
 

NodeBytes

Dedi Addict
I'll post a more complete answer tomorrow, but at one point I found a graph of an active bgp session from CC LA (Quadranet) and it was pure Quadranet BGP.
 

Tux

DigitialOcean? lel
Good points.  To be honest, I've never made sense of how they handle their routing.  The upstream graphic is umm, semi odd.

" Most of it Piggybacks off the DC's BGP blend. "   I've suspected this.   What truly confirms that?  I do see some of the datacenters in the upstream graph which is one clue :)  Anything else?

Yes, Colocrossing is strictly IPv4.   People have been whining for years about that and running the IPv6 jokes their way just as long.

XO routing.... well from Buffalo to anywhere, do you see anything other than Telia to XO out of there?  Last time I looked/cared, all I saw was Telia to XO with Cogent often appearing thereafter on outbound...

"Telia -> Cogent -> XO -> Cogent -> Level3 -> DC"

Again, Cogent has the packets early and wastes fussing with XO.  Weird since bonesheads claim they have Cogent and XO and Level3 bandwidth (maybe more claims these days?).   From what I see, doesn't appear so.  Looks like in Buffalo that they have Telia for sure on the outbound.  Inbound they accept Cogent (as per your routes).  I see on inbound they accept XO directly in also.  From Choopa in NJ, they accept into Buffalo over Telia too.

The network wasn't like this 10 months ago it was noticeably better.
I can confirm that at least Cogent and Telia are accepted inbound. My ISP gives some Telia routes, but mostly Cogent routes.

CC's routing is overall wonky anyway. I'm sure most of the locations are mostly over nLayer with DC blends as backup, then we have freak-outs like Buffalo without nLayer but far worse peerage. Then again, my ISP's routing changes randomly every day anyway.
 
Top