Skip to main content

Twilio outage on November 11, 2026: Voice Call Failures in JP1

Twilio reported an incident affecting Twilio for 3 hours 51 minutes on 11 November 2026, from 18:58 to 22:50 UTC.

www.twilio.com All times UTC

Resolved

Official incident reported by Twilio

Started
18:58
11 Nov 2026 UTC
Resolved
22:50
11 Nov 2026 UTC
Duration
3h 51m
3 hours 51 minutes
Impact
Minor
as rated by Twilio
Updates
6
posted by Twilio

Timeline

All times UTC.

Official incident from Twilio

Voice Call Failures in JP1

Resolved Minor impact 11 Nov 2026 18:58 UTC View on Twilio's status page
  1. Official
    Investigating

    We are investigating an issue with Voice services in JP1. Users may experience failures when making or receiving calls using the Voice JavaScript SDK. We will provide another update in 1 hour or as soon as more information becomes available.

  2. Official
    Identified

    We have identified an issue with Voice services in JP1. Users may experience failures when making or receiving calls using the Voice JavaScript SDK. We will provide another update in 2 hours or as soon as more information becomes available.

  3. Official
    Identified

    We are investigating an issue with Voice services in JP1. Users may experience failures when making or receiving calls using the Voice JavaScript SDK. We will provide another update in 37 minutes or as soon as more information becomes available.

  4. Official
    Identified

    We are investigating an issue with Voice services in JP1. Users may experience failures when making or receiving calls using the Voice JavaScript SDK. We will provide another update in 4 hours or as soon as more information becomes available.

  5. Official
    Monitoring

    Voice services in JP1 are now operating normally. We will continue to monitor for system stability. We'll provide another update in 1 hour or as soon as more information becomes available.

  6. Official
    Resolved

    The issue affecting Voice services in JP1 has been resolved and is operating normally at this time.

"Official" rows are quoted from Twilio's public status page, status.twilio.com. Very long posts are shortened.

What our checkpoints saw

HostTracker's checkpoints, which test www.twilio.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live Twilio status shows what our checks see right now.

Does your product depend on Twilio?

An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.

You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.

Independent measurement by HostTracker. Not affiliated with Twilio. Official updates are quoted from Twilio's public status page and remain Twilio's own words.