United States SMS and MMS Carrier Maintenance - AT&T
The AT&T network in the United States is conducting a planned maintenance from 04 November 2026 at 18:00 PST until 05 November 2026 at 03:00 PST. During the maintenance window, there could be intermittent delays delivering SMS and MMS to and from AT&T United States handsets when sending via long codes and short codes.
The latest update from Twilio.
State
Scheduled
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Twilio
The AT&T network in the United States is conducting a planned maintenance from 04 November 2026 at 18:00 PST until 05 November 2026 at 03:00 PST. During the maintenance window, there could be intermittent delays delivering SMS and MMS to and from AT&T United States handsets when sending via long codes and short codes.
Affected components
8Twilio in the last 90 days
Full historyIncidents in 90 days
71
Days with an incident
40
Median duration
7 h 20 min
This incident
Not comparable
Other Twilio incidents
All incidentsTwilio·MMS Delivery Failures from a Subset of Twilio Long Codes to GCI United States
Twilio MMS delivery failures affect a subset of Twilio Long Codes and the carrier network for GCI subscribers in the United States. Twilio reports that it is investigating this issue.
Twilio·MMS Delivery Delays from a Subset of Twilio Long Codes to Multiple Small Networks in United States
Twilio reports MMS delivery delays from a subset of Twilio Long Codes to network subscribers on multiple small networks in the United States. The MMS Long Code components in North America are affected. Twilio has identified the cause and continues to work on a fix. Message delivery may succeed, but delivery receipts may be delayed.
Twilio·MMS Delivery Delays and Delivery Receipt Delays from a Subset of Twilio Long Codes and Short Codes to AT&T United States
MMS delivery and MMS delivery receipts do not work correctly for some Twilio Long Codes and Short Codes to AT&T subscribers in the United States. Twilio reports that it identified the cause and now monitors service stability after a recovery.
Twilio·MMS Delivery Delays and Failures from a Subset of Twilio Short Codes to T-Mobile and Verizon United States
MMS delivery delays and failures affected a subset of Twilio Short Codes to T-Mobile and Verizon subscribers in the United States. Twilio reports that the incident is resolved. The incident lasted about 6 hours and 18 minutes.
Twilio·SMS Delivery Delays from a Subset of Twilio Short Codes and Long Codes to Brisanet Brazil
Twilio SMS delivery delays affected a subset of Short Codes and Long Codes to Brisanet subscribers in Brazil. The SMS and Carrier Network SMS services in Latin America were degraded. The incident is resolved and lasted about 14 hours and 47 minutes.
Follow Twilio
Your coding agent knows when Twilio is down, and tells you when a failure is theirs, not yours. You can also get Twilio incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "twilio" and tell me if Twilio has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=twilio/feed subscribe https://outages.cc/feed.xml?providers=twilioFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane