Skip to main content
Bandwidth

Outbound UK Voice Incident

Degraded Lasted 7h 23m · started · Bandwidth's page

Level
confirmed
Worst impact
Degraded
Components
Outbound Calling - United Kingdom

What to do

  • Check whether you use Bandwidth Outbound Calling - United Kingdom. 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 7h 23m it lasted.

    Anything that failed between 2026-03-24 11:44 UTC and 2026-03-24 19:08 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

  1. identified

    Teams have identified an Outbound UK Voice incident impacting UK based traffic where some calls may fail to complete as expected. Teams are working to restore expected network behavior.

    provider

  2. monitoring

    Teams are observing expected network behavior. We will continue to monitor.

    provider

  3. 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-2152ca4c80

Is Bandwidth still down?

No, this incident was resolved 2026-03-24 19:08 UTC. For Bandwidth's live state, see https://down.guide/bandwidth.

How long did it last?

7h 23m, from 2026-03-24 11:44 UTC to 2026-03-24 19:08 UTC, by the times Bandwidth posted.

What was affected?

Bandwidth named Outbound Calling - United Kingdom.

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.