MOREnet incident

Brightspeed Outage #507390367

Notice Resolved View vendor source →

MOREnet experienced a notice incident on March 17, 2026 affecting MOREnet Internet and Carrier Network, lasting 14h 45m. The incident has been resolved; the full update timeline is below.

Started
Mar 17, 2026, 11:57 AM UTC
Resolved
Mar 18, 2026, 02:42 AM UTC
Duration
14h 45m
Detected by Pingoru
Mar 17, 2026, 11:57 AM UTC

Affected components

MOREnet InternetCarrier Network

Update timeline

  1. investigating Mar 17, 2026, 11:57 AM UTC

    Sites: NE Vernon SD Description: THere is a service disruption in Rockville, MO. The Brightspeed Network Operations Center (NOC) is actively engaged in diagnosing the problem to ascertain its cause. Will provide updates as given.

  2. investigating Mar 17, 2026, 01:47 PM UTC

    A technician has been dispatched to the fault location to investigate and identify the root cause of the issue. An estimated time of arrival is not available at this time.

  3. investigating Mar 17, 2026, 02:42 PM UTC

    Field Operations has arrived at the Schell central office to conduct light level testing to determine the source of the service disruption

  4. monitoring Mar 17, 2026, 04:28 PM UTC

    Brightspeed is reporting a fiber fault, however our sites recovered shortly after crews arrived at central office. As I have not received an all clear from the vendor, I will place us in monitoring mode until I hear otherwise.

  5. monitoring Mar 17, 2026, 04:28 PM UTC

    no all clear given as they are still investigating a fiber cut in the area.

  6. identified Mar 17, 2026, 05:20 PM UTC

    The fiber repair crew has located a frozen splice case at the fault point and is actively working to restore service.

  7. identified Mar 17, 2026, 06:43 PM UTC

    The technicians are working on the case after determining that all of the splices were bad. Network Operations is monitoring alarms as work continues

  8. identified Mar 17, 2026, 08:55 PM UTC

    We are continuing to work on a fix for this issue.

  9. resolved Mar 18, 2026, 02:42 AM UTC

    This incident has been resolved.