Twilio favicon

Twilio outage on 2026-11-13

twilio.com
November 2026 13 Minor incident

Twilio logged seven separate incidents on 13 November 2026, touching voice trunking, SMS delivery, and identity verification across different regions. None of them were caused by anything on your side, and one, an SMS delay to a Brazilian carrier, was still open well past the day's end.

Started

02:33 UTC

Duration

Lasted 28m

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, Latin America, Voice, Latin America, SMS, APAC, Legacy Identity MatchAndAttributes, Lookup SIM Swap, Verify Silent Network Auth, Lookup Identity Match, Termination US1

What happened?

Twilio's status page recorded seven incidents starting at 02:33 UTC and running through the day. The first was a 28 minute Elastic SIP Trunking fault affecting voice calls, resolved by 03:02. Two separate SMS issues hit short codes and delivery receipts to networks in India within the same early morning window, one lasting 3h 14m and the other 50m. Later in the day a Silent Network Authentication and Lookup API failure in the United Kingdom ran for 5h 13m, with Twilio noting that affected transactions could fail over to secondary methods like SMS OTP. A second India SMS delay, started at 15:37, ran for 56h 4m, well beyond the calendar day. A voice call failure affecting Colombia, Mexico, Chile, and Costa Rica lasted 21h 39m. The longest-running incident, SMS delivery delays from Twilio to Brisanet in Brazil, started at 22:36 and was still open at 16:19 UTC on the next cycle, the last update shown, with Twilio cycling between "identified" and "monitoring" multiple times without a final resolution posted in the updates available. Across all seven incidents Twilio logged 54 status updates in total. No user reports were filed in the window covered here. Twilio's own updates are the only record of impact; no independent post-mortem has been published for any of these.

Learning

UptimeRobot's own probes against Twilio's API, run from the EU and North America, stayed at 100% uptime across the last 24 hours, 7 days and 30 days, and did not register this incident at all. That is not a contradiction. These failures sat in specific regional paths, voice trunking, SMS routing to particular carriers in India and Brazil, and identity lookups in the UK, none of which a generic API health check from outside those corridors would ever touch. A provider's core API can answer every ping correctly while the actual message or call it is meant to carry fails somewhere downstream, on a carrier interconnect or regional gateway that your monitoring never sees directly. If your product sends SMS or places calls through Twilio into any of the affected countries, your customers could have been stuck for hours while every dashboard you control looked green. That is the gap this kind of outage exposes: your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.