Twilio favicon

Twilio outage on 2026-11-06

twilio.com
November 2026 6 Minor incident

Twilio logged eight separate incidents on 6 November 2026, touching SMS delivery in Europe and Latin America, voice calls to Colombia and Chile, Console notification logs, and a documentation page. One of them, SMS delivery receipt delays to Chile, was still open as the day closed. All eight were faults on Twilio's side, not yours.

Started

01:23 UTC

Duration

Lasted 8h 56m

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, Documentation, Voice, Latin America, Conversations, Notify, SMS, Europe

What happened?

Twilio's status page recorded eight incidents starting at 01:23 UTC and continuing through the day. The first was SMS delivery delays between Twilio and T-Mobile subscribers in the Czech Republic, open for 8h 56m before resolution at 10:19 UTC. Two incidents affected Console notification logs: one lasted 1h 38m after logs stopped populating new data from around 04:25 UTC, and a second, shorter one was mitigated within 8 minutes. In the afternoon, Twilio reported voice call audio quality degradation from a subset of its mobile numbers to Claro subscribers in Colombia, resolved in 40 minutes, followed closely by voice call failures to Chile lasting 3h 49m. A documentation page error sent users following ConversationRelay links into an unexpected Console login prompt, a bug unrelated to call or message delivery, fixed after 2 hours. SMS delivery delays from Twilio to Claro in the Dominican Republic ran for 3h 50m. The last incident, SMS delivery receipt delays from a subset of Twilio long codes to multiple Chilean networks, started at 21:21 UTC and was still open at 02:22 UTC the next day, the last update Twilio published, with 47 status updates logged against it in total. Twilio's updates describe the cause as identified but do not spell out what it was. No user reports were filed in the window covered by this record. Across all eight incidents, the pattern is regional and carrier-specific: single countries, single carriers, or a single documentation page, rather than a platform-wide failure.

Learning

UptimeRobot's own checks against Twilio's API, run from Europe and North America every 60 seconds, stayed at 100% uptime over 24 hours, 7 days and 30 days, and none of these incidents registered against that probe. That is not a contradiction. These failures sat in the delivery paths between Twilio and specific mobile carriers in the Czech Republic, Colombia, Chile and the Dominican Republic, and in Console features like notification logs and documentation, none of which a simple API reachability check would ever touch. Your own monitoring of your integration would most likely have shown the same green result, because your calls to Twilio's API were probably succeeding even while messages sat delayed on a carrier's network or call audio degraded on a specific route. This is the shape to recognise: the API accepts your request and still reports success, while the actual SMS or voice call fails somewhere downstream, on a leg you cannot see from your own endpoint. Twilio's own history shows 547 incidents in the past 90 days with a median duration of 5 hours 57 minutes, so this kind of regional, carrier-specific fault is routine for them, not exceptional. 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.