Twilio outage on November 15, 2026: Inbound MMS Failures
Twilio reported an incident affecting Twilio for 1 hour 35 minutes on 15 November 2026, from 23:02 to 00:37 UTC.
Resolved
Official incident reported by Twilio
- Started
- 23:02
- 15 Nov 2026 UTC
- Resolved
- 00:37
- 16 Nov 2026 UTC
- Duration
- 1h 35m
- 1 hour 35 minutes
- Impact
- Minor
- as rated by Twilio
- Updates
- 2
- posted by Twilio
Timeline
All times UTC.
Official incident from Twilio
Inbound MMS Failures
-
Official
Investigating
We are investigating an issue with inbound MMS. Users may experience error 12300 when receiving inbound MMS. We will provide another update in 1 hour or as soon as more information becomes available.
-
Official
Resolved
Our engineers have resolved the issue. Inbound MMS processing is returning to normal.
"Official" rows are quoted from Twilio's public status page, status.twilio.com. Very long posts are shortened.
What our checkpoints saw
HostTracker's checkpoints, which test www.twilio.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live Twilio status shows what our checks see right now.
Does your product depend on Twilio?
An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.
You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.
Independent measurement by HostTracker. Not affiliated with Twilio. Official updates are quoted from Twilio's public status page and remain Twilio's own words.