Twilio logged seven separate incidents on 11 November 2026, mostly SMS and MMS delivery problems to specific carriers in Turkey, Kazakhstan, Tajikistan and the United States, plus a Voice JavaScript SDK issue in Japan. The longest ran 16 hours 30 minutes, and the fault sat with Twilio's delivery paths to third-party networks, not with your own integration.
Started
12:55 UTC
Duration
Lasted 3h 58m
Source
IsDown
Next time
Twilio is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: SMS, APAC, MMS Long Code, North America, Client Web AU1, SMS, Europe
What happened?
Across the day Twilio's status page recorded seven incidents touching four components: SMS in Europe, Client Web AU1, SMS in APAC, and MMS Long Code in North America. The first began at 12:55 UTC, SMS delivery failures from Twilio to Turkcell subscribers in Turkey, resolved in 3 hours 58 minutes. A short-lived JS client connectivity issue to the Tokyo edge followed at 18:44, logged for 17 minutes with only one update ever filed. Voice call failures tied to the Voice JavaScript SDK in JP1 ran from 18:58 to 21:40, taking 3 hours 51 minutes to clear. Later in the evening, three carrier-specific SMS and MMS problems overlapped: delivery failures to K-Cell in Kazakhstan (7h 27m), MMS delays to multiple US networks on a subset of long codes (16h 30m, the longest of the day), and delivery failures to Tcell in Tajikistan (11h 21m). A seventh incident, SMS delays to MTS in Kazakhstan, started at 23:18 and ran 14 hours 9 minutes, working through investigating, identified and monitoring stages before resolution. Across all seven, Twilio's own language stayed consistent: "may be experiencing" delivery failures or delays, each tied to a specific destination network rather than to Twilio's platform broadly. Twilio filed 38 status updates in total, and no post-mortem has been published for any of these incidents. No user reports were filed during the window on this page's record.
Learning
Every incident on this page was scoped to delivery between Twilio and a specific downstream carrier network, in Turkey, Kazakhstan, Tajikistan or across the US, rather than a fault in Twilio's API itself. UptimeRobot's own probes against Twilio's API, run from EU and NA regions, show 100% uptime over 24 hours, 7 days and 30 days, and this incident was not registered against those probes. That is not a contradiction. An external check against an API endpoint confirms the endpoint answers; it says nothing about whether an SMS handed off to Turkcell or K-Cell actually lands on a handset. This is the shape to recognise in your own product: your messages can queue, delay or fail on the carrier side while every health check you run against Twilio keeps returning green, because the check and the failure are watching different layers entirely. If your users report messages not arriving, checking Twilio's API status alone will not tell you why. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.