Bandwidth incident

Bandwidth Local Market Impairment - 951 - Rocky Mount, NC

Resolved after 4 days 18 hours, affecting 951 - Rocky Mount, NC, on September 13, 2026.

resolved Sep 17, 2026, 07:09 PM UTC

Our carrier has completed all necessary repairs and Bandwidth can confirm all services are restored. This incident is resolved.

Started
Sep 13, 2026, 01:00 AM UTC
Resolved
Sep 17, 2026, 07:09 PM UTC
Duration
4d 18h
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.

  16. identified Sep 15, 2026, 01:11 PM UTC

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

  17. identified Sep 15, 2026, 05:00 PM UTC

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

  18. identified Sep 15, 2026, 11:04 PM UTC

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

  19. identified Sep 16, 2026, 02:58 AM UTC

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

  20. identified Sep 16, 2026, 06:40 AM UTC

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

  21. identified Sep 16, 2026, 10:29 AM UTC

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

  22. identified Sep 16, 2026, 01:42 PM UTC

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

  23. identified Sep 16, 2026, 06:27 PM UTC

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

  24. identified Sep 16, 2026, 10:30 PM UTC

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

  25. identified Sep 17, 2026, 02:27 AM UTC

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

  26. identified Sep 17, 2026, 07:16 AM UTC

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

  27. identified Sep 17, 2026, 11:22 AM UTC

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

  28. monitoring Sep 17, 2026, 03:42 PM UTC

    We have observed services in this market have recovered and our carrier is finalizing repairs. This incident will be resolved when we confirm all repairs are complete

  29. resolved Sep 17, 2026, 07:09 PM UTC

    Our carrier has completed all necessary repairs and Bandwidth can confirm all services are restored. This incident is resolved.

Your product runs on more than Bandwidth

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →