Silent Network Authentication (SNA) Missing Redirects and Gateway API (Lookup API) Failure Increase in Netherlands
The incident has been resolved and API transactions for Silent Network Authentication (SNA) in the Netherlands and Lookup API transactions in the Netherlands are operating normally.
The latest update from SendGrid.
State
Resolved
Started
8 d ago
2026-10-24 21:28 UTC
Lasted
20 h 54 min
until 2026-10-25 18:22 UTC
Worst impact
Degraded
Timeline
9 updatesInvestigating
11 min 1%
Identified
18 h 7 min 87%
Monitoring
2 h 36 min 12%
Updates
Times in UTCAs posted by SendGrid
The incident has been resolved and API transactions for Silent Network Authentication (SNA) in the Netherlands and Lookup API transactions in the Netherlands are operating normally.
We have observed the recovery in API transactions for Silent Network Authentication (SNA) and the recovery for Lookup API transactions in the Netherlands and are monitoring service stability. We will provide another update in 4 hours or as soon as more information becomes available.
We have observed the recovery in API transactions for Silent Network Authentication (SNA) in the Netherlands and the recovery for Lookup API transactions involving the Netherlands 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) and failure responses for Lookup API transactions in the Netherlands. 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 16 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) and failure responses for Lookup API transactions in the Netherlands. 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 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) and failure responses for Lookup API transactions in the Netherlands. 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 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) and failure responses for Lookup API transactions in Netherlands. 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 device verification timeouts during API transactions for Silent Network Authentication (SNA) and failure responses for Lookup API transactions in Netherlands. 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 device verification timeouts during API transactions for Silent Network Authentication (SNA) and failure responses for Lookup API transactions in the Netherlands. 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
4SendGrid in the last 90 days
Full historyIncidents in 90 days
52
Days with an incident
38
Median duration
9 h 35 min
This incident
2.2× the median
Other SendGrid incidents
All incidentsSendGrid·SMS Delivery Delays from a Subset of Twilio Short Codes to Google Voice United States
SendGrid reports SMS delivery delays from a subset of Twilio short codes to Google Voice subscribers in the United States. The problem affects SMS Short Code and CARRIER NETWORK SMS Short Code in North America. SendGrid has identified the cause and works to resolve the issue.
SendGrid·SMS Delivery Failures from Twilio to KDDI Japan
SendGrid reports SMS delivery failures from Twilio to KDDI network subscribers in Japan. The affected components are SMS, APAC and CARRIER NETWORK - SMS, APAC. Twilio identified the cause and monitored a recovery. The incident is resolved and lasted 4 hours and 8 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.
SendGrid·Automated Alert: Minimal Customer Impact
We have fully investigated the issue affecting verifications to Ivory Coast, and it was determined that the impact was limited to a small set of customers, who have been contacted individually to address any concerns. All systems are operational.
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