Voice Call Post Dial Delay from a Subset of Twilio Phone Numbers to United States
Twilio Voice and carrier network voice in North America had post dial delay on calls from some Twilio phone numbers to United States subscribers. Twilio identified the cause and resolved the incident. The outage lasted 30 minutes.
State
Resolved
Started
Lasted
30 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
23 min 76%
Identified
7 min 24%
Updates
Times in UTCAs posted by Twilio
The incident has been resolved and voice calls from a subset of Twilio Phone Numbers to network subscribers in the United States are operating normally.
Twilio customers may be experiencing voice call post dial delay from a subset of Twilio Phone Numbers to network subscribers in the United States. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available.
Twilio customers may be experiencing voice call post dial delay from a subset of Twilio Phone Numbers to network subscribers in the United States. Our team is actively investigating this issue. We will 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
126
Days with an incident
48
Median duration
6 h 32 min
This incident
92% shorter than the median
Other Twilio incidents
All incidentsTwilio·SMS Delivery Receipt Failures from Twilio to Claro Costa Rica
Twilio SMS delivery receipts fail for Claro network subscribers in Costa Rica. This affects SMS in Latin America and the carrier network for SMS in Latin America. Twilio is investigating the problem.
Twilio·SMS Delivery Delays and Failures from Twilio to Brisanet Servicos De Telecomunicacoes SA Brazil
Twilio SMS delivery to Brisanet network subscribers in Brazil has delays and failures. The affected components are SMS, Latin America and CARRIER NETWORK - SMS, Latin America. Twilio reports a recovery in SMS delivery and monitors service stability.
Twilio·Email Delivery Delays to Microsoft-Hosted Inboxes
Twilio reports delayed email delivery to some inboxes hosted by Microsoft. Other inbox providers are not affected. Twilio has identified the issue and states that messages to these inboxes stay queued longer than usual. No mail loss has occurred.
Twilio·SMS Delivery Receipt Delays from Twilio to Claro Colombia
Twilio SMS delivery receipts to Claro network subscribers in Colombia did not work. The SMS and Carrier Network SMS components in Latin America were degraded. Twilio reports that the incident is resolved. The outage lasted 5 hours and 34 minutes.
Twilio·Voice Call Silent and One-Way Audio from Colombia to a Subset of Twilio Phone Numbers
Twilio reports silent and one-way audio on voice calls from network subscribers in Colombia to a subset of Twilio Phone Numbers. The affected components are Voice, Latin America and CARRIER NETWORK - Voice, Latin America. Twilio has identified the cause and is working to resolve the issue.
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