Silent Network Authentication (SNA) Missing Redirects on XL Axiata in Indonesia
SendGrid reported that Silent Network Authentication did not work on XL Axiata in Indonesia. Device verification timed out during API transactions. SendGrid reported the incident as resolved after 13 hours and 27 minutes.
State
Resolved
Started
1 d ago
2026-11-02 06:54 UTC
Lasted
13 h 27 min
until 2026-11-02 20:21 UTC
Worst impact
Degraded
Timeline
9 updatesInvestigating
45 min 6%
Identified
10 h 36 min 79%
Monitoring
2 h 6 min 16%
Updates
Times in UTCAs posted by SendGrid
The incident has been resolved and API transactions for Silent Network Authentication (SNA) on XL Axiata in Indonesia are operating normally.
We have observed the recovery in API transactions for Silent Network Authentication (SNA) on XL Axiata in Indonesia 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) on XL Axiata 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) on XL Axiata 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. 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 8 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 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 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
2SendGrid in the last 90 days
Full historyIncidents in 90 days
67
Days with an incident
39
Median duration
6 h 53 min
This incident
2.0× the median
Other SendGrid incidents
All incidentsSendGrid·SMS Delivery Delays from a Subset of Twilio Short Codes and Long Codes to Brisanet Brazil
SendGrid reports SMS delivery delays from a subset of Twilio Short Codes and Long Codes to Brisanet subscribers in Brazil. The delays affect SMS in Latin America and the related carrier network. SendGrid identified the cause and continues to work on a fix.
SendGrid·MMS Delivery Receipt Delays from a Subset of Twilio Long Codes to GCI Communication United States
SendGrid reports MMS delivery receipt delays from a subset of Twilio Long Codes to GCI Communication subscribers in the United States. The MMS Long Code components for North America are affected. SendGrid has identified the cause and is working to resolve the issue. Message delivery can succeed, but delivery receipts can be delayed.
SendGrid·SMS Delivery Delays from Twilio to Entel Bolivia
SendGrid reports SMS delivery delays to Entel network subscribers in Bolivia. The delays affect the SMS and carrier network components in Latin America. SendGrid has identified the cause and is working to resolve the issue.
SendGrid·SMS Delivery Delays from Twilio to Lycamobile United Kingdom
SendGrid reports SMS delivery delays from Twilio to Lycamobile network subscribers in the United Kingdom. The issue affected SMS in Europe and the carrier network for SMS in Europe. SendGrid reports that the incident is resolved. The incident lasted about 160 minutes.
SendGrid·Voice Call Audio Quality Degradation from Network Subscribers to Twilio Phone Numbers
SendGrid reports voice call audio delays and high packet loss for calls from network subscribers to Twilio phone numbers. The affected regions are North America, Latin America, APAC, Europe, and the Middle East and Africa. SendGrid reports a recovery and monitors service stability.
Follow SendGrid
Your coding agent knows when SendGrid is down, and tells you when a failure is theirs, not yours. You can also get SendGrid 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 "sendgrid" and tell me if SendGrid 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=sendgrid/feed subscribe https://outages.live/feed.xml?providers=sendgridFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane