Silent Network Authentication (SNA) Failure Increase and Gateway API (Lookup API) Failure Increase in United Kingdom
Twilio reports failures in Silent Network Authentication and Lookup API transactions in the United Kingdom. The affected components include Verify Silent Network Auth, Lookup Identity Match, Lookup SIM Swap, and Legacy Identity MatchAndAttributes. Twilio has identified the cause and is working to resolve the issue.
State
Identified
Started
Ongoing for
14 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
7 min 48%
Identified
7 min 52%
Updates
Times in UTCAs posted by Twilio
Twilio customers may be experiencing verification failures during API transactions for Silent Network Authentication (SNA) and failure responses for Lookup API transactions in the United Kingdom. API transactions may temporarily fail over to secondary methods like SMS OTP. 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 verification failures during API transactions for Silent Network Authentication (SNA) and failure responses for Lookup API transactions in the United Kingdom. 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
8Twilio in the last 90 days
Full historyIncidents in 90 days
130
Days with an incident
49
Median duration
6 h 25 min
This incident
96% shorter than the median
Other Twilio incidents
All incidentsTwilio·SMS Delivery Receipt Delays from a Subset of Twilio Short Codes to Multiple Networks in India
Twilio SMS delivery receipts were delayed from a subset of Twilio Short Codes to subscribers on multiple networks in India. The incident affected SMS in APAC and the related carrier network. Twilio reports that the incident is resolved and lasted 48 minutes.
Twilio·SMS Delivery Delays from a Subset of Twilio Short Codes to Multiple Networks in India
Twilio SMS delivery from a subset of Twilio Short Codes to multiple networks in India had delays. The SMS and carrier network components in APAC were affected. Twilio resolved the incident after 3 hours and 12 minutes.
Twilio·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.
Twilio·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
Twilio reports SMS delivery receipt failures for messages to Claro network subscribers in Costa Rica. The issue affects SMS in Latin America and the related carrier network. Twilio is investigating. Message delivery may succeed, but delivery receipts may fail.
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