Silent Network Authentication (SNA) Missing Redirects in Philippines
Silent Network Authentication (SNA) device verification had degraded performance in the Philippines. This affected Twilio Verify Silent Network Auth and the carrier network component. Twilio reports that the incident is resolved. The outage lasted about 16 hours.
State
Resolved
Started
Lasted
16 h 3 min
Worst impact
Degraded
Timeline
9 updatesInvestigating
6 h 59 min 44%
Identified
6 h 9 min 38%
Monitoring
2 h 55 min 18%
Updates
Times in UTCAs posted by Twilio
The incident has been resolved and API transactions for Silent Network Authentication (SNA) in the Philippines are operating normally.
We have observed the recovery in API transactions for Silent Network Authentication (SNA) in the Philippines and are monitoring service stability. We will provide another update in 4 hours or as soon as more information becomes available.
We have observed the recovery in API transactions for Silent Network Authentication (SNA) in the Philippines and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.
Twilio customers may be experiencing device verification timeouts during API transactions for Silent Network Authentication (SNA) in the Philippines. Our team is actively investigating the issue. API transactions may temporarily fail over to secondary methods like SMS OTP. We will provide another update in 4 hours or as soon as more information becomes available.
Twilio customers may be experiencing device verification timeouts during API transactions for Silent Network Authentication (SNA) in the Philippines. API transactions may temporarily fail over to secondary methods like SMS OTP. Our team is actively investigating the issue. We will provide another update in 2 hours or as soon as more information becomes available.
Twilio customers may be experiencing device verification timeouts during API transactions for Silent Network Authentication (SNA) in the Philippines. Our team is actively investigating the issue. API transactions may temporarily fail over to secondary methods like SMS OTP. We will provide another update in 1 hour or as soon as more information becomes available.
Twilio customers may be experiencing device verification timeouts during API transactions for Silent Network Authentication (SNA) in the Philippines. Our team is actively investigating the issue. API transactions may temporarily fail over to secondary methods like SMS OTP. We will provide another update in 4 hours or as soon as more information becomes available.
Twilio customers may be experiencing device verification timeouts during API transactions for Silent Network Authentication (SNA) in the Philippines. Our team is actively investigating the issue. API transactions may temporarily fail over to secondary methods like SMS OTP. We will provide another update in 2 hours or as soon as more information becomes available.
Twilio customers may be experiencing device verification timeouts during API transactions for Silent Network Authentication (SNA) in the Philippines. Our team is actively investigating the issue. API transactions may temporarily fail over to secondary methods like SMS OTP. 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
153
Days with an incident
53
Median duration
6 h 18 min
This incident
2.5× the median
Other Twilio incidents
All incidentsTwilio·SMS Delivery Delays from Twilio to Sky United Kingdom
Twilio SMS delivery delays affect messages to Sky network subscribers in the United Kingdom. The affected components are SMS, Europe and CARRIER NETWORK - SMS, Europe. Twilio has identified the cause and work continues to resolve the issue.
Twilio·Gateway API (Lookup API) Failure Increase in Canada
Twilio Lookup API transactions in Canada failed. The incident affected Lookup Identity Match and Legacy Identity MatchAndAttributes, including CARRIER NETWORK components. Twilio reports that the incident is resolved. The outage lasted 3 hours and 59 minutes.
Twilio·SMS Delivery Delays from a Subset of Twilio Short Codes to Liberty Mobile Puerto Rico
Twilio reports SMS delivery delays from a subset of Twilio Short Codes to Liberty Mobile subscribers in Puerto Rico. The affected components are SMS, Latin America and CARRIER NETWORK - SMS, Latin America. Twilio has identified the cause and is working to resolve the issue.
Twilio·On Call Engineers are Investigating an issue with processing profile events
Twilio reported an issue that affected newly created profiles and the processing of profile events. Twilio investigated the issue. The issue is resolved. It lasted 86 minutes.
Twilio·SMS Delivery Delays from a Subset of Twilio Short Codes to T-Mobile United States
Twilio SMS delivery delays affected a subset of Twilio Short Codes to T-Mobile subscribers in the United States. The incident is resolved. It lasted about 2 hours and 21 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