- To: outages-list@eskimo.com
- Subject: Sprint Backbone Outage
- From: Robert Dinse <nanook@eskimo.com>
- Date: Mon, 12 Oct 1998 01:24:16 -0700 (PDT)
- Resent-Date: Mon, 12 Oct 1998 01:22:42 -0700
- Resent-From: outages-list@eskimo.com
- Resent-Message-ID: <"R1lUo3.0.n-6.HnR8s"@mx1>
- Resent-Sender: outages-list-request@eskimo.com
- Prev by Date: Network Outage
- Next by Date: Routing Problems in the Fort Worth
- Prev by thread: Routing Problems in the Fort Worth
- Next by thread: Network Outage
- Index(es):
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Sprint Backbone Outage
It is 1:17am and Sprint appears to be routing traffic to us again.
The outage which lasted from almost exactly at midnight until about 1:10am
on Monday morning, Oct 12, was the result of work Sprint was doing on "route
reflectors".
They did not expect the work to cause an outage due to redundancy that is
built in to the system that is supposed to prevent one but an outage it did
cause. They did not announce the work in advance because they did not expect
an outage to result.
They tell me that there is sufficient redundancy in the backbone now that
normally backbone work will not cause any outages and so they do not announce
it. They only announce work on parts of the infrastructure expected to result
in an outage. Obviously in this case their expectations were incorrect.