Skip to main content
Bandwidth

Messaging Incident - Verizon Wireless

Degraded Lasted 0m · started · Bandwidth's page

Level
confirmed
Worst impact
Degraded

What to do

  • Check whether your product depends on Bandwidth. 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 0m it lasted.

    Anything that failed between 2026-09-19 12:13 UTC and 2026-09-19 12:11 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 1

  1. resolved

    For a brief period of time outbound messages to Verizon Wireless destination were not delivering as expected. This was investigated and determined to be an off-network incident.

    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-e60495185f

Is Bandwidth still down?

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

How long did it last?

0m, from 2026-09-19 12:13 UTC to 2026-09-19 12:11 UTC, by the times Bandwidth posted.

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.