- Level
- confirmed
- Worst impact
- Degraded
- Components
- Inbound Calling (SIP) - United States, Outbound Calling (SIP) - United States
- Regions
- us
- Down Index
- 21of 100
What to do
Check whether you use Bandwidth Inbound Calling (SIP) - United States, 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 49m it lasted.
Anything that failed between 2026-09-11 14:51 UTC and 2026-09-11 15: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 3
- investigating
Bandwidth teams are investigating an isolated incident in our LAX Datacenter. Some calls may not complete as expected.
provider
- monitoring
Teams are observing expected network behavior. We 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-de354c3a9c
Is Bandwidth still down?
No, this incident was resolved 2026-09-11 15:40 UTC. For Bandwidth's live state, see https://down.guide/bandwidth.
How long did it last?
49m, from 2026-09-11 14:51 UTC to 2026-09-11 15:40 UTC, by the times Bandwidth posted.
What was affected?
Bandwidth named Inbound Calling (SIP) - United States, 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.