Bandwidth incident

Bandwidth Local Market Impairment - 122 - Manchester, NH

Notice Resolved View vendor source →

Bandwidth experienced a notice incident on October 9, 2026 affecting 122 - Manchester, NH, lasting 2d 12h. The incident has been resolved; the full update timeline is below.

Started
Oct 09, 2026, 08:45 AM UTC
Resolved
Oct 11, 2026, 09:33 PM UTC
Duration
2d 12h
Detected by Pingoru
Oct 09, 2026, 08:45 AM UTC

Affected components

122 - Manchester, NH

Update timeline

  1. investigating Oct 09, 2026, 08:45 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 Oct 09, 2026, 09:43 AM UTC

    We are continuing to investigate this issue.

  3. investigating Oct 09, 2026, 11:45 AM UTC

    We are continuing to investigate this issue.

  4. investigating Oct 09, 2026, 02:53 PM 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.

  5. identified Oct 09, 2026, 03:53 PM UTC

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

  6. identified Oct 09, 2026, 07:56 PM UTC

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

  7. identified Oct 10, 2026, 12:11 AM UTC

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

  8. identified Oct 10, 2026, 04:02 AM UTC

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

  9. identified Oct 10, 2026, 07:59 AM UTC

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

  10. identified Oct 10, 2026, 11:49 AM UTC

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

  11. identified Oct 10, 2026, 03:46 PM UTC

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

  12. identified Oct 10, 2026, 07:54 PM UTC

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

  13. identified Oct 10, 2026, 07:54 PM UTC

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

  14. identified Oct 11, 2026, 01:03 AM UTC

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

  15. identified Oct 11, 2026, 04:45 AM UTC

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

  16. identified Oct 11, 2026, 08:42 AM UTC

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

  17. identified Oct 11, 2026, 01:52 PM UTC

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

  18. monitoring Oct 11, 2026, 06:40 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

  19. resolved Oct 11, 2026, 09:33 PM UTC

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