Cogent Routers Down: Can Any Experts Offer Help

Portal Home > Knowledgebase > Articles Database > Cogent Routers Down: Can Any Experts Offer Help

Posted by JenniH, 11-17-2005, 02:45 PM
I'm a little out of my depth regarding network issues like these... I wondered if someone could explain a few issues? I can't view our sites at either axishost or jumpline from here (in the UK). Using Alerta, however, I see that the boxes are up and running. I've therefore used tracert at dnsstuff.com to look around, and see the following: ------------------ Hop T1 T2 T3 Best Graph IP Hostname Dist TTL Ctry Time 1 1 449 * 0.6 ms 66.36.240.2 AS0 IANA-RSVD-0 c-vl102-d1.acc.dca2.hopone.net. 255 US Unknown: 82213114 2 3 * 5 0.6 ms [+0ms] 66.36.224.242 AS0 IANA-RSVD-0 ge5-0.core1.dca2.hopone.net. 0 miles [+0] 254 US Unknown: 840eef34 3 4 0 1 0.6 ms [+0ms] 66.36.224.227 AS0 IANA-RSVD-0 ge5-0.core2.dca2.hopone.net. 0 miles [+0] 254 US Unknown: 81fde682 4 2 5 4 1.9 ms [+1ms] 66.36.224.185 AS0 IANA-RSVD-0 iar2-ge-2-0-0.washington.savvis.net. 0 miles [+0] 252 US Unix: 18:34:02.559 5 2 1 2 1.9 ms [+0ms] 206.24.226.97 AS0 IANA-RSVD-0 bcs1-loopback.washington.savvis.net. 0 miles [+0] 252 US Unix: 18:34:02.656 6 9 5 6 3.9 ms [+2ms] 208.173.52.113 AS0 IANA-RSVD-0 cpr1-pos-0-0.virginiaequinix.savvis.net. 0 miles [+0] 251 US Unix: 18:34:02.693 7 11 478 465 3.9 ms [+0ms] 208.173.10.182 AS0 IANA-RSVD-0 [Missing reverse DNS entry] 0 miles [+0] 250 US [Router did not respond] 8 13 4 3 3.9 ms [+0ms] 154.54.2.197 AS0 IANA-RSVD-0 p11-0.core02.dca01.atlas.cogentco.com. 0 miles [+0] 249 US [Router did not respond] 9 20 28 * 20 ms [+16ms] 66.28.4.161 AS224 UNINETT p14-0.core01.atl01.atlas.cogentco.com. 0 miles [+0] 248 US [Router did not respond] 10 55 1508 * 39 ms [+18ms] 38.112.7.86 AS5089 NTL tulix_systems.demarc.cogentco.com. -1 miles [+0] 0 miles [+0] 247 US [Router did not respond] 11 176 * * 39 ms [+0ms] 154.37.0.2 AS0 IANA-RSVD-0 [Missing reverse DNS entry] -1 miles [+0] 0 miles [+0] 246 US Unknown: 842d83eb 12 39 * * 39 ms [+0ms] 154.37.3.42 AS0 IANA-RSVD-0 [Reached Destination]cappa.genwebserver.com. -1 miles [+0] 54 US -------------------- The traceroute therefore gets through (so why can't I via a browser?)... but mentions that the router did not respond at atlas.cogentco.com. So I took a look at Pulse which tells me that for cogent: Origin AT&T 67 111 143 32 Cogent 180 91 82 NA ... with plenty of red boxes for them So: - I am guessing that I can't view because an internet backbone carrier (Cogent) is having problems. Correct? - Most people will still be able to see the sites. Correct? - Lots of people and tens of thousands of other sites will be in the same position as me. Correct? - There is nothing I can do about it. Correct? I hope someone can answer these and explain... I'm tearing my hair out here! Thanks very much.
Posted by JenniH, 11-17-2005, 03:44 PM
Is no-one able to offer any advice at all on this? Maybe I should temporarily re-house the sites at one of our other hosts until it is fixed? Anything?
Posted by Sekweta, 11-17-2005, 03:47 PM
It's not a router outage. Copied/pasted from NANOG: Cogent is experiencing 2 fiber cuts in the north/southeast-US. The locations are: Between Houston and Tampa (Southeast) Ticket #347277 Between Philidelpha and DC (Northeast) Ticket #347375 Customers traversing cogent's network will experience latency and packet loss. You can check the status of the ticket by going to http://status.cogentco.com.
Posted by JenniH, 11-17-2005, 03:51 PM
Thanks for the info LordDark. Unfortunately we can't view that page from here, I guess due to the fibre-sut itself. If anyone could offer info or responses on the other questions I raised it would be very much appreciated.
Posted by tkam, 11-17-2005, 05:13 PM
I actually think it's just one fiber cut (in the New Orleans area) and faulty hardware in the Washington DC area. Either way it's causing some havok for Cogent users.
Posted by dollar, 11-17-2005, 05:16 PM
Your trace that you did at DNSStuff was not from your home computer. Run a trace from your home computer to see where the connection dies for you. Correct Correct Correct Switch ISPs and/or switch hosts, but aside from that there is really nothing you can do.
Posted by JenniH, 11-17-2005, 06:23 PM
Thanks very much. Appreciated. Problems like this are also.... learning opportunities.
Posted by [inx]Olly, 11-17-2005, 09:46 PM
The biggest lesson that things will always go wrong, even with the big companies.
Posted by Sekweta, 11-18-2005, 05:57 PM
According to Cogent's website, the issue between Philly and D.C. was indeed a fiber cut and was repaired around 3:45 p.m. yesterday.
Posted by TeleSouthNet, 11-18-2005, 05:59 PM
Thank god its not Level 3 again