This is a coordinated effort between the power company (PECO), AboveNet (the actual owner of the fiber in question), and Cogent. Since PECO needs to approve access for AboveNet, and since it requires closing a major thoroughfare, the new ETA is 2 AM with no official ETR.
Wouldn't it be possible for Nocster to basically shut off all traffic going on the cogent line if that's the only problem?
I'm actually not noticing anything too serious on the routes to Nocster, but I'm getting about 30% packet loss on ge-7-0-ctsi.rtr0.scra1.hostnoc.net [220.127.116.11] which I believe is already inside the Nocster network.
As of approxiately 4:30 PM EDT on May 12th, 2004 Cogent Communications experienced an underground fiber fire in a main corridor of Philadelphia. The fiber is owned by MFN/AboveNet and, due to it's proximity to the local power company's (PECO) power grid, there has been a delay in repair. The delay is due to the need to first reroute power through a different grid, and secondly to close the section of the highway the fiber runs under. There is currently no ETA for repair. Although the fiber in question does not directly affect our connection with Cogent, we are affected since the Cogent customers that were directly affected have been re-routed onto our network segment. BurstNET has re-routed much of our traffic over other carriers, but you may still see some minor packet loss and slow speeds temporarily. This is due to many other carriers re-routing as well, and overloading some of the other regional networks/backbones.
Originally posted by aleck he said "almost down" actually
There hasn't been a network problem for almost 2 days, it's been a little more than 1 day (that doesn't affect everybody, too). It's most likely an issue with his server going slow for some reason, not the network. Speeds are still fine for me, I'm just routed oddly around the fiber that was damaged. That's Cogent's problem in Philly, not Burst's problem in Scranton though.