On 9 November, Twilio ran eight separate incidents across SMS, Voice and WhatsApp, touching routes in Laos, Germany, France, the UK, Italy, Chile and more. The longest, a voice call failure to Chile, ran 19h 21m. Every one of these was logged and fixed on Twilio's side, not yours.
Started
06:57 UTC
Duration
Lasted 16h 8m
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: WhatsApp Messaging, Voice, Latin America, Voice, Europe, SMS, Europe, SMS, APAC
What happened?
Twilio's status page recorded eight distinct incidents starting from 06:57 UTC, spread across SMS delivery, voice calls and WhatsApp Business API, with 49 status updates posted in total. The components affected span SMS in APAC and Europe, Voice in Europe and Latin America, and WhatsApp Messaging. The first incident, SMS delivery failures from Twilio to ETL network subscribers in Laos, opened at 06:57 and ran for 16h 8m before Twilio confirmed recovery and resolution. A separate SMS problem hit a subset of Twilio Long Codes receiving traffic from Germany, lasting 8h 43m with only an opening and a resolved update on the public record. France saw SMS delivery receipt delays to Bouygues Telecom subscribers, where Twilio was explicit that "message delivery may succeed, but delivery receipts may be delayed", a distinction worth noting if your systems depend on receipts rather than just sends. That incident ran 13h 35m. Shorter faults hit SMS to Spusu subscribers in the United Kingdom (3h 28m) and to multiple networks in Italy via alphanumeric sender IDs and long codes (3h 15m). On the voice side, the UK saw silent and one-way audio problems lasting 5h 20m, while calls from a subset of Twilio Phone Numbers to Chile failed for 19h 21m, the longest incident of the day. A WhatsApp Business API incident, opened at 20:32, caused message send errors and was not marked resolved until 13:02 the next day, a span of 16h 30m. No user reports were filed in this window, and Twilio's own updates are the only record of any of this.
Learning
Every one of these incidents sat on specific routes and carriers, from Megacom subscribers in Kyrgyzstan to Bouygues Telecom in France to a subset of numbers reaching Chile, not on Twilio's API as a whole. Our own probes against Twilio's API in the EU and North America showed 100% uptime across the 24 hour, 7 day and 30 day windows, and that reading is accurate: the API that accepts your request was up the entire time. What failed sat downstream, in the carrier interconnects and delivery paths that decide whether a message or call actually lands, and that layer is invisible to a check that only confirms the API answered. This is why a product built on Twilio can show green on every monitor you control while real messages to real countries are silently failing or delayed. The pattern repeats across the day: short, narrow, carrier-specific failures that Twilio catches and fixes well before any status page aggregation would call it a general outage. If you only watch your own endpoints, you have no way to see this kind of regional breakage happening on the other side of the API call. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.