Skip to main content
Bandwidth

Outbound MMS Messaging Incident - AT&T

Partial outage Lasted 36m · started · Bandwidth's page

Level
confirmed
Worst impact
Partial outage
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.
  • Confirm your retries, queues and scheduled jobs caught up after the 36m it lasted.

    Anything that failed between 2026-09-30 01:54 UTC and 2026-09-30 02:31 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 2

  1. investigating

    Bandwidth teams are investigating an incident impacting outbound MMS messages towards AT&T destinations. Theses messages are delayed in delivery.

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

Is Bandwidth still down?

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

How long did it last?

36m, from 2026-09-30 01:54 UTC to 2026-09-30 02:31 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.