Stytch Outage History

Started Oct 06, 2026, 04:48 PM UTC· resolved Oct 06, 2026, 04:49 PM UTC

1. investigating Oct 06, 2026, 04:48 PM UTC

   We're investigating an increase in 500 errors in our Live API..

2. resolved Oct 06, 2026, 04:49 PM UTC

   This incident has been resolved..

Read the full incident report →

Started Sep 09, 2026, 02:30 PM UTC· resolved Sep 09, 2026, 05:00 PM UTC

1. investigating Sep 09, 2026, 02:30 PM UTC

   We're currently investigating SMS deliverability issues to AT&T Wireless..

2. monitoring Sep 09, 2026, 04:43 PM UTC

   We've switched to an alternative messaging provider and are monitoring the result..

3. resolved Sep 09, 2026, 05:00 PM UTC

   SMS are being sent successfully to AT&T numbers..

Read the full incident report →

Started Sep 01, 2026, 04:30 PM UTC· resolved Sep 01, 2026, 05:27 PM UTC

1. investigating Sep 01, 2026, 04:30 PM UTC

   A small percentage of SMS requests are currently resulting in 500 / internal\_server\_errors due to an upstream messaging issue..

2. resolved Sep 01, 2026, 05:27 PM UTC

   This issue has been resolved..

Read the full incident report →

Started Aug 28, 2026, 10:29 PM UTC· resolved Aug 28, 2026, 11:00 PM UTC

1. investigating Aug 28, 2026, 10:29 PM UTC

   We are currently investigating delayed logs in our Event Log Streaming feature..

2. resolved Aug 28, 2026, 11:00 PM UTC

   This incident has been resolved. Delayed logs are now delivered..

Read the full incident report →

Started Aug 17, 2026, 09:27 AM UTC· resolved Aug 17, 2026, 01:00 PM UTC

1. investigating Aug 17, 2026, 09:27 AM UTC

   We are currently investigating this incident..

2. monitoring Aug 17, 2026, 12:14 PM UTC

   We've mitigated the issue and emails are now being delivered. Currently monitoring..

3. resolved Aug 17, 2026, 01:00 PM UTC

   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..

4. monitoring Aug 18, 2026, 12:00 AM UTC

   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**: This outage was triggered by abuse of free-tier email sending, a pattern we defend against continuously. In this case, our abuse controls did not engage in time, and a large volume of spam was sent before we intervened. That volume exhausted our sending quota with our primary email provider, which normally handles the majority of traffic. Automated failover and alerting fired, and our on-call engineer fully failed over to our secondary email provider within 20 minutes. That failover appeared to succeed: The secondary provider accepted our sends and reported them as successful 200s. However, the secondary provider was not delivering those emails due to the previous spam volume. As a result, we believed email had been restored when it had not. We received customer reports beginning at 03:15 PT and confirmed the true state of email sends at 05:01 PT. We restored service at 05:15 PT, banned the malicious accounts, and implemented new safeguards against the abuse seen. **Impact**: All email sent during the window failed permanently. Any authentication email a user requested between 02:15 and 05:15 PT never arrived, and users would need to request a new one after 05:15 PT. **Ongoing impact on deliverability**: The spam volume sent from our infrastructure has affected our sender reputation for `[email protected]`. For some time, a higher-than-normal share of legitimate emails may land in recipients' spam folders. We are working with our providers on reputation remediation and expect this to improve over the coming days. No action is required. If your users report missing authentication emails, please ask them to check their spam folder. **What we're changing**: We have already implemented new safeguards against the abuse seen. To prevent future attacks, we are also reviewing our systems and processes, including: * Rate limits and quotas * Verification of failover paths * Abuse detection at signup and message send time.

Read the full incident report →

Started Jul 24, 2026, 10:56 AM UTC· resolved Jul 24, 2026, 11:11 AM UTC

1. investigating Jul 24, 2026, 10:56 AM UTC

   We are investigating an increase in 5XX errors in the Stytch API..

2. resolved Jul 24, 2026, 11:11 AM UTC

   This incident has been resolved..

3. monitoring Jul 24, 2026, 05:00 PM UTC

   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..

Read the full incident report →

Started Jun 15, 2026, 10:07 PM UTC· resolved Jun 16, 2026, 02:53 PM UTC

1. investigating Jun 15, 2026, 10:07 PM UTC

   We've identified an issue causing invalid\_email errors for some B2B users with valid email addresses..

2. resolved Jun 16, 2026, 02:53 PM UTC

   This issue has been resolved..

Read the full incident report →

Started Jun 02, 2026, 06:00 PM UTC· resolved Jun 02, 2026, 07:00 PM UTC

1. investigating Jun 02, 2026, 06:00 PM UTC

   We are actively investigating SMS delivery delays with our primary messaging provider..

2. monitoring Jun 02, 2026, 06:41 PM UTC

   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..

3. resolved Jun 02, 2026, 07:00 PM UTC

   This incident has been resolved..

Read the full incident report →

Started May 29, 2026, 06:12 PM UTC· resolved May 29, 2026, 10:41 PM UTC

1. identified May 29, 2026, 06:12 PM UTC

   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..

2. resolved May 29, 2026, 10:41 PM UTC

   This incident has been resolved..

Read the full incident report →

Started Apr 06, 2026, 02:52 PM UTC· resolved Apr 06, 2026, 05:00 PM UTC

1. investigating Apr 06, 2026, 02:52 PM UTC

   We are currently investigating elevated 500 errors in the email risk API..

2. monitoring Apr 06, 2026, 04:45 PM UTC

   A fix has been implemented and we are currently monitoring the result..

3. resolved Apr 06, 2026, 05:00 PM UTC

   This incident has been resolved..

