Elastic SIP Trunking Voice Call Issues
Twilio Elastic SIP Trunking Voice calls did not work correctly on Termination US1. Twilio reports that the issue is resolved after 28 minutes. The service operates normally.
State
Resolved
Started
Lasted
28 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
28 min 100%
Updates
Times in UTCAs posted by Twilio
We've detected full recovery of Elastic SIP Trunking. The issue impacting Voice calls has been resolved, and the service is operating normally.
We are investigating an issue with Elastic SIP Trunking. Users may experience issues when making or receiving Voice calls using Elastic SIP Trunking. 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
127
Days with an incident
49
Median duration
6 h 32 min
This incident
93% shorter than the median
Other Twilio incidents
All incidentsTwilio·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.
Twilio·SMS Delivery Receipt Failures from Twilio to Claro Costa Rica
SMS delivery receipts fail from Twilio to Claro network subscribers in Costa Rica. This affects SMS in Latin America and the carrier network for SMS in Latin America. Twilio reports that the problem is under investigation. Message delivery can succeed, but delivery receipts can fail.
Twilio·SMS Delivery Delays and Failures from Twilio to Brisanet Brazil
Twilio SMS delivery to Brisanet network subscribers in Brazil had delays and failures. The incident affected SMS in Latin America and the carrier network for SMS in Latin America. Twilio reports that the incident is resolved. It lasted about 6 hours and 40 minutes.
Twilio·Email Delivery Delays to Microsoft Inbox Providers
Twilio reports delays for Email sent to Microsoft-hosted inboxes. Messages to other inbox providers are not affected. Twilio has identified the issue and states that it comes from a third-party provider dependency. Mail is queued for later delivery and no mail is lost.
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.
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