Inbound MMS Messaging Incident

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 2d it lasted.

  Anything that failed between 2026-05-18 09:57 UTC and 2026-05-20 10:48 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 5

1. investigatingMay 18, 2026, 9:57 AM UTC

   Bandwidth teams are investigating an inbound MMS messaging incident. Messages from AT&T and Verizon intermittently fail to reach the Bandwidth network. Teams are working with the impacted industry vendor.

   provider

2. identifiedMay 18, 2026, 12:50 PM UTC

   The source of the incident has been identified as an off network industry incident. We continue to work with industry partners to restore expected messaging behavior.

   provider

3. identifiedMay 19, 2026, 10:40 AM UTC

   Bandwidth teams continue to escalate with impacted industry counterparts to restore expected messaging behavior.

   provider

4. monitoringMay 19, 2026, 11:19 AM UTC

   Teams are observing expected inbound delivery of inbound MMS messages. We will monitor for stability.

   provider

5. resolvedMay 20, 2026, 10:48 AM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.