Stytch Status - Incident history https://status.stytch.com Stytch Tue, 6 Oct 2026 16:48:00 +0000 Increase in 500 errors Type: Incident Duration: 59 minutes Affected Components: Live API Oct 6, 16:49:00 GMT+0 - Resolved - This incident has been resolved. Oct 6, 16:48:00 GMT+0 - Investigating - We're investigating an increase in 500 errors in our Live API. Type: Incident

Duration: 59 minutes

Affected Components:

Oct 6, 16:49:00 GMT+0
Resolved - This incident has been resolved..

Oct 6, 16:48:00 GMT+0
Investigating - We're investigating an increase in 500 errors in our Live API..

]]> Tue, 6 Oct 2026 16:48:00 +0000 https://status.stytch.com/incident/cmuwxilb002zw1bplcf8ofz3i https://status.stytch.com/incident/cmuwxilb002zw1bplcf8ofz3i Scheduled Test API DB maintenance Type: Maintenance Duration: 30 minutes Affected Components: Test API Sep 10, 03:30:00 GMT+0 - Completed - Maintenance has completed successfully Sep 10, 03:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 8, 16:57:29 GMT+0 - Identified - We are planning for a scheduled maintenance during this time. We expect single digit minutes of increased latency during this window. Type: Maintenance

Duration: 30 minutes

Affected Components:

Sep 10, 03:30:00 GMT+0
Completed - Maintenance has completed successfully.

Sep 10, 03:00:01 GMT+0
Identified - Maintenance is now in progress.

Sep 8, 16:57:29 GMT+0
Identified - We are planning for a scheduled maintenance during this time. We expect single digit minutes of increased latency during this window..

]]> Thu, 10 Sep 2026 03:00:00 +0000 https://status.stytch.com/maintenance/cmtswx9470au513pqpc432583 https://status.stytch.com/maintenance/cmtswx9470au513pqpc432583 Investigating SMS deliverability issues to AT&T Wireless Type: Incident Duration: 2 hours and 16 minutes Affected Components: Message deliverability Sep 9, 17:00:00 GMT+0 - Resolved - SMS are being sent successfully to AT&T numbers. Sep 9, 16:43:00 GMT+0 - Monitoring - We've switched to an alternative messaging provider and are monitoring the result. Sep 9, 14:30:00 GMT+0 - Investigating - We're currently investigating SMS deliverability issues to AT&T Wireless. Type: Incident

Duration: 2 hours and 16 minutes

Affected Components:

Sep 9, 17:00:00 GMT+0
Resolved - SMS are being sent successfully to AT&T numbers..

Sep 9, 16:43:00 GMT+0
Monitoring - We've switched to an alternative messaging provider and are monitoring the result..

Sep 9, 14:30:00 GMT+0
Investigating - We're currently investigating SMS deliverability issues to AT&T Wireless..

]]> Wed, 9 Sep 2026 14:30:00 +0000 https://status.stytch.com/incident/cmtubw3qh0my413mrwz4gpxr7 https://status.stytch.com/incident/cmtubw3qh0my413mrwz4gpxr7 Small percentage of SMS requests resulting in 500 errors Type: Incident Duration: 57 minutes Affected Components: Message deliverability Sep 1, 17:27:00 GMT+0 - Resolved - This issue has been resolved. Sep 1, 16:30:00 GMT+0 - Investigating - A small percentage of SMS requests are currently resulting in 500 / internal\_server\_errors due to an upstream messaging issue. Type: Incident

Duration: 57 minutes

Affected Components:

Sep 1, 17:27:00 GMT+0
Resolved - This issue has been resolved..

Sep 1, 16:30:00 GMT+0
Investigating - A small percentage of SMS requests are currently resulting in 500 / internal\_server\_errors due to an upstream messaging issue..

]]> Tue, 1 Sep 2026 16:30:00 +0000 https://status.stytch.com/incident/cmtixrkeo0nvq13o1twzafs5p https://status.stytch.com/incident/cmtixrkeo0nvq13o1twzafs5p Delayed Event Log Streams Type: Incident Duration: 31 minutes Affected Components: Dashboard Aug 28, 23:00:01 GMT+0 - Resolved - This incident has been resolved. Delayed logs are now delivered. Aug 28, 22:29:00 GMT+0 - Investigating - We are currently investigating delayed logs in our Event Log Streaming feature. Type: Incident

Duration: 31 minutes

