- Level
- confirmed
- Worst impact
- Degraded
- Components
- Bandwidth App
- Down Index
- 22of 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 7h 29m it lasted.
Anything that failed between 2026-04-07 13:38 UTC and 2026-04-07 21:07 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
- identified
Bandwidth teams have identified an incident where numbers were erroneously de-provisioned from their assigned campaigns in the Bandwidth App. Teams are working to restore expected settings and messaging behaviors.
provider
- identified
Teams continue to work to resolve this incident.
provider
- resolved
This incident has been resolved. Impacted telephone numbers have been restored to their campaigns.
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-37d2efa91f
Is Bandwidth still down?
No, this incident was resolved 2026-04-07 21:07 UTC. For Bandwidth's live state, see https://down.guide/bandwidth.
How long did it last?
7h 29m, from 2026-04-07 13:38 UTC to 2026-04-07 21:07 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.