[snip]
I've noticed the sprint outage list has become very quiet, as has the MCI outage list. They seem to be quiet even during and after widely [snip] Sprint's list has gotten better regarding notifications. Using existing customer-provider relations is very useful. For our providers that are lax in notification, we hit the mangvlement/customer relations/sales folk pretty hard. In a collaborative enviornment, non-customers having a problem with provider S could contact a customer of provider S and have them source the trouble call [this is not, purely hytpothetical].
I'm thinking that it might be useful about now to set up a decent notification organization that can seek out network status and outage [snip]
As was pointed out elsewhere, the NLARN IPNmoo has been up and running for quite some time. The others in the handful that would be considered 'regulars' may want to comment as well, but I for one find it of great value. We've seen several instances of real-time debugging w/in this collaborative environment. Cheers, -- Joe Provo, Network Architect 800.763.8111 x3006 Network Operations Center Fax 508.229.2375 UltraNet Communications, Inc. <jprovo@ultra.net>
...
Sprint's list has gotten better regarding notifications. Using existing customer-provider relations is very useful. [snip]
From snailmail I just got from Sprint: "Sprint Internet Services does not guarantee proactive notification to our customer base on any outage or maintenance (scheduled or unscheduled)."
This in response to my complaint about an unscheduled "upgrade" to Anaheim that took the whole hub offline for 6 hours... It's a denial-of-service attack from SPRINT to its customers. Ehud
participants (2)
-
Ehud Gavron
-
Joe Provo - Network Architect