outages.live
Live
TwilioIncident ·

On Call Engineers are Investigating

ResolvedOfficial update
0

Twilio reported a problem with JS client connectivity to the Tokyo edge. Twilio investigated the issue. The issue is now resolved, and it lasted 19 minutes.

State

Resolved

Started

Lasted

19 min

Worst impact

Notice

Timeline

2 updates
18:4418:4918:5318:5819:03
NoticeUpdate postedTimes in UTC

Investigating

19 min 100%

Updates

Times in UTC

As posted by Twilio

Resolved
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.

Twilio in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

109

Days with an incident

47

Median duration

7 h 17 min

This incident

96% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

33 days
median 7 h 17 min
90 days agoToday

Other Twilio incidents

All incidents

Twilio·Voice Call Failures in JP1

Twilio Voice calls fail in JP1. The problem affects Client Web AU1 and PROGRAMMABLE VOICE AU1 - Client Web AU1. Users can fail to make or receive calls with the Voice JavaScript SDK. Twilio identified the issue and reports the state as identified.

Degraded

Twilio·SMS Delivery Failures from Twilio to Turkcell Turkey

Twilio SMS delivery to Turkcell network subscribers in Turkey failed. This affected SMS in Europe and the Carrier Network for SMS in Europe. Twilio reports that the incident is resolved. The outage lasted about 3 hours and 55 minutes.

Resolved

Twilio·Retroactive Incident Impacting Twilio Usage APIs

Twilio Usage APIs were degraded for 6 minutes between 16:42pm and 16:48 Pacific Time on 11/10/2026. During this period of time customers may have experienced 5xx errors. The issue has now been resolved.

Resolved

Twilio·Email Template Editor Issues

Twilio SendGrid Marketing Campaigns had degraded email template editing. HTML entities changed to spaces, links changed, and template content did not render correctly after save or preview. Twilio resolved the issue. The outage lasted 1 hour and 44 minutes.

Resolved

Twilio·SMS Delivery Receipt Delays from Twilio Phone Numbers to Movistar Venezuela

Twilio SMS delivery receipts to Movistar network subscribers in Venezuela were delayed. This affected SMS in Latin America and the carrier network for SMS in Latin America. Twilio reports that the incident is resolved. The incident lasted about 3 hours and 26 minutes.

Resolved

Follow Twilio

Your coding agent knows when Twilio is down, and tells you when a failure is theirs, not yours. You can also get Twilio incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "twilio" and tell me if Twilio has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=twilio
Slack
/feed subscribe https://outages.live/feed.xml?providers=twilio

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane