Skip to main content

Twilio outage on October 22, 2026: Issue with Realtime Transcriptions and Deepgram

Twilio reported an incident affecting Twilio for 1 hour 36 minutes on 22 October 2026, from 16:32 to 18:08 UTC.

www.twilio.com All times UTC

Resolved

Official incident reported by Twilio

Started
16:32
22 Oct 2026 UTC
Resolved
18:08
22 Oct 2026 UTC
Duration
1h 36m
1 hour 36 minutes
Impact
-
as rated by Twilio
Updates
3
posted by Twilio

Timeline

All times UTC.

Official incident from Twilio

Issue with Realtime Transcriptions and Deepgram

Resolved 22 Oct 2026 16:32 UTC View on Twilio's status page
  1. Official
    Investigating

    Our monitoring systems have detected a potential issue with realtime transcription and Deepgram. Our engineers have been alerted and are investigating. We will provide an update when we have more details. Customers are recommended to move to Google as a temporary workaround until we have additional details.

  2. Official
    Monitoring

    We have mitigated the issue and are monitoring system performance. Speech recognition for Voice calls is returning to normal. We will provide another update in 30 minutes or as soon as more information becomes available.

  3. Official
    Resolved

    The issue affecting realtime transcriptions and Deepgram has been resolved, and the service is functioning 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.