- Level
- confirmed
- Worst impact
- Degraded
- Components
- 536 - Oklahoma City, OK
What to do
Check whether you use Bandwidth 536 - Oklahoma City, OK. 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 4h 21m it lasted.
Anything that failed between 2026-10-14 05:26 UTC and 2026-10-14 09:47 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 3
- 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
- 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
- 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-716485380d
Is Bandwidth still down?
No, this incident was resolved 2026-10-14 09:47 UTC. For Bandwidth's live state, see https://down.guide/bandwidth.
How long did it last?
4h 21m, from 2026-10-14 05:26 UTC to 2026-10-14 09:47 UTC, by the times Bandwidth posted.
What was affected?
Bandwidth named 536 - Oklahoma City, OK.
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.