Affected Components:

Aug 28, 23:00:01 GMT+0
Resolved - This incident has been resolved. Delayed logs are now delivered..

Aug 28, 22:29:00 GMT+0
Investigating - We are currently investigating delayed logs in our Event Log Streaming feature..

]]> Fri, 28 Aug 2026 22:29:00 +0000 https://status.stytch.com/incident/cmtdjykwn03vv13miug34t66r https://status.stytch.com/incident/cmtdjykwn03vv13miug34t66r Emails not being delivered Type: Incident Duration: 5 hours and 18 minutes Affected Components: Message deliverability Aug 18, 00:00:00 GMT+0 - 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**: 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 `login@stytch.com`. 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 Aug 17, 13:00:00 GMT+0 - 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. Aug 17, 12:14:00 GMT+0 - Monitoring - We've mitigated the issue and emails are now being delivered. Currently monitoring. Aug 17, 09:27:00 GMT+0 - Investigating - We are currently investigating this incident. Type: Incident

Duration: 5 hours and 18 minutes

Affected Components:

Aug 18, 00:00:00 GMT+0
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**: 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 `login@stytch.com`. 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.

Aug 17, 13:00:00 GMT+0
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..

Aug 17, 12:14:00 GMT+0
Monitoring - We've mitigated the issue and emails are now being delivered. Currently monitoring..

Aug 17, 09:27:00 GMT+0
Investigating - We are currently investigating this incident..

]]> Mon, 17 Aug 2026 09:27:00 +0000 https://status.stytch.com/incident/cmsx7bm7805qd10pi1zmp87a5 https://status.stytch.com/incident/cmsx7bm7805qd10pi1zmp87a5 Increase in 500 errors Type: Incident Duration: 1 minute Affected Components: Javascript SDK, Test API, Live API Jul 27, 01:11:05 GMT+0 - Postmortem - An update to our DB caused around 1.5 minutes of increased 500's in our API. Apologies for the interruption. Jul 27, 00:36:00 GMT+0 - Resolved - This incident has been resolved. Jul 27, 00:35:00 GMT+0 - Investigating - We are currently investigating this incident. Type: Incident

Duration: 1 minute

Affected Components: , ,

Jul 27, 01:11:05 GMT+0
Postmortem - An update to our DB caused around 1.5 minutes of increased 500's in our API. Apologies for the interruption. .

Jul 27, 00:36:00 GMT+0
Resolved - This incident has been resolved..

Jul 27, 00:35:00 GMT+0
Investigating - We are currently investigating this incident..

]]> Mon, 27 Jul 2026 00:35:00 +0000 https://status.stytch.com/incident/cms2i0x1f0pir1aqd1b4erlfm https://status.stytch.com/incident/cms2i0x1f0pir1aqd1b4erlfm Increase in 5XX errors Type: Incident Duration: 15 minutes Affected Components: Live API Jul 24, 17:00:00 GMT+0 - 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. Jul 24, 11:11:00 GMT+0 - Resolved - This incident has been resolved. Jul 24, 10:56:00 GMT+0 - Investigating - We are investigating an increase in 5XX errors in the Stytch API. Type: Incident

Duration: 15 minutes

Affected Components:

Jul 24, 17:00:00 GMT+0
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..

Jul 24, 11:11:00 GMT+0
Resolved - This incident has been resolved..

Jul 24, 10:56:00 GMT+0
Investigating - We are investigating an increase in 5XX errors in the Stytch API..

]]> Fri, 24 Jul 2026 10:56:00 +0000 https://status.stytch.com/incident/cmrywd58x08910rlc3kazjxdr https://status.stytch.com/incident/cmrywd58x08910rlc3kazjxdr Issue causing invalid_email errors for some valid B2B email addresses Type: Incident Duration: 16 hours and 46 minutes Affected Components: Message deliverability Jun 16, 14:53:00 GMT+0 - Resolved - This issue has been resolved. Jun 15, 22:07:00 GMT+0 - Investigating - We've identified an issue causing invalid\_email errors for some B2B users with valid email addresses. Type: Incident

Duration: 16 hours and 46 minutes

Affected Components:

Jun 16, 14:53:00 GMT+0
Resolved - This issue has been resolved..

