SendGrid: Silent Network Authentication (SNA) Missing Redirects and Gateway API (Lookup API) Failure Increase in Netherlands
Affected components: CARRIER NETWORK - Lookup Identity MatchLookup Identity MatchCARRIER NETWORK - Lookup SIM SwapLookup SIM SwapCARRIER NETWORK - Verify Silent Network AuthVerify Silent Network Auth
Timeline of updates
- investigating
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.
- identified
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 is actively investigating the issue. We will provide another update in 1 hour or as soon as more information becomes available.
- identified
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 2 hours or as soon as more information becomes available.
Changes Rewindex caught on this incident
- Incident updated: Silent Network Authentication (SNA) Missing Redirects and Gateway API (Lookup API) Failure Increase in Netherlands
- Incident updated: Silent Network Authentication (SNA) Missing Redirects and Gateway API (Lookup API) Failure Increase in Netherlands
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
Rewindex captured this after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).