Notice history

Sep 2025

Oct 2025

Nov 2025

Sep 2025

Oct 2025

Nov 2025

Sep 2025

Oct 2025

Nov 2025

Sep 2025

Oct 2025

Nov 2025

Sep 2025

Oct 2025

Nov 2025

Sep 2025

Oct 2025

Nov 2025

Resolved
November 18, 2025 at 12:10 PM
Resolved
November 18, 2025 at 12:10 PM
During Cloudflare's 2025-11-18 incident, 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.
Investigating
November 18, 2025 at 11:30 AM
Investigating
November 18, 2025 at 11:30 AM
We are currently investigating this incident.

Resolved
November 18, 2025 at 12:10 PM
Resolved
November 18, 2025 at 12:10 PM
During Cloudflare's 2025-11-18 incident, 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.
Monitoring
November 18, 2025 at 12:01 PM
Monitoring
November 18, 2025 at 12:01 PM
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.
Investigating
November 18, 2025 at 11:30 AM
Investigating
November 18, 2025 at 11:30 AM
We are currently investigating an increase in errors in the Stytch API due to impact from an upstream provider outage.

Resolved
November 13, 2025 at 2:20 PM
Resolved
November 13, 2025 at 2:20 PM
This incident has been resolved.
Monitoring
November 13, 2025 at 2:17 PM
Monitoring
November 13, 2025 at 2:17 PM
We implemented a fix and are currently monitoring the result.
Investigating
November 13, 2025 at 2:06 PM
Investigating
November 13, 2025 at 2:06 PM
We are currently investigating issues with increased latency in the live API.

Resolved
November 10, 2025 at 8:16 PM
Resolved
November 10, 2025 at 8:16 PM
This incident has been resolved.
Investigating
November 10, 2025 at 5:20 PM
Investigating
November 10, 2025 at 5:20 PM
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
October 20, 2025 at 6:40 PM
Resolved
October 20, 2025 at 6:40 PM
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.
Monitoring
October 20, 2025 at 6:38 PM
Monitoring
October 20, 2025 at 6:38 PM
The SMS OTP errors have subsided. We will continue to monitor the situation while our primary messaging provider investigates the incident.
Investigating
October 20, 2025 at 4:57 PM
Investigating
October 20, 2025 at 4:57 PM
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.

Postmortem
October 21, 2025 at 9:27 PM
Postmortem
October 21, 2025 at 9:27 PM
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.
Resolved
October 20, 2025 at 6:01 PM
Resolved
October 20, 2025 at 6:01 PM
This incident has been resolved.
Investigating
October 20, 2025 at 4:29 PM
Investigating
October 20, 2025 at 4:29 PM
SAML SSO requests are currently failing as a downstream affect of the AWS outage. We're currently investigating ways to mitigate the issue.

Resolved
October 20, 2025 at 4:19 PM
Resolved
October 20, 2025 at 4:19 PM
This incident has been resolved.
Investigating
October 20, 2025 at 3:57 PM
Investigating
October 20, 2025 at 3:57 PM
We are currently investigating elevated DFP BLOCK rates.

Resolved
October 10, 2025 at 12:10 AM
Resolved
October 10, 2025 at 12:10 AM
This incident has been resolved.
Investigating
October 09, 2025 at 12:10 AM
Investigating
October 09, 2025 at 12:10 AM
We've received several reports of potential issues with delivery login emails to Yahoo Email inboxes.

Resolved
October 07, 2025 at 6:28 PM
Resolved
October 07, 2025 at 6:28 PM
This incident has been resolved.
Investigating
October 07, 2025 at 6:27 PM
Investigating
October 07, 2025 at 6:27 PM
We are investigating elevated API latencies.

No notices reported this month

Sep 2025 to Nov 2025

Stytch - Notice history