Jun 15, 22:07:00 GMT+0
Investigating - We've identified an issue causing invalid\_email errors for some B2B users with valid email addresses..

]]> Mon, 15 Jun 2026 22:07:00 +0000 https://status.stytch.com/incident/cmqgt9ndj00kn2jo3e1419uxv https://status.stytch.com/incident/cmqgt9ndj00kn2jo3e1419uxv SMS delivery is currently experiencing some delays. Type: Incident Duration: 1 hour and 2 minutes Affected Components: Message deliverability Jun 2, 19:00:00 GMT+0 - Resolved - This incident has been resolved. Jun 2, 18:41:00 GMT+0 - 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. Jun 2, 18:00:00 GMT+0 - Investigating - We are actively investigating SMS delivery delays with our primary messaging provider. Type: Incident

Duration: 1 hour and 2 minutes

Affected Components:

Jun 2, 19:00:00 GMT+0
Resolved - This incident has been resolved..

Jun 2, 18:41:00 GMT+0
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..

Jun 2, 18:00:00 GMT+0
Investigating - We are actively investigating SMS delivery delays with our primary messaging provider..

]]> Tue, 2 Jun 2026 18:00:00 +0000 https://status.stytch.com/incident/cmpx0175q0042p4nq1scqiq2f https://status.stytch.com/incident/cmpx0175q0042p4nq1scqiq2f Errors with custom auth domain creation Type: Incident Duration: 4 hours and 30 minutes Affected Components: Dashboard May 29, 22:41:34 GMT+0 - Resolved - This incident has been resolved. May 29, 18:12:00 GMT+0 - 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. Type: Incident

Duration: 4 hours and 30 minutes

Affected Components:

May 29, 22:41:34 GMT+0
Resolved - This incident has been resolved..

May 29, 18:12:00 GMT+0
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..

]]> Fri, 29 May 2026 18:12:00 +0000 https://status.stytch.com/incident/cmprgti1u01hkqxjh9ysthtk9 https://status.stytch.com/incident/cmprgti1u01hkqxjh9ysthtk9 Issues with Email Risk API Type: Incident Duration: 1 hour and 52 minutes Affected Components: Device Fingerprinting Apr 6, 17:00:00 GMT+0 - Resolved - This incident has been resolved. Apr 6, 16:45:00 GMT+0 - Monitoring - A fix has been implemented and we are currently monitoring the result. Apr 6, 14:52:56 GMT+0 - Investigating - We are currently investigating elevated 500 errors in the email risk API. Type: Incident

Duration: 1 hour and 52 minutes

Affected Components:

Apr 6, 17:00:00 GMT+0
Resolved - This incident has been resolved..

Apr 6, 16:45:00 GMT+0
Monitoring - A fix has been implemented and we are currently monitoring the result..

Apr 6, 14:52:56 GMT+0
Investigating - We are currently investigating elevated 500 errors in the email risk API..

]]> Mon, 6 Apr 2026 14:52:56 +0000 https://status.stytch.com/incident/cmnnb818v0qr6yn6v75phe0ci https://status.stytch.com/incident/cmnnb818v0qr6yn6v75phe0ci Internal Logging Disruption Type: Incident Duration: 4 hours and 51 minutes Jan 28, 20:55:00 GMT+0 - Resolved - This incident has been resolved. Jan 28, 20:23:00 GMT+0 - 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. Type: Incident

Duration: 4 hours and 51 minutes

Jan 28, 20:55:00 GMT+0
Resolved - This incident has been resolved..

Jan 28, 20:23:00 GMT+0
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..

]]> Wed, 28 Jan 2026 20:23:00 +0000 https://status.stytch.com/incident/cmkyikbok054dah4dhiwrbqid https://status.stytch.com/incident/cmkyikbok054dah4dhiwrbqid Outlook incident - emails not getting delivered Type: Incident Jan 27, 13:00:00 GMT+0 - 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/) Type: Incident

Jan 27, 13:00:00 GMT+0
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/).

]]> Tue, 27 Jan 2026 13:00:00 +0000 https://status.stytch.com/incident/cmkwydalq0033ff6nvlej3xjw https://status.stytch.com/incident/cmkwydalq0033ff6nvlej3xjw Gmail incident - delayed emails Type: Incident Duration: 14 hours and 29 minutes Affected Components: Message deliverability Jan 25, 03:30:57 GMT+0 - Resolved - This incident has been resolved. Jan 24, 21:12:10 GMT+0 - Monitoring - Reports of delivery issues has dropped but is still not back to normal. We're continuing to monitor. Jan 24, 17:22:06 GMT+0 - Monitoring - Continuing to monitor. Jan 24, 13:02:00 GMT+0 - Investigating - Gmail is currently experiencing an incident that is causing delayed emails for end users. You can follow along with their incident here: <https://www.google.com/appsstatus/dashboard/incidents/NNnDkY9CJ36annsfytjQ> We'll be monitoring and will resolve this incident when we've confirmed delivery returns to normal for Gmail users. Type: Incident

