Increase in 500 errors
Timeline · 2 updates
- investigating Oct 06, 2026, 04:48 PM UTC
We're investigating an increase in 500 errors in our Live API..
- resolved Oct 06, 2026, 04:49 PM UTC
This incident has been resolved..
Stytch had 24 outages in the last 2 years totaling 80h 17m of downtime — averaging 1 incident per month.
There were 24 Stytch outages since October 7, 2025 totaling 80h 17m of downtime. Each is summarised below — incident details, duration, and resolution information.
We're investigating an increase in 500 errors in our Live API..
This incident has been resolved..
We're currently investigating SMS deliverability issues to AT&T Wireless..
We've switched to an alternative messaging provider and are monitoring the result..
SMS are being sent successfully to AT&T numbers..
A small percentage of SMS requests are currently resulting in 500 / internal\_server\_errors due to an upstream messaging issue..
This issue has been resolved..
We are currently investigating delayed logs in our Event Log Streaming feature..
This incident has been resolved. Delayed logs are now delivered..
We are investigating an increase in 5XX errors in the Stytch API..
This incident has been resolved..
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..
We've identified an issue causing invalid\_email errors for some B2B users with valid email addresses..
This issue has been resolved..
We are actively investigating SMS delivery delays with our primary messaging provider..
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..
This incident has been resolved..
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..
This incident has been resolved..
We are currently investigating elevated 500 errors in the email risk API..
A fix has been implemented and we are currently monitoring the result..
This incident has been resolved..
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..
This incident has been 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. We're looking into any ways we may be able to mitigate this until Microsoft addresses the issue. Though these issues are not causing any downtime in Stytch services, due to the popularity of Microsoft Outlook, we've created this incident for posterity for customers investigating downtime in their own systems. Customers that feel they are continuing to observe excessive deferrals and/or blocks should fill out the OLC Support request form at [https://olcsupport.office.com.](https://olcsupport.office.com/).
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..
Continuing to monitor..
Reports of delivery issues has dropped but is still not back to normal. We're continuing to monitor..
This incident has been resolved..
We have identified an issue with Connected Apps caused by a recent change and are currently implementing a fix..
We implemented a fix and are currently monitoring the result..
This incident has been resolved..
We are actively investigating an elevated rate of SAML SSO errors..
We implemented a fix and are currently monitoring the result..
This incident has been resolved. SAML SSO traffic is healthy..
We are currently investigating an increase in errors in the Stytch API due to impact from an upstream provider outage..
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..
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 server side requests, fail to make it to the Stytch API, thus causing their auth flows to fail. Though the Cloudflare incident did not cause any downtime in Stytch services, due to the popularity of Cloudflare, we've created this incident for posterity for customers investigating downtime in their own systems..
We are currently investigating this incident..
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 during this time would have failed to do so and received no telemetry. Clients that had already loaded the script before this time period were unaffected..
We are currently investigating issues with increased latency in the live API..
We implemented a fix and are currently monitoring the result..
This incident has been resolved..
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..
This incident has been resolved..
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..
The SMS OTP errors have subsided. We will continue to monitor the situation while our primary messaging provider investigates the incident..
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..
SAML SSO requests are currently failing as a downstream affect of the AWS outage. We're currently investigating ways to mitigate the issue..
This incident has been resolved..
**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 services, like the core Authentication API, responded appropriately in the face of downtime and continued to operate as expected. The result was that all SAML SSO login attempts during this incident returned an invalid certificate error and prevented users from logging in. **Remediation** Stytch updated the SSO service to handle certificate management so that it aligns with our other services that did not error. This reconfiguration will prevent this error from recurring in the event of AWS failure again in the future..
We are currently investigating elevated DFP BLOCK rates..
This incident has been resolved..
We've received several reports of potential issues with delivery login emails to Yahoo Email inboxes..
This incident has been resolved..
We are investigating elevated API latencies..
This incident has been resolved..