Skip to main content
Bandwidth

Bandwidth Local Market Impairment - 548 - Wichita Falls, TX

Degraded Lasted 2d 17h · started · Bandwidth's page

Level
confirmed
Worst impact
Degraded
Components
548 - Wichita Falls, TX

What to do

  • Check whether you use Bandwidth 548 - Wichita Falls, TX. 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 2d 17h it lasted.

    Anything that failed between 2026-10-06 17:29 UTC and 2026-10-09 10:41 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 17

  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. identified

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

    provider

  3. identified

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

    provider

  4. identified

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

    provider

  5. identified

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

    provider

  6. identified

    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

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

    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

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

    provider

  14. identified

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

    provider

  15. identified

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

    provider

  16. 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

  17. 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-78bdb7d5b3

Is Bandwidth still down?

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

How long did it last?

2d 17h, from 2026-10-06 17:29 UTC to 2026-10-09 10:41 UTC, by the times Bandwidth posted.

What was affected?

Bandwidth named 548 - Wichita Falls, TX.

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.