- Level
- confirmed
- Worst impact
- Degraded
- Components
- Inbound Calling - Germany, Outbound Calling - Germany
What to do
Check whether you use Bandwidth Inbound Calling - Germany, Outbound Calling - Germany. 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 22h 37m it lasted.
Anything that failed between 2026-07-30 16:28 UTC and 2026-07-31 15:05 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
- investigating
Teams are investigating an Inbound and Outbound calling incident for German based calls. These calls may not complete as expected.
provider
- investigating
We are continuing to investigate this issue.
provider
- identified
Teams have identified the source of this incident and continue work to resolve this incident.
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-bb298365b5
Is Bandwidth still down?
No, this incident was resolved 2026-07-31 15:05 UTC. For Bandwidth's live state, see https://down.guide/bandwidth.
How long did it last?
22h 37m, from 2026-07-30 16:28 UTC to 2026-07-31 15:05 UTC, by the times Bandwidth posted.
What was affected?
Bandwidth named Inbound Calling - Germany, Outbound Calling - Germany.
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.