Twilio favicon

Twilio outage on 2026-11-08

twilio.com
November 2026 8 Minor incident

Twilio had two separate verification and messaging outages on 8 November 2026, one lasting 14h 13m and tied to EnStream in Canada, the other lasting 6h 1m and tied to MTN Nigeria. Both were problems on Twilio's side involving its network partners, not your integration.

Started

14:58 UTC

Duration

Lasted 14h 13m

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, Middle East & Africa, Verify Silent Network Auth, Legacy Identity MatchAndAttributes, Lookup Identity Match, Lookup SIM Swap

What happened?

The first incident started at 14:58 UTC and affected Silent Network Authentication and Lookup API transactions routed through EnStream in Canada. Twilio said customers might see verification failures and Lookup API failures, with some transactions falling back to SMS OTP. It took until 16:59 UTC, about two hours in, for Twilio to say it had identified the cause, though it never named what that cause was in any update. Twilio then posted identified-status updates at 18:02 and 20:09 UTC without new detail, each just pushing the next update window out further. Recovery was first noted at 23:00 UTC, and the incident was marked resolved at 05:11 UTC the next day, 14 hours and 13 minutes after it began. The second incident started separately at 23:19 UTC, affecting SMS delivery from Twilio numbers to MTN network subscribers in Nigeria. Twilio initially described it as affecting "multiple networks in multiple countries" before narrowing it to MTN Nigeria specifically at 00:03 UTC. That one identified a cause internally by the same update but, again, did not publish what it was. Recovery was logged at 03:19 UTC and the incident closed at 05:20 UTC, a duration of 6 hours and 1 minute. Five components were listed as affected across the day: Verify Silent Network Auth, Legacy Identity MatchAndAttributes, Lookup Identity Match, Lookup SIM Swap, and SMS for Middle East and Africa. No user reports were filed during either window on this page, and Twilio has not published any post-mortem for either incident.

Learning

UptimeRobot's own probes against Twilio's API, run from EU and NA regions, showed 100% uptime across 24 hours, 7 days and 30 days, and this incident was not registered as an outage event in that probe history. That is not a contradiction. Both failures here were carrier-specific: one ran through EnStream's network path into Canada, the other through MTN's network path into Nigeria, so a generic API health check can return green while verification requests or SMS messages fail once they hit that specific carrier route. This is the shape to recognise in your own product: the API endpoint answers fine, but a subset of real end-user transactions, filtered by country or carrier, silently fail downstream. Watching your own endpoints only tells you that your calls to Twilio succeeded, not that the SMS or verification actually reached the subscriber. Twilio's status updates confirm this pattern by repeatedly scoping the issue to one carrier in one country rather than the whole API. 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.