- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Outbound Calling - Netherlands
What to do
Check whether you use Bandwidth Outbound Calling - Netherlands. 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 19m it lasted.
Anything that failed between 2026-07-27 12:33 UTC and 2026-07-27 16:52 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
Bandwith teams are investigating an outbound calling incident, impacting Netherlands based phone calls. These outbound calls may not complete as expected at this time
provider
- identified
Teams have identified the source of this incident and working to restore expected calling behaviors.
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-ca556bab59
Is Bandwidth still down?
No, this incident was resolved 2026-07-27 16:52 UTC. For Bandwidth's live state, see https://down.guide/bandwidth.
How long did it last?
4h 19m, from 2026-07-27 12:33 UTC to 2026-07-27 16:52 UTC, by the times Bandwidth posted.
What was affected?
Bandwidth named Outbound Calling - Netherlands.
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.