Media Streams Audio Delays
Twilio Media Streams audio delays affect Media Streams US1 and PROGRAMMABLE VOICE US1 in the US1 region. Twilio reports that it is investigating the problem.
State
Investigating
Started
1 h ago
2026-11-03 01:29 UTC
Ongoing for
1 h
Worst impact
Degraded
Timeline
1 updateInvestigating
1 h 100%
Updates
Times in UTCAs posted by Twilio
We are investigating media streams audio delays. We expect to provide another update in 1 hour or as soon as more information becomes available
Affected components
2Twilio in the last 90 days
Full historyIncidents in 90 days
63
Days with an incident
39
Median duration
6 h 53 min
This incident
85% shorter than the median
Other Twilio incidents
All incidentsTwilio·Voice Call Audio Delays
Twilio Voice in North America has audio delays and high packet loss. The CARRIER NETWORK for Voice in North America is also affected. Twilio reports that it is investigating the issue.
Twilio·RateQueue Host Down Did Not Recover
The Twilio SMS component and Programmable Messaging - SMS have degraded performance. Twilio reports delays in messages presented, and no messages are lost. Twilio is investigating this incident.
Twilio·SMS Delivery Delays and Failures from Twilio to Claro Puerto Rico
Twilio reports SMS delivery delays and failures to Claro network subscribers in Puerto Rico. The problem affects SMS in Latin America and the carrier network for SMS in Latin America. Twilio identified the cause and continues to work on a fix.
Twilio·SMS Delivery Receipt Delays from a Subset of Twilio Short Codes to Liberty Puerto Rico
Twilio reports SMS delivery receipt delays from a subset of Twilio Short Codes to Liberty network subscribers in Puerto Rico. This affects SMS in Latin America and the carrier network for SMS in Latin America. Twilio has identified the cause and is working to resolve the issue. Message delivery may succeed, but delivery receipts may be delayed.
Twilio·Voice Call One-Way Audio from Brazil to a Subset of Twilio Numbers
On October 31, 2026, from 5AM to 8AM PT, customers may have experienced an issue with some inbound calls to Twilio Brazil numbers having no audio, and some calls also dropping. The impact was linked to a carrier fiber cut and a fallback route that could not handle the traffic load. The issue has been resolved and Voice is operating normally.
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.
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.
https://outages.live/feed.xml?providers=twilio/feed subscribe https://outages.live/feed.xml?providers=twilioFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane