Skip to main content
Bandwidth

MMS Incident

Degraded Lasted 2h 46m · started · Bandwidth's page

Level
confirmed
Worst impact
Degraded
Components
MMS Messaging (MM4)
Down Index
20of 100

What to do

  • Check whether you use Bandwidth MMS Messaging (MM4). 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 2h 46m it lasted.

    Anything that failed between 2026-04-22 11:58 UTC and 2026-04-22 14:44 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. investigating

    Bandwidth teams are currently investigating an incident impacting MMS DLRs. These DLRs are delayed in population.

    provider

  2. monitoring

    Teams are observing expected network performance. We will monitor for continued stability.

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

Is Bandwidth still down?

No, this incident was resolved 2026-04-22 14:44 UTC. For Bandwidth's live state, see https://down.guide/bandwidth.

How long did it last?

2h 46m, from 2026-04-22 11:58 UTC to 2026-04-22 14:44 UTC, by the times Bandwidth posted.

What was affected?

Bandwidth named MMS Messaging (MM4).

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.