[outages] Savvis/CenturyLink issues this AM

[Cary Wiedemann]

This outage is still ongoing and has far-reaching implications beyond their
CH3 facility.  I have servers in DC3 (Sterling, VA/Washington, DC) and
haven't been able to reach 12.0.0.0/8 among other networks since early this
morning.

Looks like things will get worse before they get better.  Here's their
latest update:

DATE OF EVENT: Tuesday, April 22, 2014
TIME OF EVENT : 03:20 CDT
MASTER CASE: 4579123

UPDATE: In effort to resolve an ongoing incident, CenturyLink will be
reloading several internet facing backbone devices within our network.
This emergency maintenance will potentially result in an intermittent loss
of connectivity and/or latency for up to 15 minutes.  Clients with
non-redundant ATS MPLS and EVPL connectivity could experience additional
impact during this maintenance.  This activity is required to address a
resource constraint on several peering and hosting routers within the
CenturyLink backbone network.  CenturyLink will notify all impacted clients
via email at the beginning and after the completion of the maintenance
activity.  We apologize for the inconvenience.

CRC Management
Request at savvis.net
North America - 888 638 6771
EMEA - 00800 7288 4743
Asia-Pacific - +65 63058099

- Cary Wiedemann
carywiedemann at gmail.com
+1 703 592 6498


On Tue, Apr 22, 2014 at 10:34 AM, Bill Weiss
<houdini+outages at clanspum.net>wrote:

> Unsure if this is related to the L3 issues or not.  Savvis, at least at
> the CH3 datacenter, has had bad connectivity problems since 3:20AM CDT.
> Internet Pulse shows atrocious packet loss to almost everywhere from
> Savvis.
>
> Master case number at Savvis is 4579123.  They don't have any more info
> than "yep, we're down, working on it".
>
> --
> Bill Weiss
> _______________________________________________
> Outages mailing list
> 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/20140422/8c360632/attachment.htm>