- Level
- confirmed
- Worst impact
- Degraded
- Components
- Inbound Calling (SIP) - United States, Outbound Calling (SIP) - United States
- Regions
- us
- Down Index
- 23of 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 1h 58m it lasted.
Anything that failed between 2026-07-11 01:50 UTC and 2026-07-11 03:48 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 incident impacting a small subset of calls transversing our DFW datacenter. Teams are working to restore expected network behavior.
provider
- monitoring
Teams are observing expected network behavior and 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-f0cd9eaa7d
Is Bandwidth still down?
No, this incident was resolved 2026-07-11 03:48 UTC. For Bandwidth's live state, see https://down.guide/bandwidth.
How long did it last?
1h 58m, from 2026-07-11 01:50 UTC to 2026-07-11 03:48 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.