Feb 29, 2004 - Philly/Scranton Route Outage

BurstCEO · #1 02-29-2004, 22:02

We are currently experiencing another outage on our fiber path between Scranton and Philadelphia.

We do not have an ETA at this time, but will post a full report once information is available.

Thank you for your understanding and patience.

SMA
PRES/CEO
BURSTNET

BurstCEO · #2 02-29-2004, 23:04

We expect to be down again shortly here for testing of the Scranton portion of the GIG-E circuit from CTSI.

SMA
PRES/CEO
BURSTNET

BurstEmployee · #3 03-01-2004, 01:18

At this point, we are back up and running. The problem was discovered to be a multi-level issue within the providers network. Tomorrow more details as to the exact cause should be available.

BurstCEO · #4 03-01-2004, 12:37

CTSI is currently working on the circuit again. They tell us they ae swapping out GIG-E cards on their equipment in one of their POPs.

SMA
PRES/CEO
BURSTNET

BurstCEO · #5 03-01-2004, 20:24

We will have an official statement on the outages and repairs later this evening.

Please check back later this evening.

Thank you all for your support thru-out this stressful ordeal...most of you have been very patient and understanding--and we thank you so much for that.

SMA
PRES/CEO
BURSTNET

BurstEmployee · #6 03-02-2004, 00:20

Beginning on Saturday, Feb. 28th and continuing through Monday, March 1st the BurstNet network experienced extended periods of downtime. The outages appear to have been caused by multiple variables in several facilities. During the outages, extensive testing, maintenance, and replacement of gear in our Scranton facility, in our Philadelphia facility, and in our fiber providers facilities was performed. Much of this maintenance is only possible during a total outage such as this. Possible problematic pieces of equipment and cabling were found in all facilities, including the apparent cause of the recent packet loss issues over the last 2 months (my tests show 0% packet loss since restoring of service this evening). The basic summary is that our fiber provider had gear that needed to be swapped out due to errors, and we had one piece of network gear and 2 fiber cables that also showed errors. It is basically impossible to exactly pinpoint which piece caused the issue. Likely, any one of these by themself would have caused difficult to track and diagnose issues (such as low-level packet loss) but, when combined, seemed to trigger this weekends outages. We apologize for the large inconvenience, and thank our customer base for their patience.

BurstEmployee · #7 03-02-2004, 00:26

Due to customer feedback, BurstNET Management realizes that many of our customers were not satisfied with the perceived handling of this crisis. We will be meeting to seriously evaluate and discuss the outage and our response to it, as well as to discuss possible solutions for avoiding further problems of this magnitude. Thank you.