From our ticket with Zayo:
*Reason for Outage Summary*: The cause of this issue was traced to an active construction site. 50' of 432 ct cable in 8 conduits were damaged. OSP was able to repair all conduits and pull and splice new fiber cable to make this repair. On Wed, Feb 1, 2017 at 10:06 AM, Jeroen Wunnink <Jeroen.Wunnink@gtt.net> wrote:
According to our optical noc they’re shooting new fiber as we speak. So now we wait.
Jeroen Wunnink IP Engineering manager office: +31.208.200.622 ext. 1011 Amsterdam Office www.gtt.net <http://www.gtt.net/>
On 01/02/2017, 15:41, "NANOG on behalf of Scott Farber" < nanog-bounces@nanog.org on behalf of scottf@gmail.com> wrote:
I know Zayo has a cut somewhere between MD and DC, it's knocked a few things offline. Not sure if it's a shared conduit and who else may be affected. ETA for splicing crew is 1030 Eastern.
On Wed, Feb 1, 2017 at 9:30 AM, Tom Beecher <beecher@beecher.cc> wrote:
> I see a couple things that leads me to believe there's something afoot in > NOVA as well. > > But not done with my first coffee, so unable to process any specifics yet. > :) > > On Wed, Feb 1, 2017 at 9:25 AM, Raymond Dijkxhoorn < > raymond@prolocation.net> > wrote: > > > Hello Ben, > > > > > > Is anyone else seeing connectivity issues along the east coast? Our pipe > >> through HE in NYC is showing loss to things behind most of Level3, and > >> Qwest below Washington. > >> > >> *Ben Hatton* > >> > >> Network Engineer > >> > >> Haefele TV Inc. > >> > >> d:(607)589-8000 > >> > >> bhatton@htva.net > >> > >> www.htva.net > >> > > > > We see the same, traffic going from Amsterdam towards HE heading USA is > > experiencing big packetloss at the moment. > > > > Traffic heading towards Ashburn seems affected from our point of view. > > > > Bye, > > Raymond. > > > > >