Silent Network Authentication (SNA) Failure Increase and Gateway API (Lookup API) Failure Increase on EnStream in Canada
Twilio had failures in Silent Network Authentication and Gateway Lookup API on EnStream in Canada. The affected components include Verify Silent Network Auth, Lookup Identity Match, Lookup SIM Swap, and Legacy Identity MatchAndAttributes. Twilio reports that the incident is resolved. The outage lasted about 14 hours and 13 minutes.
State
Resolved
Started
Lasted
14 h 13 min
Worst impact
Degraded
Timeline
10 updatesInvestigating
2 h 1 min 14%
Identified
6 h 3 min 43%
Monitoring
6 h 8 min 43%
Updates
Times in UTCAs posted by Twilio
The incident has been resolved and API transactions for Silent Network Authentication (SNA) on EnStream in Canada and Lookup API transactions involving EnStream in Canada are operating normally.
We have observed recovery in API transactions for Silent Network Authentication (SNA) and the recovery for Lookup API transactions involving EnStream in Canada and are monitoring service stability. We will provide another update in 4 hours or as soon as more information becomes available.
We have observed recovery in API transactions for Silent Network Authentication (SNA) and the recovery for Lookup API transactions involving EnStream in Canada and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.
We have identified the cause of the Silent Network Authentication (SNA) Failure Increase and Gateway API Failure Increase to EnStream in Canada. We will continue working with our Service Provider to resolve the incident. An update will be provided in 4 hour or as soon as more details become available.
We have identified the cause of the Silent Network Authentication (SNA) Failure Increase and Gateway API Failure Increase to EnStream in Canada. We will continue working with our Service Provider to resolve the incident. An update will be provided in 2 hour or as soon as more details become available.
We have identified the cause of the Silent Network Authentication (SNA) Failure Increase and Gateway API Failure Increase to EnStream in Canada. We will continue working with our Service Provider to resolve the incident. An update will be provided in 1 hour or as soon as more details become available.
We have identified the cause of the Silent Network Authentication (SNA) Failure Increase and Gateway API Failure Increase to EnStream in Canada. We will continue working with our Service Provider to resolve the incident. An update will be provided in 2 hour or as soon as more details become available.
We have identified the cause of the Silent Network Authentication (SNA) Failure Increase and Gateway API Failure Increase to EnStream in Canada. We will continue working with our Service Provider to resolve the incident. An update will be provided in 1 hour or as soon as more details become available.
Twilio customers may be experiencing verification failures during API transactions for Silent Network Authentication (SNA) and failure responses for Lookup API transactions on EnStream in Canada. 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 verification failures during API transactions for Silent Network Authentication (SNA) and failure responses for Lookup API transactions on EnStream in Canada. 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
102
Days with an incident
46
Median duration
7 h 30 min
This incident
1.9× the median
Other Twilio incidents
All incidentsTwilio·WhatsApp Business API Message Send Failures
Twilio reports message send failures on the WhatsApp Business API, which affects WhatsApp Messaging. Some customers get error 63007 when they send outbound messages. Twilio has mitigated the issue and now monitors system performance. Message sending is returning to normal for affected customers.
Twilio·Voice Call Failures from a Subset of Twilio Phone Numbers to Chile
Voice calls fail from some Twilio phone numbers to network subscribers in Chile. The Voice, Latin America and CARRIER NETWORK - Voice, Latin America components are affected. Twilio has identified the cause and works to resolve the issue.
Twilio·Voice Call Audio Quality Degradation, Silent and One-Way Audio between Twilio and Multiple Networks in United Kingdom
Twilio voice calls had audio quality degradation, silent audio, and one-way audio between Twilio and network subscribers on multiple networks in the United Kingdom. The affected components were Voice, Europe and CARRIER NETWORK - Voice, Europe. Twilio reports that the incident is resolved, and it lasted about 5 hours and 19 minutes.
Twilio·SMS Delivery Delays and Failures from a Subset of Twilio Alphanumeric Sender IDs and Long Codes to Multiple Networks in Italy
Twilio SMS delivery delays and failures affected a subset of Twilio Alphanumeric Sender IDs and Long Codes to multiple networks in Italy. Twilio identified the cause, then monitored service stability. The incident is resolved. It lasted about 3 hours and 14 minutes.
Twilio·SMS Delivery Delays and Failures from Twilio to Spusu United Kingdom
Twilio SMS delivery delays and failures affected messages to Spusu subscribers in the United Kingdom. Twilio reports that the incident is resolved. The outage lasted 3 hours and 26 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