Internet Split? Cogent VS Level 3


#1

I wonder how my log will show up tonight… i already see significant loss in traffic…

Quote:
slashmicah asks: “Internet partitioning and Tier 1 ISPs are something most people don’t know much about (myself included). Today, however, some Slashdot readers might have run into some issues involving these two topics. Cogent Communications and Level 3, both Tier 1 ISPs, are apparently having some ‘undisclosed’ disagreements, causing an Internet partition by turning-off or deactivating their peering point. Cogent Co. has released a statement explaining their side of the problem, however they have no mention of when the problem will be fixed, or when they will sort it out. This partitioning is a problem because any [single-homed] computers that are connected through Cogent Co, can not connect to [single-homed] computers connected through Level 3. Having spent all day sorting out this problem, I ask Slashdot: Isn’t there a better way that the issue of peering can be handled/regulated? If not, does the future hold a scenario in which the Internet is split into several separate networks, only to be connected at the whims of large corporations?”


#2

[quote]I wonder how my log will show up tonight… i already see significant loss in traffic…

[/quote]

You shouldn’t notice any loss in traffic due to this - Cogent is reachable just fine from DH’s network, and vice-versa. Even a single-homed Cogent customer would be able to reach your site just fine.

[william@mitch]% traceroute www.cogentco.com
traceroute to cogentco.com (38.9.51.20), 64 hops max, 40 byte packets
1 gw-66-33-192-1.dreamhost.com (66.33.192.1) 0.608 ms 0.379 ms 0.549 ms
2 ge-0-1-0.405.ar1.LAX3.gblx.net (67.17.162.161) 0.554 ms 0.665 ms 0.580 ms
3 so0-0-0-2488M.ar1.LAX2.gblx.net (67.17.72.106) 0.730 ms 0.930 ms 0.740 ms
4 cogent.ar1.LAX2.gblx.net (208.50.13.198) 11.755 ms 11.737 ms 12.116 ms
5 p9-1.core01.lax01.atlas.cogentco.com (154.54.2.101) 11.35 ms 10.946 ms 11.300 ms
6 p5-0.core01.san01.atlas.cogentco.com (66.28.4.78) 13.260 ms 13.918 ms 13.274 ms
7 p6-0.core01.iah01.atlas.cogentco.com (66.28.4.5) 44.96 ms 44.316 ms 44.204 ms
8 p4-0.core01.dca01.atlas.cogentco.com (66.28.4.89) 82.412 ms 83.981 ms 82.613 ms
9 p2-0.ca03.iad03.atlas.cogentco.com (154.54.1.102) 83.478 ms 83.582 ms 84.718 ms
10 www.cogentco.com (38.9.51.20) 83.359 ms !C 84.49 ms !C 83.438 ms !C

route-server>sh ip bgp 66.33.192.1
BGP routing table entry for 66.33.192.0/19, version 102541647
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Not advertised to any peer
174 3549 26347
66.28.1.1 from 66.28.1.1 (66.28.1.1)
Origin IGP, metric 78000, localpref 100, valid, external, best
Community: 174:21000 16631:1000

route-server>trace 66.33.206.206

Type escape sequence to abort.
Tracing the route to ns1.dreamhost.com (66.33.206.206)

1 38.112.10.213 [AS 174] 0 msec 0 msec 0 msec
2 g0-7.core01.dca01.atlas.cogentco.com (66.28.6.189) [AS 174] 4 msec 4 msec 0 msec
3 p15-0.core01.dca01.atlas.cogentco.com (66.28.4.21) [AS 174] 4 msec 4 msec 0 msec
4 p4-0.core01.phl01.atlas.cogentco.com (66.28.4.18) [AS 174] 4 msec 4 msec 4 msec
5 p5-0.core02.jfk02.atlas.cogentco.com (66.28.4.1) [AS 174] 8 msec 8 msec 8 msec
6 p12-0.core01.mci01.atlas.cogentco.com (154.54.3.202) [AS 174] 44 msec 44 msec 44 msec
7 p10-0.core02.sfo01.atlas.cogentco.com (66.28.4.209) [AS 174] 156 msec 224 msec 140 msec
8 p10-0.core01.sjc03.atlas.cogentco.com (66.28.4.133) [AS 174] 80 msec 96 msec 80 msec
9 gblx.sjc03.atlas.cogentco.com (154.54.11.174) [AS 174] 80 msec 80 msec 80 msec
10 so0-3-0-622M.ar1.LAX3.gblx.net (67.17.64.49) [AS 3549] 84 msec 80 msec 80 msec
11 GE1-GX.dreamhost.com (67.17.162.162) [AS 3549] 84 msec 80 msec 80 msec
12 ns1.dreamhost.com (66.33.206.206) [AS 26347] 84 msec 84 msec 84 msec


#3

cool cool! good to hear :slight_smile: because one of my buddy that works over at Gravity (http://iro.ragnarokonline.com/) was telling me he couldn’t reach my site from their office, could have been a fluke :slight_smile: great to hear!


#4

This is sure showing up on the internet health report. I haven’t seen any problems yet though, thanks for the heads-up.