Silent Network Authentication (SNA) Missing Redirects in Indonesia
Twilio reports that Silent Network Authentication (SNA) device verification timeouts occur during API transactions in Indonesia. The affected components are Verify Silent Network Auth and CARRIER NETWORK - Verify Silent Network Auth. Twilio identified the problem and API transactions can fail over to secondary methods such as SMS OTP.
State
Identified
Started
2 h ago
2026-11-02 06:54 UTC
Ongoing for
1 h 54 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
45 min 40%
Identified
1 h 9 min 60%
Updates
Times in UTCAs posted by Twilio
Twilio customers may be experiencing device verification timeouts during API transactions for Silent Network Authentication (SNA) in Indonesia. 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 Indonesia. 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 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 Indonesia. 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
54
Days with an incident
38
Median duration
8 h 25 min
This incident
77% shorter than the median
Other Twilio incidents
All incidentsTwilio·Voice Call Failures from a Subset of Twilio Phone Numbers to Philippines
Twilio reports voice call failures from a subset of Twilio Philippines phone numbers to network 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.
Twilio·SMS Delivery Delays from a Subset of Twilio Short Codes to Google Voice United States
Twilio SMS delivery from a subset of Twilio Short Codes to Google Voice subscribers in the United States had delays. The SMS Short Code components in North America were affected. Twilio reports that the incident is resolved and the service operates normally. The incident lasted about 6 hours and 32 minutes.
Twilio·SMS Delivery Failures from Twilio to KDDI Japan
SMS delivery failures from Twilio to KDDI network subscribers in Japan affected SMS in the APAC region. 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.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