Skip to main content
Bandwidth

MMS Failures

Maintenance Lasted 1h 56m · started · Bandwidth's page

Level
confirmed
Worst impact
Maintenance
Components
MMS Messaging (MM4)

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.
  • Check that everything you run on Bandwidth came back after the window closed 2026-04-08 10:57 UTC.

  • 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 2

  1. monitoring

    For a brief period of time, some MMS messages towards AT&T may have failed to deliver as expected. Teams are observing expected network performance and are monitoring for stability.

    provider

  2. 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-09e41cd6dd

Is this Bandwidth maintenance still going on?

No, it ended 2026-04-08 10:57 UTC.

How long did it last?

1h 56m, from 2026-04-08 09:01 UTC to 2026-04-08 10:57 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.