Twilio favicon

Twilio outage on 2026-11-07

twilio.com
November 2026 7 Minor incident

On 7 November Twilio ran four separate SMS delivery receipt incidents affecting networks in New Zealand, India, the United States and the Philippines. The longest, affecting Short Codes in New Zealand, took 51h 31m to resolve. All four faults sat on Twilio's side of the connection.

Started

02:57 UTC

Duration

Lasted 2d 3h

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, APAC, SMS Short Code, North America, SMS Long Code, North America

What happened?

Twilio's status page logged four incidents starting at 02:57 UTC, each tied to SMS delivery receipts rather than message delivery itself. The first affected a subset of Short Codes sending to multiple networks in New Zealand, took 51h 31m to resolve, and ran through ten updates before Twilio confirmed resolution at 06:26 UTC. Twilio was explicit throughout that "message delivery may succeed, but delivery receipts may be delayed", a distinction worth holding onto, since the underlying texts were likely arriving even while confirmation of that arrival was stuck. A second incident, delivery delays from Twilio to multiple networks in India, started at 13:00 UTC and resolved in 3h 41m. A third, covering Long Codes and Short Codes to networks across the United States, started at 19:37 UTC and ran 21h 38m before resolving. A fourth, affecting Globe Philippines specifically, started at 21:22 UTC and resolved in 13h 20m after three separate "monitoring" updates each reporting an observed recovery before Twilio finally closed it. Across the day Twilio filed 29 updates and touched three listed components: SMS APAC, SMS Short Code North America and SMS Long Code North America. No post-mortem has been published for any of the four incidents, and Twilio's own text never names a root cause, only that one was "identified" internally. No user reports were filed during the window on this page.

Learning

Twilio's own probes for this period show 100% uptime on the API component across both EU and North America regions, which is accurate for what it measures: the API endpoint stayed reachable the whole time. What broke sat one layer downstream, in the confirmation loop between Twilio and carrier networks that tells you whether a text actually landed on a handset. An uptime check against Twilio's API cannot see that loop, because the API call that sends the message succeeds regardless of what happens afterwards on the carrier side. That is why your own monitoring can show green while customers in New Zealand, India, the US or the Philippines wait on delivery receipts that never arrive on time. If your product depends on those receipts to trigger anything downstream, like retries or billing, a delay like this looks identical to silence on your end. 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.