Read the full incident report →

Started Jan 28, 2026, 08:23 PM UTC· resolved Jan 28, 2026, 08:55 PM UTC

1. identified Jan 28, 2026, 08:23 PM UTC

   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..

2. resolved Jan 28, 2026, 08:55 PM UTC

   This incident has been resolved..

Read the full incident report →

Started Jan 27, 2026, 01:00 PM UTC· resolved Jan 27, 2026, 01:00 PM UTC

1. resolved Jan 27, 2026, 01:00 PM UTC

   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/).

Read the full incident report →

Started Jan 24, 2026, 01:02 PM UTC· resolved Jan 25, 2026, 03:30 AM UTC

1. investigating Jan 24, 2026, 01:02 PM UTC

   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..

2. monitoring Jan 24, 2026, 05:22 PM UTC

   Continuing to monitor..

3. monitoring Jan 24, 2026, 09:12 PM UTC

   Reports of delivery issues has dropped but is still not back to normal. We're continuing to monitor..

4. resolved Jan 25, 2026, 03:30 AM UTC

   This incident has been resolved..

Read the full incident report →

Started Dec 22, 2025, 09:59 PM UTC· resolved Dec 22, 2025, 10:35 PM UTC

1. identified Dec 22, 2025, 09:59 PM UTC

   We have identified an issue with Connected Apps caused by a recent change and are currently implementing a fix..

2. monitoring Dec 22, 2025, 10:30 PM UTC

   We implemented a fix and are currently monitoring the result..

3. resolved Dec 22, 2025, 10:35 PM UTC

   This incident has been resolved..

Read the full incident report →

Started Dec 19, 2025, 04:30 PM UTC· resolved Dec 19, 2025, 04:52 PM UTC

1. investigating Dec 19, 2025, 04:30 PM UTC

   We are actively investigating an elevated rate of SAML SSO errors..

2. monitoring Dec 19, 2025, 04:51 PM UTC

   We implemented a fix and are currently monitoring the result..

3. resolved Dec 19, 2025, 04:52 PM UTC

   This incident has been resolved. SAML SSO traffic is healthy..

Read the full incident report →

Started Nov 18, 2025, 11:30 AM UTC· resolved Nov 18, 2025, 12:10 PM UTC

1. investigating Nov 18, 2025, 11:30 AM UTC

   We are currently investigating an increase in errors in the Stytch API due to impact from an upstream provider outage..

2. monitoring Nov 18, 2025, 12:01 PM UTC

   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..

3. resolved Nov 18, 2025, 12:10 PM UTC

   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..

Read the full incident report →

Started Nov 18, 2025, 11:30 AM UTC· resolved Nov 18, 2025, 12:10 PM UTC

1. investigating Nov 18, 2025, 11:30 AM UTC

   We are currently investigating this incident..

2. resolved Nov 18, 2025, 12:10 PM UTC

   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..

Read the full incident report →

Started Nov 13, 2025, 02:06 PM UTC· resolved Nov 13, 2025, 02:20 PM UTC

1. investigating Nov 13, 2025, 02:06 PM UTC

   We are currently investigating issues with increased latency in the live API..

2. monitoring Nov 13, 2025, 02:17 PM UTC

   We implemented a fix and are currently monitoring the result..

3. resolved Nov 13, 2025, 02:20 PM UTC

   This incident has been resolved..

Read the full incident report →

Started Nov 10, 2025, 05:20 PM UTC· resolved Nov 10, 2025, 08:16 PM UTC

1. investigating Nov 10, 2025, 05:20 PM UTC

   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..

2. resolved Nov 10, 2025, 08:16 PM UTC

   This incident has been resolved..

Read the full incident report →

Started Oct 20, 2025, 04:57 PM UTC· resolved Oct 20, 2025, 06:40 PM UTC

1. investigating Oct 20, 2025, 04:57 PM UTC

   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..

2. monitoring Oct 20, 2025, 06:38 PM UTC

   The SMS OTP errors have subsided. We will continue to monitor the situation while our primary messaging provider investigates the incident..

3. resolved Oct 20, 2025, 06:40 PM UTC

   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..

Read the full incident report →

Started Oct 20, 2025, 04:29 PM UTC· resolved Oct 20, 2025, 06:01 PM UTC

1. investigating Oct 20, 2025, 04:29 PM UTC

   SAML SSO requests are currently failing as a downstream affect of the AWS outage. We're currently investigating ways to mitigate the issue..

2. resolved Oct 20, 2025, 06:01 PM UTC

   This incident has been resolved..

3. monitoring Oct 21, 2025, 09:27 PM UTC

   **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..

Read the full incident report →

Started Oct 20, 2025, 03:57 PM UTC· resolved Oct 20, 2025, 04:19 PM UTC

1. investigating Oct 20, 2025, 03:57 PM UTC

   We are currently investigating elevated DFP BLOCK rates..

2. resolved Oct 20, 2025, 04:19 PM UTC

   This incident has been resolved..

Read the full incident report →

Started Oct 09, 2025, 12:10 AM UTC· resolved Oct 10, 2025, 12:10 AM UTC

1. investigating Oct 09, 2025, 12:10 AM UTC

   We've received several reports of potential issues with delivery login emails to Yahoo Email inboxes..

2. resolved Oct 10, 2025, 12:10 AM UTC

   This incident has been resolved..

Read the full incident report →

Started Oct 07, 2025, 06:27 PM UTC· resolved Oct 07, 2025, 06:28 PM UTC

1. investigating Oct 07, 2025, 06:27 PM UTC

   We are investigating elevated API latencies..

2. resolved Oct 07, 2025, 06:28 PM UTC

   This incident has been resolved..

Read the full incident report →