ChangesStytchMissing or delayed SMS OTPs
Stytch: Incident updated: Missing or delayed SMS OTPs
Summary pending. The diff below shows exactly what changed.
Incident page: the full timeline of updates
What changed
Struck in red is what Stytch removed; blue is what they added. Muted text is unchanged context.
Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).
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. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
Before captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
16718c89f2deaf5d…After captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
89e71cd5fab3f0f3…
History of this incident
Thursday, October 22
1 rewrite, 2 incident changes
- Minor editEdited by the vendor
Stytch’s 10-22 16:00 UTC update clarified that missing or delayed SMS OTPs from its primary messaging provider affected VOIP phone numbers, rather than an unspecified subset. Its 10-22 18:15 UTC update still reports failover to the secondary provider and deliverability monitoring, but no longer describes the failover as manual.
- Normal progressIncident
Incident updateMissing or delayed SMS OTPsthis change
- Normal progressIncident
Incident updateMissing or delayed SMS OTPs
Cite this
Incident updated: Missing or delayed SMS OTPs on Stytch’s status page, changed 2026-10-22 18:33 UTC (change 2 of 3).
- Title
- Incident updated: Missing or delayed SMS OTPs
- Vendor
- Stytch
- Date
- URL
- https://rewindex.com/change/ra804936f0a40fa