On 25 September, Twilio logged seven separate incidents spanning SMS, voice and Verify components, affecting carriers from Arizona to Brazil to the UAE. The longest ran 19 hours 59 minutes. All seven were carrier or feature specific faults on Twilio's side, not a problem you could have fixed from your own stack.
Started
02:24 UTC
Duration
Lasted 19h 59m
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: Verify, SMS Short Code, North America, SMS, Middle East & Africa, Voice, Latin America, Lookup SIM Swap, Legacy Identity MatchAndAttributes, SMS, Latin America
What happened?
Twilio's status page recorded seven incidents starting at 02:24 UTC and running through the day, touching SMS Short Code delivery in North America, SMS to Latin America, Lookup SIM Swap, Legacy Identity MatchAndAttributes, Voice to Latin America, SMS to the Middle East and Africa, and Verify. The longest, SMS delivery delays from a subset of Twilio Short Codes to Cellularone subscribers in NE Arizona, opened at 02:24 and was not marked resolved until 22:23, a span of 19 hours 59 minutes, with Twilio cycling through "identified" updates for most of the day before reporting a recovery at 20:15. A separate SMS delay to Claro in Brazil ran 4 hours 42 minutes. A User Authentication Identity Gateway API failure affecting Verizon in the United States ran 6 hours 13 minutes with only a start and resolve update on record. Voice calls saw post-dial delay to Brazil for 7 hours 50 minutes, and SMS to Etisalat in the United Arab Emirates was delayed for 7 hours 3 minutes. A shorter SMS delivery failure to T-Mobile in the US lasted 2 hours 28 minutes, and a Verify "Try it out" trial feature fault ran 1 hour 27 minutes overnight. Across all seven, Twilio's updates describe symptoms and carrier names but none give a named cause, only "identified" status without detail. There are 40 total status updates logged for the day across these incidents. No user reports were filed in this window on record.
Learning
UptimeRobot's own probes against Twilio's API, checked from the EU and North America, showed 100% uptime over the past 24 hours, 7 days and 30 days, and this incident was not registered against those checks. That is not a contradiction: these faults sat inside specific carrier routes for SMS and voice, and inside identity and Verify features, none of which a generic API uptime check touches. A short code message failing to reach Cellularone subscribers in Arizona, or an SMS stalling en route to Claro in Brazil, can happen while Twilio's core API answers every request correctly. This is the shape to watch for with Twilio: the platform is up, but a lane to a specific carrier or a specific feature is not, and that failure is invisible unless you are tracking message and call outcomes by destination rather than endpoint health. Your own monitoring tells you your service is reachable, it cannot tell you whether a message actually landed on a Brazilian or Emirati handset. UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
