RE: Cogent issues in SF area?
Maybe they depeered themselves. They seem to be on a roll! It's quite ironic and they (Cogent) are quite contradicting themselves. When their CEO, Dave Schaffer comes out to media and bashes Level3, France Telecom, AOL, etc (the list goes on), citing Cogent is being unfairly treated, each and every time Cogent gets depeered, you would think Cogent would be the last network to be the one pulling jack moves. Now it seems Cogent is the one that's unfairly treating their peers, the table has been turned around. Time to buy some ATDN transit just to reach Cogent, eh? I'm sure they'll get a kick out of this one :) james
Re: Cogent issues in SF area?
It's quite ironic and they (Cogent) are quite contradicting themselves. When their CEO, Dave Schaffer comes out to media and bashes Level3, France Telecom, AOL, etc (the list goes on), citing Cogent is being unfairly treated, each and every time Cogent gets depeered, you would think Cogent would be the last network to be the one pulling jack moves. what we see in others is oft a reflection of our own thoughts randy
Cogent issues in SF area?
Anyone else seeing it? BGP_Level3traceroute 208.70.27.35 Type escape sequence to abort. Tracing the route to 208.70.27.35 1 4.79.220.77 0 msec 4 msec 0 msec 2 4.68.123.30 [AS 3356] 8 msec 0 msec 4 msec 3 4.68.18.5 [AS 3356] 0 msec 4 msec 0 msec 4 4.68.110.138 [AS 3356] 4 msec 0 msec 4 msec 5 154.54.6.81 [AS 174] 4 msec * 0 msec 6 154.54.6.133 [AS 174] 4 msec 4 msec 4 msec 7 154.54.24.38 [AS 174] 4 msec 4 msec 4 msec 8 * * * 9 * * * Bah! -Mike
Re: Cogent issues in SF area?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mike Lyon wrote: Anyone else seeing it? BGP_Level3traceroute 208.70.27.35 Type escape sequence to abort. Tracing the route to 208.70.27.35 1 4.79.220.77 0 msec 4 msec 0 msec 2 4.68.123.30 [AS 3356] 8 msec 0 msec 4 msec 3 4.68.18.5 [AS 3356] 0 msec 4 msec 0 msec 4 4.68.110.138 [AS 3356] 4 msec 0 msec 4 msec 5 154.54.6.81 [AS 174] 4 msec * 0 msec 6 154.54.6.133 [AS 174] 4 msec 4 msec 4 msec 7 154.54.24.38 [AS 174] 4 msec 4 msec 4 msec 8 * * * 9 * * * Ok getting there from Cogent in Denver: [EMAIL PROTECTED] ~]# traceroute 208.70.27.35 traceroute to 208.70.27.35 (208.70.27.35), 30 hops max, 46 byte packets 1 10.10.1.254 (10.10.1.254) 0.304 ms 0.157 ms 0.143 ms 2 ai-core (38.116.133.1) 0.548 ms 0.451 ms 0.424 ms 3 f0-2.na01.b009854-0.den01.atlas.cogentco.com (38.112.6.145) 0.944 ms 1.346 ms 0.692 ms 4 g0-3.core01.den01.atlas.cogentco.com (66.250.10.217) 0.929 ms 0.813 ms 1.131 ms 5 t3-1.mpd01.den01.atlas.cogentco.com (154.54.5.30) 1.156 ms 0.770 ms 1.295 ms 6 t7-2.mpd02.sfo01.atlas.cogentco.com (154.54.6.34) 24.828 ms 24.632 ms 24.537 ms 7 t3-4.ccr01.sfo05.atlas.cogentco.com (154.54.24.38) 25.055 ms 24.444 ms 24.387 ms 8 207.241.239.146 (207.241.239.146) 24.749 ms 24.791 ms 24.385 ms 9 ia700743.eg.archive.org (208.70.27.35) 25.234 ms 25.478 ms 25.202 ms -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org iD8DBQFG/VfCnSVip47FEdMRAvzJAJ93U/xqs3SeZnYK/9CSCK8RCZNWmwCfUDm6 FvWsm7RERiD57HWoGikTblM= =bZis -END PGP SIGNATURE-
Re: Cogent issues in SF area?
We're seeing very poor performance on Cogent in Chicago to major sites such as CNN and Salon. Traceroutes indicate packets dropping inside Cogent's network and at their handoff to at atdn.net. Opened a ticket with Cogent around 10am Central, haven't heard from anybody since. Not necessarily related to your problem, but maybe another data point. Carl Hirsch Mike Lyon [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 09/28/2007 01:39 PM To NANOG nanog@merit.edu cc Subject Cogent issues in SF area? Anyone else seeing it? BGP_Level3traceroute 208.70.27.35 Type escape sequence to abort. Tracing the route to 208.70.27.35 1 4.79.220.77 0 msec 4 msec 0 msec 2 4.68.123.30 [AS 3356] 8 msec 0 msec 4 msec 3 4.68.18.5 [AS 3356] 0 msec 4 msec 0 msec 4 4.68.110.138 [AS 3356] 4 msec 0 msec 4 msec 5 154.54.6.81 [AS 174] 4 msec * 0 msec 6 154.54.6.133 [AS 174] 4 msec 4 msec 4 msec 7 154.54.24.38 [AS 174] 4 msec 4 msec 4 msec 8 * * * 9 * * * Bah! -Mike
Re: Cogent issues in SF area?
CNN and www.archive.org were the two sites I couldn't get to... -Mike On 9/28/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: We're seeing very poor performance on Cogent in Chicago to major sites such as CNN and Salon. Traceroutes indicate packets dropping inside Cogent's network and at their handoff to at atdn.net. Opened a ticket with Cogent around 10am Central, haven't heard from anybody since. Not necessarily related to your problem, but maybe another data point. Carl Hirsch *Mike Lyon [EMAIL PROTECTED]* Sent by: [EMAIL PROTECTED] 09/28/2007 01:39 PM To NANOG nanog@merit.edu cc Subject Cogent issues in SF area? Anyone else seeing it? BGP_Level3traceroute 208.70.27.35 Type escape sequence to abort. Tracing the route to 208.70.27.35 1 4.79.220.77 0 msec 4 msec 0 msec 2 4.68.123.30 [AS 3356] 8 msec 0 msec 4 msec 3 4.68.18.5 [AS 3356] 0 msec 4 msec 0 msec 4 4.68.110.138 [AS 3356] 4 msec 0 msec 4 msec 5 154.54.6.81 [AS 174] 4 msec * 0 msec 6 154.54.6.133 [AS 174] 4 msec 4 msec 4 msec 7 154.54.24.38 [AS 174] 4 msec 4 msec 4 msec 8 * * * 9 * * * Bah! -Mike
RE: Cogent issues in SF area?
Maybe they depeered themselves. They seem to be on a roll! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Lyon Sent: Friday, September 28, 2007 2:39 PM To: NANOG Subject: Cogent issues in SF area? Anyone else seeing it? BGP_Level3traceroute 208.70.27.35 Type escape sequence to abort. Tracing the route to 208.70.27.35 1 4.79.220.77 0 msec 4 msec 0 msec 2 4.68.123.30 [AS 3356] 8 msec 0 msec 4 msec 3 4.68.18.5 [AS 3356] 0 msec 4 msec 0 msec 4 4.68.110.138 [AS 3356] 4 msec 0 msec 4 msec 5 154.54.6.81 [AS 174] 4 msec * 0 msec 6 154.54.6.133 [AS 174] 4 msec 4 msec 4 msec 7 154.54.24.38 [AS 174] 4 msec 4 msec 4 msec 8 * * * 9 * * * Bah! -Mike
Re: Cogent issues in SF area?
The archive.org/Cogent stuff was an issue specific to archive.org's connection to Cogent. Jim Shankland
RE: Cogent issues in SF area?
http://www.e-gerbil.net/cogent-t1r looks like they're playing the depeering games again. E From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Lyon Sent: Friday, September 28, 2007 3:45 PM To: [EMAIL PROTECTED] Cc: NANOG Subject: Re: Cogent issues in SF area? CNN and www.archive.org were the two sites I couldn't get to... -Mike On 9/28/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: We're seeing very poor performance on Cogent in Chicago to major sites such as CNN and Salon. Traceroutes indicate packets dropping inside Cogent's network and at their handoff to at atdn.net. Opened a ticket with Cogent around 10am Central, haven't heard from anybody since. Not necessarily related to your problem, but maybe another data point. Carl Hirsch Mike Lyon [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 09/28/2007 01:39 PM To NANOG nanog@merit.edu cc Subject Cogent issues in SF area? Anyone else seeing it? BGP_Level3traceroute 208.70.27.35 Type escape sequence to abort. Tracing the route to 208.70.27.35 1 4.79.220.77 0 msec 4 msec 0 msec 2 4.68.123.30 [AS 3356] 8 msec 0 msec 4 msec 3 4.68.18.5 [AS 3356] 0 msec 4 msec 0 msec 4 4.68.110.138 [AS 3356] 4 msec 0 msec 4 msec 5 154.54.6.81 [AS 174] 4 msec * 0 msec 6 154.54.6.133 [AS 174] 4 msec 4 msec 4 msec 7 154.54.24.38 [AS 174] 4 msec 4 msec 4 msec 8 * * * 9 * * * Bah! -Mike
Re: Cogent issues in SF area?
No problem here... computer:~ hexstar$ traceroute 208.70.27.35 traceroute to 208.70.27.35 (208.70.27.35), 64 hops max, 40 byte packets 1 10.0.1.1 (10.0.1.1) 2.672 ms 1.937 ms 1.730 ms 2 * * * 3 ge-2-8-ur01.oakland.ca.sfba.comcast.net (68.86.249.113) 11.590 ms 11.371 ms 15.132 ms 4 te0-7-0-4-ar01.oakland.ca.sfba.comcast.net (68.86.90.146) 18.551 ms 12.220 ms 13.409 ms 5 68.86.85.77 (68.86.85.77) 14.655 ms 15.077 ms 14.305 ms 6 comcast-ip.car2.sanjose1.level3.net (4.79.43.134) 18.156 ms 16.841 ms 16.973 ms 7 te-4-4.car2.sanjose1.level3.net (4.79.43.133) 16.951 ms 16.932 ms 16.473 ms 8 ae-33-89.car3.sanjose1.level3.net (4.68.18.133) 21.731 ms 23.819 ms 17.007 ms 9 cogent-comm.car3.sanjose1.level3.net (4.68.110.138) 18.566 ms 18.726ms 19.115 ms 10 v3499.mpd01.sjc01.atlas.cogentco.com (154.54.6.237) 26.997 ms 32.775ms 28.556 ms 11 t7-1.mpd02.sfo01.atlas.cogentco.com (154.54.2.53) 28.941 ms 31.305 ms 31.928 ms 12 t3-4.ccr01.sfo05.atlas.cogentco.com (154.54.24.38) 27.725 ms 31.943ms 27.018 ms 13 207.241.239.163 (207.241.239.163) 31.519 ms 28.896 ms 28.454 ms 14 208.70.27.35 (208.70.27.35) 29.631 ms 28.457 ms 28.165 ms
