Voice Call Failures from a Subset of Twilio Phone Numbers to Philippines
Voice calls fail from a subset of Twilio Philippines phone numbers to subscribers on multiple networks in the Philippines. The affected components are Voice, APAC and CARRIER NETWORK - Voice, APAC. Twilio has identified the cause and is working to resolve the issue.
State
Identified
Started
2 h ago
2026-11-02 05:41 UTC
Ongoing for
1 h 50 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
4 min 3%
Identified
1 h 47 min 97%
Updates
Times in UTCAs posted by Twilio
Twilio customers may be experiencing voice call failures from a subset of Twilio Phone Numbers to network subscribers in the Philippines. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 2 hours or as soon as more information becomes available.
Twilio customers may be experiencing voice call failures from a subset of Twilio Philippines Phone Numbers to network subscribers on multiple networks in the Philippines. 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 failures from a subset of Twilio Philippines Phone Numbers to network subscribers on multiple networks in the Philippines. 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
54
Days with an incident
38
Median duration
8 h 25 min
This incident
78% shorter than the median
Other Twilio incidents
All incidentsTwilio·Silent Network Authentication (SNA) Missing Redirects in Indonesia
Silent Network Authentication (SNA) redirects do not work in Indonesia. This affects the Verify Silent Network Auth component and the carrier network for Verify Silent Network Auth. Twilio reports the state as investigating.
Twilio·SMS Delivery Delays from a Subset of Twilio Short Codes to Google Voice United States
Twilio SMS delivery delays affected a subset of Twilio Short Codes to Google Voice subscribers in the United States, on the SMS Short Code and Carrier Network SMS Short Code components in North America. Twilio reports that the incident is resolved and that delivery operates normally. The incident lasted about 6 hours and 32 minutes.
Twilio·SMS Delivery Failures from Twilio to KDDI Japan
SMS delivery failures affected Twilio messages to KDDI network subscribers in Japan. Twilio reports that the incident is resolved. The outage lasted about 4 hours and 8 minutes.
Twilio·Silent Network Authentication (SNA) Missing Redirects and Gateway API (Lookup API) High Latency on KPN in Netherlands
The incident has been resolved and API transactions for Silent Network Authentication (SNA) on KPN in Netherlands and Lookup API transactions involving KPN in Netherlands are operating normally.
Twilio·Silent Network Authentication (SNA) Missing Redirects on Smart in Philippines
The incident has been resolved and API transactions for Silent Network Authentication (SNA) on Smart in Philippines are 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.cc/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.cc/feed.xml?providers=twilio/feed subscribe https://outages.cc/feed.xml?providers=twilioFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane