Silent Network Authentication (SNA) Missing Redirects in Indonesia
SendGrid reports that Silent Network Authentication (SNA) does not work for device verification in Indonesia. The affected components are Verify Silent Network Auth and CARRIER NETWORK - Verify Silent Network Auth. SendGrid identified the problem and states that 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 43 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
45 min 44%
Identified
58 min 56%
Updates
Times in UTCAs posted by SendGrid
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
54
Days with an incident
38
Median duration
8 h 25 min
This incident
80% shorter than the median
Other SendGrid incidents
All incidentsSendGrid·Voice Call Failures from a Subset of Twilio Phone Numbers to Philippines
SendGrid voice calls fail from a subset of Twilio Philippines phone numbers to network subscribers in the Philippines. The Voice, APAC and CARRIER NETWORK - Voice, APAC components are degraded. SendGrid identified the cause and works to resolve the issue.
SendGrid·SMS Delivery Delays from a Subset of Twilio Short Codes to Google Voice United States
SendGrid reports SMS delivery delays from a subset of short codes to Google Voice subscribers in the United States. The affected components are SMS Short Code, North America and CARRIER NETWORK, SMS Short Code, North America. SendGrid resolved the incident after about 6 hours and 33 minutes.
SendGrid·SMS Delivery Failures from Twilio to KDDI Japan
SendGrid reports SMS delivery failures from Twilio to KDDI network subscribers in Japan. The incident affects SMS in APAC and the carrier network for SMS in APAC. SendGrid resolved the incident on 2 November 2026. The outage lasted 248 minutes.
SendGrid·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.
SendGrid·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 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.cc/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.cc/feed.xml?providers=sendgrid/feed subscribe https://outages.cc/feed.xml?providers=sendgridFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane