Messaging Delays - AT&T

What to do

• Check whether you use Bandwidth SMS Messaging (SMPP), MMS Messaging (MM4), REST APIs - HTTP SMS Messaging, REST APIs - HTTP MMS Messaging. 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 1d 1h it lasted.

  Anything that failed between 2026-05-11 12:16 UTC and 2026-05-12 13:35 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 6

1. investigatingMay 11, 2026, 12:16 PM UTC

   Bandwidth teams are investigating an incident impacting Inbound and Outbound messaging delays to and from AT&T destinations. Teams are working to restore expected delivery with this carrier.

   provider

2. monitoringMay 11, 2026, 2:06 PM UTC

   Teams are observing expected message deliverability at this time and will monitor for prolonged stability.

   provider

3. identifiedMay 11, 2026, 3:02 PM UTC

   Teams have identified the source of the delay and are working to restored expected messaging behavior.

   provider

4. identifiedMay 11, 2026, 6:45 PM UTC

   Teams continue to investigate this incident.

   provider

5. monitoringMay 12, 2026, 12:50 AM UTC

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

   provider

6. resolvedMay 12, 2026, 1:35 PM 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.