[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Megapop_alert] MegaPOP Network Alert Update (fwd)
- To: outages-list@eskimo.com
- Subject: [Megapop_alert] MegaPOP Network Alert Update (fwd)
- From: Robert Dinse <nanook@eskimo.com>
- Date: Fri, 16 Mar 2001 20:44:51 -0800 (PST)
- Resent-Date: Fri, 16 Mar 2001 20:44:56 -0800
- Resent-From: outages-list@eskimo.com
- Resent-Message-ID: <"3g5mw.0.GY5.8lkiw"@mx1>
- Resent-Sender: outages-list-request@eskimo.com
This is relating to the routing problems with the MegaPOP POP's. It would
appear they have routed around this for Seattle at least as I am seeing
successful connections from the Seattle POP.
---------- Forwarded message ----------
Date: Fri, 16 Mar 2001 22:38:07 -0600
From: noc@megapop.net
To: megapop_alert@lists.starnetinc.com
Subject: [Megapop_alert] MegaPOP Network Alert Update
Attention MegaPOP Customer,
At 22:38 on 2001-03-16 the following was posted to Network Alerts:
Problem : Loss of routing
Location: 999 - Global,
Status : Ongoing
Event : Major problem with DialUp Major problem with the Network
Detailed Description:
We are continuing to work with our provider on this issue.
The resolution has been compounded by multiple failures, all of which require resolution before the routing problem can be resolved. Currently they have ATM network switch issues and circuit failures, all of which are affecting our network.
We are continuing to route around this massive failure wherever possible.
We will post updates here as new information becomes available, unfortunately due to the extent of the outage a realistic ETR is not possible at this time.
ETR: UNKNOWN
This message was posted by: cparker, regarding Trouble Ticket: 11106.
_______________________________________________
This message was automatically generated by
MegaPOP Network Operations for subscribers
of the Megapop_alert mailing list.
Mailing List Management: http://lists.starnetinc.com/cgi-bin/list.cgi
Network Operations Current Status: http://www.megapop.net/noc/