Duration: 14 hours and 29 minutes

Affected Components:

Jan 25, 03:30:57 GMT+0
Resolved - This incident has been resolved..

Jan 24, 21:12:10 GMT+0
Monitoring - Reports of delivery issues has dropped but is still not back to normal. We're continuing to monitor..

Jan 24, 17:22:06 GMT+0
Monitoring - Continuing to monitor..

Jan 24, 13:02:00 GMT+0
Investigating - Gmail is currently experiencing an incident that is causing delayed emails for end users. You can follow along with their incident here: <https://www.google.com/appsstatus/dashboard/incidents/NNnDkY9CJ36annsfytjQ> We'll be monitoring and will resolve this incident when we've confirmed delivery returns to normal for Gmail users..

]]> Sat, 24 Jan 2026 13:02:00 +0000 https://status.stytch.com/incident/cmksksz0j0jkj8iu99xldo8fy https://status.stytch.com/incident/cmksksz0j0jkj8iu99xldo8fy Increased 4XX and 5XX errors with Connected Apps Type: Incident Duration: 36 minutes Affected Components: Device Fingerprinting, Test API, Live API, Dashboard, Javascript SDK, Message deliverability Dec 22, 22:35:00 GMT+0 - Resolved - This incident has been resolved. Dec 22, 22:30:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Dec 22, 21:59:00 GMT+0 - Identified - We have identified an issue with Connected Apps caused by a recent change and are currently implementing a fix. Type: Incident

Duration: 36 minutes

Affected Components: , , , , ,

Dec 22, 22:35:00 GMT+0
Resolved - This incident has been resolved..

Dec 22, 22:30:00 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Dec 22, 21:59:00 GMT+0
Identified - We have identified an issue with Connected Apps caused by a recent change and are currently implementing a fix..

]]> Mon, 22 Dec 2025 21:59:00 +0000 https://status.stytch.com/incident/cmjhptdsw08jo14bla3r0ftv0 https://status.stytch.com/incident/cmjhptdsw08jo14bla3r0ftv0 Elevated error rates for SAML SSO flow Type: Incident Duration: 9 minutes Affected Components: Test API, Live API Dec 19, 16:52:00 GMT+0 - Resolved - This incident has been resolved. SAML SSO traffic is healthy. Dec 19, 16:51:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Dec 19, 16:30:00 GMT+0 - Investigating - We are actively investigating an elevated rate of SAML SSO errors. Type: Incident

Duration: 9 minutes

Affected Components: ,

Dec 19, 16:52:00 GMT+0
Resolved - This incident has been resolved. SAML SSO traffic is healthy..

Dec 19, 16:51:00 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Dec 19, 16:30:00 GMT+0
Investigating - We are actively investigating an elevated rate of SAML SSO errors..

]]> Fri, 19 Dec 2025 16:30:00 +0000 https://status.stytch.com/incident/cmjd3r38v04jk9pamutqhsi6d https://status.stytch.com/incident/cmjd3r38v04jk9pamutqhsi6d Inability to load frontend script from Cloudflare custom domain Type: Incident Duration: 1 hour and 40 minutes Affected Components: Device Fingerprinting Nov 18, 12:10:00 GMT+0 - 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 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. Nov 18, 11:30:00 GMT+0 - Investigating - We are currently investigating this incident. Type: Incident

Duration: 1 hour and 40 minutes

Affected Components:

Nov 18, 12:10:00 GMT+0
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 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..

Nov 18, 11:30:00 GMT+0
Investigating - We are currently investigating this incident..

]]> Tue, 18 Nov 2025 11:30:00 +0000 https://status.stytch.com/incident/cmi6np63m00t0ekn395p7bgpy https://status.stytch.com/incident/cmi6np63m00t0ekn395p7bgpy Elevated error rate in API Type: Incident Affected Components: Test API, Live API, Javascript SDK Nov 18, 12:10:00 GMT+0 - 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 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. Nov 18, 12:01:00 GMT+0 - 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. Nov 18, 11:30:00 GMT+0 - Investigating - We are currently investigating an increase in errors in the Stytch API due to impact from an upstream provider outage. Type: Incident

