- Level
- confirmed
- Worst impact
- Major outage
- Components
- 658 - Colorado Springs, CO
What to do
Check whether you use Bandwidth 658 - Colorado Springs, CO. 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 10h 11m it lasted.
Anything that failed between 2026-10-27 04:45 UTC and 2026-10-27 14:56 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.
Root cause
Our carrier has identified the cause of this incident and is working to complete repairs.Read the postmortem
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
- identified
Our carrier has identified the cause of this incident and is working to complete repairs.
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-6d2bedc036
Is Bandwidth still down?
No, this incident was resolved 2026-10-27 14:56 UTC. For Bandwidth's live state, see https://down.guide/bandwidth.
How long did it last?
10h 11m, from 2026-10-27 04:45 UTC to 2026-10-27 14:56 UTC, by the times Bandwidth posted.
What was affected?
Bandwidth named 658 - Colorado Springs, CO.
What caused it?
Bandwidth wrote: "Our carrier has identified the cause of this incident and is working to complete repairs." The postmortem: https://stspg.io/qwlbrhyg521w
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.