Stytch
Apps and SaaS. Source: Stytch status page.
- Incidents, last 90 days
- 7
- Median to mitigation
- 31m
- Median to resolution
- 31m
- p95 to resolution
- 3h 33m
- Naming an upstream provider
- 0%
- With a postmortem on the status page
- 42%
What failed, last 90 days
| A provider or third-party service this vendor depends on failed | 2 |
| The text does not say enough to tell | 1 |
| Data delayed, stale, lost or corrupted, or needing replay after recovery | 1 |
| Traffic surge or denial-of-service attack | 1 |
| A schema or data migration caused the failure | 1 |
| Network, DNS, routing or connectivity failure | 1 |
Tagged by claude-haiku-5-5 from each incident's updates. See the methodology.
Incidents per month
All recorded incidents
Increase in 500 errors
Affected: Live API
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We're investigating an increase in 500 errors in our Live API.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Stytch's status page.
Investigating SMS deliverability issues to AT&T Wireless
Affected: Message deliverability
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We're currently investigating SMS deliverability issues to AT&T Wireless.
-
monitoring
We've switched to an alternative messaging provider and are monitoring the result.
-
resolved
SMS are being sent successfully to AT&T numbers.
Excerpts are shortened. Read the full incident on Stytch's status page.
Small percentage of SMS requests resulting in 500 errors
Affected: Message deliverability
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
investigating
A small percentage of SMS requests are currently resulting in 500 / internal\_server\_errors due to an upstream messaging issue.
-
resolved
This issue has been resolved.
Excerpts are shortened. Read the full incident on Stytch's status page.
Delayed Event Log Streams
Affected: Dashboard
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating delayed logs in our Event Log Streaming feature.
-
resolved
This incident has been resolved. Delayed logs are now delivered.
Excerpts are shortened. Read the full incident on Stytch's status page.
Emails not being delivered
Affected: Message deliverability
Failure mode: Traffic surge or denial-of-service attack. Root cause: An external attack. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
investigating
We are currently investigating this incident.
-
monitoring
We've mitigated the issue and emails are now being delivered. Currently monitoring.
-
resolved
The incident should be resolved; we have put in mitigations and will continue to monitor. A small percentage of users may see some lingering deliverability issues as we catch up. We apologize for the inconvenience.
-
postmortem
We extend our sincerest apologies for this outage. On 17 August 2026, between 02:15 and 05:15 PT (09:15–12:15 UTC), all outbound email from Stytch failed, including email magic links, email OTPs, and password reset emails. Service was restored at 05:15 PT. **What happened**:...
Excerpts are shortened. Read the full incident on Stytch's status page.
Increase in 500 errors
Affected: Javascript SDK, Test API, Live API
Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating this incident.
-
resolved
This incident has been resolved.
-
postmortem
An update to our DB caused around 1.5 minutes of increased 500's in our API. Apologies for the interruption.
Excerpts are shortened. Read the full incident on Stytch's status page.
Increase in 5XX errors
Affected: Live API
Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
investigating
We are investigating an increase in 5XX errors in the Stytch API.
-
resolved
This incident has been resolved.
-
postmortem
A network connectivity degradation in one of the regions where our infrastructure is hosted disrupted traffic, resulting in some timeouts. Steps will be taken to mitigate this in the future.
Excerpts are shortened. Read the full incident on Stytch's status page.
Issue causing invalid_email errors for some valid B2B email addresses
Affected: Message deliverability
Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We've identified an issue causing invalid\_email errors for some B2B users with valid email addresses.
-
resolved
This issue has been resolved.
Excerpts are shortened. Read the full incident on Stytch's status page.
SMS delivery is currently experiencing some delays.
Affected: Message deliverability
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
investigating
We are actively investigating SMS delivery delays with our primary messaging provider.
-
monitoring
We have failed over to our secondary messaging provider and are monitoring the status. You may see fewer SMSDelivery event logs than expected during this time.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Stytch's status page.
Errors with custom auth domain creation
Affected: Dashboard
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
identified
We have identified the root cause and are currently implementing a fix for errors with custom auth domain creation. Existing custom domains are not impacted.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Stytch's status page.
Issues with Email Risk API
Affected: Device Fingerprinting
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating elevated 500 errors in the email risk API.
-
monitoring
A fix has been implemented and we are currently monitoring the result.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Stytch's status page.
Internal Logging Disruption
Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
Event log streaming and internal logging in the Dashboard were interrupted for approximately 32 minutes. A fix was deployed, and the issue has been resolved.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Stytch's status page.
Outlook incident - emails not getting delivered
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
resolved
We are currently aware of an upstream incident with Microsoft Outlook impacting email deliveries with several of our messaging providers over the past several days. This has been widely reported across the industry, but Microsoft has not shared any public commentary as of yet....
Excerpts are shortened. Read the full incident on Stytch's status page.
Gmail incident - delayed emails
Affected: Message deliverability
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
investigating
Gmail is currently experiencing an incident that is causing delayed emails for end users. You can follow along with their incident here: We'll be monitoring and will resolve this incident when we've confirmed delivery returns to normal for Gmail users.
-
monitoring
Continuing to monitor.
-
monitoring
Reports of delivery issues has dropped but is still not back to normal. We're continuing to monitor.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Stytch's status page.
Increased 4XX and 5XX errors with Connected Apps
Affected: Device Fingerprinting, Test API, Live API, Dashboard, Javascript SDK, Message deliverability
Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
We have identified an issue with Connected Apps caused by a recent change and are currently implementing a fix.
-
monitoring
We implemented a fix and are currently monitoring the result.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Stytch's status page.
Elevated error rates for SAML SSO flow
Affected: Test API, Live API
Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are actively investigating an elevated rate of SAML SSO errors.
-
monitoring
We implemented a fix and are currently monitoring the result.
-
resolved
This incident has been resolved. SAML SSO traffic is healthy.
Excerpts are shortened. Read the full incident on Stytch's status page.
Inability to load frontend script from Cloudflare custom domain
Affected: Device Fingerprinting
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
Names an upstream provider: Cloudflare.
-
investigating
We are currently investigating this incident.
-
resolved
During [Cloudflare's 2025-11-18 incident](https://blog.cloudflare.com/18-november-2025-outage/), loading of Device Fingerprinting's frontend script was inaccessible for customers using a custom domain powered by Cloudflare. Any client that normally would have been fingerprinted...
Excerpts are shortened. Read the full incident on Stytch's status page.
Elevated error rate in API
Affected: Test API, Live API, Javascript SDK
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
Names an upstream provider: Cloudflare.
-
investigating
We are currently investigating an increase in errors in the Stytch API due to impact from an upstream provider outage.
-
monitoring
Services are recovering in the upstream provider, Cloudflare. Customers may continue to observe higher-than-normal error rates if they utilized Cloudflare in the meantime.
-
resolved
During [Cloudflare's 2025-11-18 incident](https://blog.cloudflare.com/18-november-2025-outage/), Stytch's services continued to operate as normal. However Stytch customers that use Cloudflare in their own infrastructure may have seen their requests to Stytch, either client or...
Excerpts are shortened. Read the full incident on Stytch's status page.
Increased latency in the live API
Affected: Live API
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating issues with increased latency in the live API.
-
monitoring
We implemented a fix and are currently monitoring the result.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Stytch's status page.
Device Fingerprinting pages unavailable in the Dashboard
Affected: Dashboard, Message deliverability
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
For customers with access to Device Fingerprinting, the Device Fingerprinting Logs and Device Fingerprinting Rules pages are inaccessible. Fingerprint Lookups and other API calls are unaffected.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Stytch's status page.
Elevated SMS OTP errors/ delays
Affected: Message deliverability
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
Names an upstream provider: AWS.
-
investigating
SMS OTP error rates and delays are currently elevated due to an incident from our primary messaging provider (related to AWS outage). We're assessing whether it makes sense to switch to a backup provider.
-
monitoring
The SMS OTP errors have subsided. We will continue to monitor the situation while our primary messaging provider investigates the incident.
-
resolved
This incident has been resolved. We experienced elevated SMS OTP errors and delays, affecting roughly 9% of all messages and about 14% of SMS and WhatsApp messages.
Excerpts are shortened. Read the full incident on Stytch's status page.
SAML SSO requests failing
Affected: Test API, Live API, Javascript SDK
Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
Names an upstream provider: AWS.
-
investigating
SAML SSO requests are currently failing as a downstream affect of the AWS outage. We're currently investigating ways to mitigate the issue.
-
resolved
This incident has been resolved.
-
postmortem
**Issue** All SAML SSO Logins failed in the Stytch Platform. **Timeline** October 20th, 2025 16:30 - 18:01 UTC **Cause** A widespread outage in AWS created a knock-on effect that uncovered a latent certificate management issue within the Stytch SSO service. Other Stytch...
Excerpts are shortened. Read the full incident on Stytch's status page.
Elevated BLOCK rates
Affected: Device Fingerprinting
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating elevated DFP BLOCK rates.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Stytch's status page.
Investigating report of email deliverability issues
Affected: Message deliverability
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We've received several reports of potential issues with delivery login emails to Yahoo Email inboxes.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Stytch's status page.
The Stytch API is currently experiencing issues.
Affected: Live API
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are investigating elevated API latencies.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Stytch's status page.