Affected Components: , ,

Nov 18, 12:10:00 GMT+0
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 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..

Nov 18, 12:01:00 GMT+0
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..

Nov 18, 11:30:00 GMT+0
Investigating - We are currently investigating an increase in errors in the Stytch API due to impact from an upstream provider outage..

]]> Tue, 18 Nov 2025 11:30:00 +0000 https://status.stytch.com/incident/cmi4jnk9j0003hilezbsh2r0k https://status.stytch.com/incident/cmi4jnk9j0003hilezbsh2r0k Increased latency in the live API Type: Incident Duration: 34 minutes Affected Components: Live API Nov 13, 14:20:00 GMT+0 - Resolved - This incident has been resolved. Nov 13, 14:17:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Nov 13, 14:06:00 GMT+0 - Investigating - We are currently investigating issues with increased latency in the live API. Type: Incident

Duration: 34 minutes

Affected Components:

Nov 13, 14:20:00 GMT+0
Resolved - This incident has been resolved..

Nov 13, 14:17:00 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Nov 13, 14:06:00 GMT+0
Investigating - We are currently investigating issues with increased latency in the live API..

]]> Thu, 13 Nov 2025 14:06:00 +0000 https://status.stytch.com/incident/cmhximlrs03jwhqpozv9o1sgu https://status.stytch.com/incident/cmhximlrs03jwhqpozv9o1sgu Device Fingerprinting pages unavailable in the Dashboard Type: Incident Duration: 47 minutes Affected Components: Dashboard, Message deliverability Nov 10, 20:16:30 GMT+0 - Resolved - This incident has been resolved. Nov 10, 17:20:00 GMT+0 - 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. Type: Incident

Duration: 47 minutes

Affected Components: ,

Nov 10, 20:16:30 GMT+0
Resolved - This incident has been resolved..

Nov 10, 17:20:00 GMT+0
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..

]]> Mon, 10 Nov 2025 17:20:00 +0000 https://status.stytch.com/incident/cmhtl0iz3013i119rtwr51pzr https://status.stytch.com/incident/cmhtl0iz3013i119rtwr51pzr Elevated SMS OTP errors/ delays Type: Incident Duration: 3 hours and 39 minutes Affected Components: Message deliverability Oct 20, 18:40:00 GMT+0 - 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. Oct 20, 18:38:00 GMT+0 - Monitoring - The SMS OTP errors have subsided. We will continue to monitor the situation while our primary messaging provider investigates the incident. Oct 20, 16:57:00 GMT+0 - 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. Type: Incident

Duration: 3 hours and 39 minutes

Affected Components:

Oct 20, 18:40:00 GMT+0
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..

Oct 20, 18:38:00 GMT+0
Monitoring - The SMS OTP errors have subsided. We will continue to monitor the situation while our primary messaging provider investigates the incident..

Oct 20, 16:57:00 GMT+0
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..

]]> Mon, 20 Oct 2025 16:57:00 +0000 https://status.stytch.com/incident/cmgzdh3ty05sszejad6bwsml3 https://status.stytch.com/incident/cmgzdh3ty05sszejad6bwsml3 SAML SSO requests failing Type: Incident Duration: 1 hour and 12 minutes Affected Components: Test API, Live API, Javascript SDK Oct 21, 21:27:25 GMT+0 - 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 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. Oct 20, 18:01:00 GMT+0 - Resolved - This incident has been resolved. Oct 20, 16:29:00 GMT+0 - Investigating - SAML SSO requests are currently failing as a downstream affect of the AWS outage. We're currently investigating ways to mitigate the issue. Type: Incident

Duration: 1 hour and 12 minutes

Affected Components: , ,

Oct 21, 21:27:25 GMT+0
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 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..

Oct 20, 18:01:00 GMT+0
Resolved - This incident has been resolved..

Oct 20, 16:29:00 GMT+0
Investigating - SAML SSO requests are currently failing as a downstream affect of the AWS outage. We're currently investigating ways to mitigate the issue..

]]> Mon, 20 Oct 2025 16:29:00 +0000 https://status.stytch.com/incident/cmgzdn6k903jgjzg6u94ljjdh https://status.stytch.com/incident/cmgzdn6k903jgjzg6u94ljjdh Elevated BLOCK rates Type: Incident Duration: 23 minutes Affected Components: Device Fingerprinting Oct 20, 16:19:56 GMT+0 - Resolved - This incident has been resolved. Oct 20, 15:57:01 GMT+0 - Investigating - We are currently investigating elevated DFP BLOCK rates. Type: Incident

