Twilio favicon

Twilio outage on 2026-11-14

twilio.com
November 2026 14 Minor incident

On 14 November 2026, Twilio logged four separate SMS delivery incidents, each tied to a specific carrier route in a different region. The longest ran 17h 2m, affecting messages sent to MTN subscribers in Nigeria, and the fault sat with the carrier corridor rather than with anything in your own application.

Started

03:52 UTC

Duration

Lasted 9h 6m

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, SMS, Middle East & Africa, SMS, APAC

What happened?

Twilio's status page recorded four incidents starting at 03:52 UTC and running through the day, each scoped to SMS delivery on a single carrier route. The first affected a subset of Twilio numbers sending to Telenor subscribers in Pakistan and ran 9h 6m before resolving. The second, and longest at 17h 2m, affected delivery to MTN subscribers in Nigeria, starting at 12:02 UTC and not resolving until the following day at 05:01 UTC. A third incident hit Orange subscribers in Mali for 4h 26m, and a fourth hit Altan Redes subscribers in Mexico for 11h 27m. Twilio's component list ties this to SMS in three regions: APAC, Middle East & Africa, and Latin America, matching the mix of Pakistan, Nigeria, Mali and Mexico. Each incident followed the same pattern on Twilio's log: investigating, identified, a period of monitoring after a recovery was observed, then resolved. None of the six updates on the Nigeria incident, the longest of the four, named a root cause beyond identifying that the cause was found. No user reports were filed during the window on any of these four incidents. Twilio's own filings are the only record of impact here, since delivery delays to a specific carrier in another country are not something most dashboards surface on their own. With four incidents in one day across four unrelated carrier routes, the pattern points to recurring friction at the interconnect level between Twilio and specific mobile networks, though Twilio does not say so directly on any of the four threads.

Learning

UptimeRobot's own probes against Twilio's API stayed at 100% uptime across the 24 hour, 7 day and 30 day windows, and that is not a contradiction with four SMS incidents happening on the same day. The probes check whether Twilio's API answers, not whether a message handed to that API actually reaches a subscriber on Telenor in Pakistan or MTN in Nigeria. SMS delivery depends on a chain of carrier interconnects downstream of Twilio's API, and a delay or failure on one specific route can sit entirely outside what an API health check measures. This is why a product built on Twilio can show a clean API and a pile of undelivered or delayed messages to one country at the same time. Twilio's 90 day history shows 547 incidents with a median duration of 5 hours 54 minutes, so route-specific delivery delays of this kind are routine rather than exceptional on this platform. If you send SMS through Twilio to these regions, checking your own endpoints only tells you that your code is calling Twilio correctly, not that the message arrived. 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.