rewindex

CompaniesStytchIncidents

Stytch: Missing or delayed SMS OTPs

unknownStatus: resolvededitedStarted Resolved (2.5 h)3 updatesstatus.stytch.com (opens in new tab)
Summary

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.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Affected components: Message deliverability

Timeline of updates

  1. investigatingEdited

    We are investigating missing or delayed SMS OTPs from our primary messaging provider to VOIP phone numbers..

  2. monitoringEdited

    We've failed over to our secondary messaging provider and are monitoring deliverability rates..

  3. resolved

    This incident has been resolved..

Changes Rewindex caught on this incident

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.

Impact, status and times are the vendor’s own, as last archived. View on status.stytch.com (opens in new tab).

Cite this

Status incident (vendor impact label: unknown) posted by Stytch, started 2026-10-22 16:00 UTC, resolved after 2.5 h, 3 update(s); edited after publishing.

Title
Missing or delayed SMS OTPs
Vendor
Stytch
Date
URL
https://rewindex.com/company/stytch/incidents/cmvjtpi4g00k71ms0l3d7zqcu

Stytch profileRecent Stytch incidentsAll outages on October 22, 2026Stytch in October 2026MarkdownJSON