Duration: 23 minutes

Affected Components:

Oct 20, 16:19:56 GMT+0
Resolved - This incident has been resolved..

Oct 20, 15:57:01 GMT+0
Investigating - We are currently investigating elevated DFP BLOCK rates..

]]> Mon, 20 Oct 2025 15:57:01 +0000 https://status.stytch.com/incident/cmgzbjcbr03huvl2l9w8k0f2z https://status.stytch.com/incident/cmgzbjcbr03huvl2l9w8k0f2z Investigating report of email deliverability issues Type: Incident Duration: 1 day Affected Components: Message deliverability Oct 10, 00:10:00 GMT+0 - Resolved - This incident has been resolved. Oct 9, 00:10:04 GMT+0 - Investigating - We've received several reports of potential issues with delivery login emails to Yahoo Email inboxes. Type: Incident

Duration: 1 day

Affected Components:

Oct 10, 00:10:00 GMT+0
Resolved - This incident has been resolved..

Oct 9, 00:10:04 GMT+0
Investigating - We've received several reports of potential issues with delivery login emails to Yahoo Email inboxes..

]]> Thu, 9 Oct 2025 00:10:04 +0000 https://status.stytch.com/incident/cmginv6no00yysf24z9d323ze https://status.stytch.com/incident/cmginv6no00yysf24z9d323ze The Stytch API is currently experiencing issues. Type: Incident Duration: 1 minute Affected Components: Live API Oct 7, 18:28:00 GMT+0 - Resolved - This incident has been resolved. Oct 7, 18:27:00 GMT+0 - Investigating - We are investigating elevated API latencies. Type: Incident

Duration: 1 minute

Affected Components:

Oct 7, 18:28:00 GMT+0
Resolved - This incident has been resolved..

Oct 7, 18:27:00 GMT+0
Investigating - We are investigating elevated API latencies..

]]> Tue, 7 Oct 2025 18:27:00 +0000 https://status.stytch.com/incident/cmggz0uhc0360kdz6yhf3bw8m https://status.stytch.com/incident/cmggz0uhc0360kdz6yhf3bw8m Scheduled maintenance in our Test environment Type: Maintenance Duration: 1 hour Affected Components: Test API Sep 20, 19:00:00 GMT+0 - Completed - Maintenance has completed successfully Sep 20, 18:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 20, 18:00:00 GMT+0 - Identified - We are performing routine database maintenance and our Test environment may experience some brief instability. Type: Maintenance

Duration: 1 hour

Affected Components:

Sep 20, 19:00:00 GMT+0
Completed - Maintenance has completed successfully.

Sep 20, 18:00:01 GMT+0
Identified - Maintenance is now in progress.

Sep 20, 18:00:00 GMT+0
Identified - We are performing routine database maintenance and our Test environment may experience some brief instability..

]]> Wed, 20 Sep 2023 18:00:00 +0000 https://status.stytch.com/maintenance/clms17owm34372bnodonp8z8a3 https://status.stytch.com/maintenance/clms17owm34372bnodonp8z8a3 Scheduled maintenance in our Test environment Type: Maintenance Duration: 5 minutes Affected Components: Test API Sep 20, 17:05:00 GMT+0 - Completed - Maintenance has completed successfully Sep 20, 17:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 20, 17:00:00 GMT+0 - Identified - We are planning for some scheduled maintenance in our Test environment. There may be increased 500's in our Test API during this time, there will be no impact to our Live environment. Type: Maintenance

Duration: 5 minutes

Affected Components:

Sep 20, 17:05:00 GMT+0
Completed - Maintenance has completed successfully.

Sep 20, 17:00:01 GMT+0
Identified - Maintenance is now in progress.

Sep 20, 17:00:00 GMT+0
Identified - We are planning for some scheduled maintenance in our Test environment. There may be increased 500's in our Test API during this time, there will be no impact to our Live environment..

]]> Wed, 20 Sep 2023 17:00:00 +0000 https://status.stytch.com/maintenance/clmkswt8n162658bnonbb03fc9y https://status.stytch.com/maintenance/clmkswt8n162658bnonbb03fc9y