- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Bandwidth App
- Down Index
- 30of 100
What to do
Check whether you use Bandwidth Bandwidth App. 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 3h 32m it lasted.
Anything that failed between 2026-04-12 01:08 UTC and 2026-04-12 04:40 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 4
- identified
Bandwidth teams have identified an incident within the Bandwidth App and API where available Number Inventory may not display accurately leading to incomplete number orders. Teams are working to restore expected numbers order and inventory behavior.
provider
- identified
We continue to work to restore expected portal behavior.
provider
- monitoring
Teams are observing expected portal and inventory behavior. Teams will monitor for stability.
provider
- resolved
This incident has been 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-0c91e01c12
Is Bandwidth still down?
No, this incident was resolved 2026-04-12 04:40 UTC. For Bandwidth's live state, see https://down.guide/bandwidth.
How long did it last?
3h 32m, from 2026-04-12 01:08 UTC to 2026-04-12 04:40 UTC, by the times Bandwidth posted.
What was affected?
Bandwidth named Bandwidth App.
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.