Date: Mon, 20 Aug 2007 15:21:38 -0400
To: nanog@merit.edu
Subject: Cogent latency / congestionDoes anyone have any details about the Cogent outage that started
this morning (9am GMT-400) and is still continuing ? If its a fibre
cut between Montville (NJ?) and Cleveland OH
(http://status.cogentco.com/) why is it so bad in Chicago and Albany
locations ? Is there really that little excess capacity ?
No details, but I've seen reports of 100+ms between S.F. and L.A. on
Cogent, as well.
hexstars-computer:~ hexstar$ traceroute status.cogentco.com
traceroute to status.cogentco.com (38.9.51.60), 64 hops max, 40 byte packets
1 10.0.1.1 ( 10.0.1.1) 2.466 ms 1.044 ms 1.012 ms
2 * * *
3 * ge-2-8-ur01.oakland.ca.sfba.comcast.net (68.86.249.113) 11.942 ms 12.726 ms
4 68.86.90.138 (68.86.90.138) 16.877 ms 13.270 ms 15.623 ms
5 68.86.90.149 ( 68.86.90.149) 16.048 ms 16.763 ms 14.488 ms
6 68.86.90.165 (68.86.90.165) 20.053 ms 17.489 ms 16.963 ms
7 te-4-4.car2.sanjose1.level3.net (4.79.43.133) 19.845 ms 19.059 ms 17.520 ms
8 ae-23-79.car3.sanjose1.level3.net ( 4.68.18.69) 19.369 ms 16.214 ms 14.273 ms
9 cogent-comm.car3.sanjose1.level3.net (4.68.110.138) 17.942 ms 20.228 ms 19.781 ms
10 v3492.mpd01.sjc01.atlas.cogentco.com (154.54.6.105) 108.626 ms 198.176 ms 223.244 ms
11 t9-2.mpd01.lax01.atlas.cogentco.com (154.54.5.70) 101.092 ms 105.903 ms 105.539 ms
12 t2-1.mpd01.iah01.atlas.cogentco.com (154.54.3.185) 103.102 ms 97.710 ms 98.995 ms
13 t3-4.ccr01.clt01.atlas.cogentco.com (154.54.7.146 ) 206.319 ms 248.681 ms *
14 t3-3.mpd01.dca01.atlas.cogentco.com (154.54.5.54) 108.830 ms 118.044 ms 133.046 ms
15 v3491.mpd01.dca02.atlas.cogentco.com (154.54.2.182) 103.144 ms 102.917 ms 103.185 ms
16 v3490.mpd01.iad03.atlas.cogentco.com (154.54.7.98) 103.380 ms 104.275 ms 103.733 ms
17 g1-1.core01.hhc.corp.cogentco.com ( 38.104.58.6) 104.401 ms * 107.873 ms
18 support.cogentco.com (38.9.51.60) 102.263 ms 104.932 ms 102.603 ms