- Level
- confirmed
- Worst impact
- Major outage
- Components
- Outbound Calling (SIP) - United States
- Regions
- us
- Down Index
- 47of 100
What to do
Check whether you use Bandwidth Outbound Calling (SIP) - United States in us. 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 36m it lasted.
Anything that failed between 2026-04-08 11:01 UTC and 2026-04-08 15:36 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
Some customers may experience outbound call failures when routing via our JFK Datacenter. These calls may be retried via ATL. Teams are working to restore expected network connectivity.
provider
- monitoring
Teams are observing expected network behavior. We will continue to 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-c825a32656
Is Bandwidth still down?
No, this incident was resolved 2026-04-08 15:36 UTC. For Bandwidth's live state, see https://down.guide/bandwidth.
How long did it last?
4h 36m, from 2026-04-08 11:01 UTC to 2026-04-08 15:36 UTC, by the times Bandwidth posted.
What was affected?
Bandwidth named Outbound Calling (SIP) - United States in us.
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.