Twilio outage on November 11, 2026: On Call Engineers are Investigating
Twilio has reported an incident affecting Twilio since 18:44 UTC on 11 November 2026 (4 hours 9 minutes so far).
Open
Official incident reported by Twilio
- Started
- 18:44
- 11 Nov 2026 UTC
- Status
- Open
- not resolved yet
- Duration
- 4h 9m
- 4 hours 9 minutes so far
- Impact
- -
- as rated by Twilio
- Updates
- 1
- posted by Twilio
Timeline
All times UTC.
Official incident from Twilio
On Call Engineers are Investigating
-
Official
Investigating
Our monitoring systems have detected a potential issues in JS client connectivity to tokyo edge. Our engineers have been alerted and are investigating. We will provide an update when we have more details.
"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.