Stytch - Notice history

All systems operational

Live API - Operational

100% - uptime
Mar 2025 · 99.993%Apr · 100.00%May · 100.00%

Previous page

Next page

Mar 2025
Apr 2025
May 2025

Test API - Operational

100% - uptime
Mar 2025 · 100.00%Apr · 100.00%May · 100.00%

Previous page

Next page

Mar 2025
Apr 2025
May 2025

Javascript SDK - Operational

100% - uptime
Mar 2025 · 100.00%Apr · 100.00%May · 100.00%

Previous page

Next page

Mar 2025
Apr 2025
May 2025

Device Fingerprinting - Operational

100% - uptime
Mar 2025 · 99.980%Apr · 99.972%May · 100.00%

Previous page

Next page

Mar 2025
Apr 2025
May 2025

Dashboard - Operational

100% - uptime
Mar 2025 · 100.00%Apr · 100.00%May · 100.00%

Previous page

Next page

Mar 2025
Apr 2025
May 2025

Message deliverability - Operational

100% - uptime
Mar 2025 · 100.00%Apr · 100.00%May · 100.00%

Previous page

Next page

Mar 2025
Apr 2025
May 2025

Notice history

May 2025

Increase in inappropriate 429 errors for SMS Sends in Consumer
  • Resolved
    Resolved
    This incident has been resolved.
  • Investigating
    Investigating

    We saw elevated 429 rate limit errors inappropriately applied within our Consumer API for the OTPsSMSSend endpoint. Our B2B product and other SMS sending endpoints, e.g. OTPsSMSLoginOrCreate, were unaffected.

Delayed SMS - AT&T
  • Resolved
    Resolved

    We have confirmed that traffic has returned to normal.

  • Monitoring
    Monitoring

    We are seeing a recovery in SMS delivery delays and are continuing to monitor.

  • Investigating
    Investigating

    We are seeing delays in some SMS messages sent on AT&T across multiple messaging providers.

Apr 2025

Increased in errors in device fingerprinting
  • Resolved
    Resolved

    We implemented a fix and are currently monitoring the result. Affected users may need to clear their cache to fully resolve the issue.

  • Investigating
    Investigating
    We are currently investigating this incident.

Mar 2025

Increase in 4xx errors in Device Fingerprinting
  • Resolved
    Resolved

    Fix has landed and Device Fingerprinting traffic is once again successful.

  • Identified
    Identified

    Issue has been identified and we're rolling out a fix.

  • Investigating
    Investigating

    We are currently investigating this incident.

Increased 5xx errors
  • Resolved
    Resolved

    This issue has been resolved.

  • Investigating
    Investigating

    We are seeing elevated 5xx errors.

Increased 500s
  • Resolved
    Resolved

    This incident has been fully resolved.

  • Monitoring
    Monitoring

    We implemented a fix and are seeings 500s decline, and are continuing to monitor.

  • Investigating
    Investigating

    We are seeing elevated levels of 500 errors, primarily with our Search endpoints. We are currently investigating this incident.

Mar 2025 to May 2025

Next