Skip to main content
Bandwidth

Bandwidth Local Market Impairment - 951 - Rocky Mount, NC

Major outage Lasted 4d 18h · started · Bandwidth's page

Level
confirmed
Worst impact
Major outage
Components
951 - Rocky Mount, NC

What to do

  • Check whether you use Bandwidth 951 - Rocky Mount, NC. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 4d 18h it lasted.

    Anything that failed between 2026-09-13 01:00 UTC and 2026-09-17 19:09 UTC may need a replay.
  • Subscribe to Bandwidth's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=bandwidth works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Bandwidth 29

  1. investigating

    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.

    provider

  2. investigating

    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.

    provider

  3. identified

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

    provider

  4. identified

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

    provider

  5. investigating

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

    provider

  6. investigating

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

    provider

  7. identified

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

    provider

  8. identified

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

    provider

  9. identified

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

    provider

  10. identified

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

    provider

  11. identified

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

    provider

  12. identified

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

    provider

  13. identified

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

    provider

  14. identified

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

    provider

  15. identified

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

    provider

  16. identified

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

    provider

  17. identified

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

    provider

  18. identified

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

    provider

  19. identified

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

    provider

  20. identified

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

    provider

  21. identified

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

    provider

  22. identified

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

    provider

  23. identified

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

    provider

  24. identified

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

    provider

  25. identified

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

    provider

  26. identified

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

    provider

  27. identified

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

    provider

  28. monitoring

    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

    provider

  29. resolved

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

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-0d987f2181

Is Bandwidth still down?

No, this incident was resolved 2026-09-17 19:09 UTC. For Bandwidth's live state, see https://down.guide/bandwidth.

How long did it last?

4d 18h, from 2026-09-13 01:00 UTC to 2026-09-17 19:09 UTC, by the times Bandwidth posted.

What was affected?

Bandwidth named 951 - Rocky Mount, NC.

What caused it?

Bandwidth hasn't published a root cause. If it does, it shows here.

Where does this come from?

Bandwidth's official status page, https://status.bandwidth.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.