[outages] Zayo Transit

[Sean Pedersen]

Last update we received:

 

Dear Zayo Customer, The majority of our peering links with our affected peering partners have restored with ancillary points still left. We are working to clear damping and reset those sessions left and some customers may still experience latency until this is completed. Thank you for your patience and if you are still experiencing a hard down issue, let us know so we can work to resolve it in a timely manner. 

 

 

From: Outages [mailto:outages-bounces at outages.org] On Behalf Of Andy Litzinger via Outages
Sent: Friday, September 29, 2017 1:07 PM
To: Adam Gregory <adam.gregory at heidmar.com>
Cc: outages at outages.org
Subject: Re: [outages] Zayo Transit

 

We use Zayo for IP access and are still experiencing issues.  Here's the response we've recived from Zayo Support:

We are experiencing a major network event across multiple peering points from the global internet table that is impacting traffic throughout the internet. We are working to mitigate the incoming traffic across these peers at this time to lessen the impact until the root-cause of the influx can be identified and halted. We expect to have a resolution within the hour, however this appears to be incoming to the Zayo global internet routing table from our major peering partners. We appreciate your patience as our technical teams are fully engaged to cease impact to our customers at this time and we will update you as the status changes. We have opened the following customer-facing bridge to assist with real-time updates as they are known to our NCC team: <number removed>

-andy

 

On Fri, Sep 29, 2017 at 12:59 PM, Adam Gregory via Outages <outages at outages.org <mailto:outages at outages.org> > wrote:

Looks like zayo went above their 60k prefix limit causing peers to drop if configured to do so. Looks like they updated to 65k per peeringdb. 


On Sep 29, 2017, at 3:12 PM, Mike Davis via Outages <outages at outages.org <mailto:outages at outages.org> > wrote:

:|   sigh...

 

 created by Eric Zalesak on Sep 29, 2017 12:02:03 PM

Turn up customer was Singtel. We are still seeing sessions dropping after mitigating Singtel.

 

 created by Eric Zalesak on Sep 29, 2017 11:55:59 AM

Suspected turn up with open policy.

 

On Fri, Sep 29, 2017 at 11:22 AM, Steven Raymond via Outages <outages at outages.org <mailto:outages at outages.org> > wrote:

We are still seeing problems with Zayo (indirectly) as of now.



_______________________________________________
Outages mailing list
Outages at outages.org <mailto:Outages at outages.org> 
https://puck.nether.net/mailman/listinfo/outages

 

_______________________________________________
Outages mailing list
Outages at outages.org <mailto:Outages at outages.org> 
https://puck.nether.net/mailman/listinfo/outages


_______________________________________________
Outages mailing list
Outages at outages.org <mailto:Outages at outages.org> 
https://puck.nether.net/mailman/listinfo/outages

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20170929/40685690/attachment.htm>