Stytch Outage History
6 incidents recorded over the last 365 days, 3 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Stytch Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 8, 2026 | Scheduled maintenanceScheduled Maintenance | 1 min | Scheduled |
| Oct 22, 2026 | Missing or delayed SMS OTPs | 2h 31m | Resolved |
| Sep 18, 2026 | Planned DB maintenance - Live environmentScheduled Maintenance | 30 min | Scheduled |
| Sep 10, 2026 | Scheduled Test API DB maintenanceScheduled Maintenance | 30 min | Scheduled |
| Sep 9, 2026 | Investigating SMS deliverability issues to AT&T Wireless | 2h 30m | Resolved |
| Aug 17, 2026 | Emails not being delivered | 7h 0m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Stytch incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Stytch Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Stytch acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Stytch outage in this window ran 7h, against a mean recovery of 2h 10m. If you depend on Stytch in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.