Stytch - Notice history

All systems operational

Live API - Operational

99.996% uptime
Sep 2025 · 100.00%Oct · 99.990%Nov · 100.00%

Previous page

Next page

Sep 2025
Oct 2025
Nov 2025

Test API - Operational

99.996% uptime
Sep 2025 · 100.00%Oct · 99.990%Nov · 100.00%

Previous page

Next page

Sep 2025
Oct 2025
Nov 2025

Javascript SDK - Operational

100.00% uptime
Sep 2025 · 100.00%Oct · 100.00%Nov · 100.00%

Previous page

Next page

Sep 2025
Oct 2025
Nov 2025

Device Fingerprinting - Operational

100.00% uptime
Sep 2025 · 100.00%Oct · 99.999%Nov · 100.00%

Previous page

Next page

Sep 2025
Oct 2025
Nov 2025

Dashboard - Operational

100.00% uptime
Sep 2025 · 100.00%Oct · 100.00%Nov · 100.00%

Previous page

Next page

Sep 2025
Oct 2025
Nov 2025

Message deliverability - Operational

99.993% uptime
Sep 2025 · 100.00%Oct · 99.979%Nov · 100.00%

Previous page

Next page

Sep 2025
Oct 2025
Nov 2025

Notice history

View current status

Nov 2025

Inability to load frontend script from Cloudflare custom domain
ResolvedDegraded performance40 minutes
  • ResolvedUTC

    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.

  • InvestigatingUTC
    We are currently investigating this incident.
Elevated error rate in API
ResolvedDegraded performance40 minutes
  • ResolvedUTC

    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.

  • MonitoringUTC

    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.

  • InvestigatingUTC

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

Increased latency in the live API
ResolvedDegraded performance14 minutes
  • ResolvedUTC
    This incident has been resolved.
  • MonitoringUTC
    We implemented a fix and are currently monitoring the result.
  • InvestigatingUTC

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

Device Fingerprinting pages unavailable in the Dashboard
ResolvedDegraded performance2 hours 56 minutes
  • ResolvedUTC
    This incident has been resolved.
  • InvestigatingUTC

    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.

Oct 2025

Elevated SMS OTP errors/ delays
ResolvedDegraded performance1 hour 43 minutes
  • ResolvedUTC

    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.

  • MonitoringUTC

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

  • InvestigatingUTC

    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.

SAML SSO requests failing
ResolvedDegraded performance1 hour 32 minutes
  • PostmortemUTC

    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.

  • ResolvedUTC

    This incident has been resolved.

  • InvestigatingUTC

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

Elevated BLOCK rates
ResolvedDegraded performance22 minutes
  • ResolvedUTC
    This incident has been resolved.
  • InvestigatingUTC

    We are currently investigating elevated DFP BLOCK rates.

Investigating report of email deliverability issues
ResolvedDegraded performance23 hours 59 minutes
  • ResolvedUTC
    This incident has been resolved.
  • InvestigatingUTC

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

The Stytch API is currently experiencing issues.
ResolvedDegraded performance1 minute
  • ResolvedUTC

    This incident has been resolved.

  • InvestigatingUTC

    We are investigating elevated API latencies.

Sep 2025

No notices reported this month

Previous

Sep 2025 to Nov 2025

Next