Bandwidth incident

Bandwidth Local Market Impairment - 951 - Rocky Mount, NC

Critical Ongoing View vendor source →

Bandwidth is currently experiencing a critical incident affecting 951 - Rocky Mount, NC, which began 2d ago. The vendor's full update timeline is below.

Started
Sep 13, 2026, 01:00 AM UTC
Resolved
Ongoing
Duration
● 2d 5h
Detected by Pingoru
Sep 13, 2026, 01:00 AM UTC

Affected components

951 - Rocky Mount, NC

Update timeline

  1. investigating Sep 13, 2026, 01:00 AM UTC

    We are experiencing an impairment on the Bandwidth network which may affect a portion of calls. We are currently working with our carrier for resolution.

  2. investigating Sep 13, 2026, 04:59 AM UTC

    We are experiencing an impairment on the Bandwidth network which may affect a portion of calls. We are currently working with our carrier for resolution.

  3. identified Sep 13, 2026, 07:51 AM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  4. identified Sep 13, 2026, 11:22 AM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  5. investigating Sep 13, 2026, 03:22 PM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  6. investigating Sep 13, 2026, 07:33 PM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  7. identified Sep 13, 2026, 09:11 PM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  8. identified Sep 14, 2026, 12:50 AM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  9. identified Sep 14, 2026, 09:01 AM UTC

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

  10. identified Sep 14, 2026, 09:09 AM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  11. identified Sep 14, 2026, 10:13 AM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  12. identified Sep 14, 2026, 02:13 PM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  13. identified Sep 14, 2026, 06:13 PM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  14. identified Sep 14, 2026, 10:14 PM UTC

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

  15. identified Sep 15, 2026, 03:37 AM UTC

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