# Outbound MMS Delays - AT&T

- Provider: [Bandwidth](https://down.guide/providers/bandwidth)
- Confidence: Confirmed
- Impact: Degraded
- lasted 1h 38m
- started 2026-10-27 14:45 UTC
- MMS Messaging (MM4)
- us
- Bandwidth states the impact was 2026-10-27 11:58 to 15:09 UTC (3h 11m)
- id: DWN-9f856cbb94
- Official page: https://stspg.io/584vsfnqvr30

## Updates from Bandwidth
### 2026-10-27 14:45 UTC: investigating
Bandwidth teams are investigating outbound MMS messages experiencing a delivery delay towards AT&T destinations.

### 2026-10-27 16:22 UTC: resolved
This incident has been resolved.

### 2026-10-28 09:28 UTC: postmortem
Bandwidth has concluded its investigation of this issue and determined that between 11:58 UTC and 15:09 UTC on October 27, 10DLC MMS sent to AT&T was delayed. 
Due to the limited scope of impact, Bandwidth is closing this incident and this will be the extent of the information we will provide for this issue. If you have any questions, please contact us through the Bandwidth support portal. 
We are grateful you have entrusted Bandwidth as your communication partner and we are sorry if this issue resulted in any disruption to your services.

From the builder: does your app depend on Bandwidth? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=bandwidth) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Bandwidth.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-9f856cbb94), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.