<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:status.stytch.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://status.stytch.com"/>
  <link rel="self" type="application/atom+xml" href="https://status.stytch.com/history.atom"/>
  <title>Stytch Status - Incident history</title>
  <updated>2026-01-28T20:23:00.000+00:00</updated>
  <author>
    <name>Stytch</name>
  </author>
  
<entry>
  <id>tag:status.stytch.com,2005:Incident/cmkyikbok054dah4dhiwrbqid</id>
  <published>2026-01-28T20:23:00.000+00:00</published>
  <updated>2026-01-28T20:23:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.stytch.com/incident/cmkyikbok054dah4dhiwrbqid"/>
  <title>Internal Logging Disruption</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 51 minutes</p>
    
    <p><small>Jan <var data-var='date'> 28</var>, <var data-var='time'>20:23:00</var> GMT+0</small><br /><strong>Identified</strong> -
  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..</p>
<p><small>Jan <var data-var='date'> 28</var>, <var data-var='time'>20:55:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.stytch.com,2005:Incident/cmkwydalq0033ff6nvlej3xjw</id>
  <published>2026-01-27T13:00:00.000+00:00</published>
  <updated>2026-01-27T13:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.stytch.com/incident/cmkwydalq0033ff6nvlej3xjw"/>
  <title>Outlook incident - emails not getting delivered</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    
    <p><small>Jan <var data-var='date'> 27</var>, <var data-var='time'>13:00:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  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&#039;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&#039;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/).</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.stytch.com,2005:Incident/cmksksz0j0jkj8iu99xldo8fy</id>
  <published>2026-01-24T13:02:00.000+00:00</published>
  <updated>2026-01-25T03:30:57.806+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.stytch.com/incident/cmksksz0j0jkj8iu99xldo8fy"/>
  <title>Gmail incident - delayed emails</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 14 hours and 29 minutes</p>
    <p><strong>Affected Components:</strong> Message deliverability</p>
    <p><small>Jan <var data-var='date'> 25</var>, <var data-var='time'>03:30:57</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jan <var data-var='date'> 24</var>, <var data-var='time'>13:02:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Gmail is currently experiencing an incident that is causing delayed emails for end users. 

You can follow along with their incident here: &lt;https://www.google.com/appsstatus/dashboard/incidents/NNnDkY9CJ36annsfytjQ&gt;

We&#039;ll be monitoring and will resolve this incident when we&#039;ve confirmed delivery returns to normal for Gmail users..</p>
<p><small>Jan <var data-var='date'> 24</var>, <var data-var='time'>17:22:06</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Continuing to monitor..</p>
<p><small>Jan <var data-var='date'> 24</var>, <var data-var='time'>21:12:10</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Reports of delivery issues has dropped but is still not back to normal.

We&#039;re continuing to monitor..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.stytch.com,2005:Incident/cmjhptdsw08jo14bla3r0ftv0</id>
  <published>2025-12-22T21:59:00.000+00:00</published>
  <updated>2025-12-22T22:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.stytch.com/incident/cmjhptdsw08jo14bla3r0ftv0"/>
  <title>Increased 4XX and 5XX errors with Connected Apps</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 36 minutes</p>
    <p><strong>Affected Components:</strong> Device Fingerprinting, Test API, Live API, Dashboard, Javascript SDK, Message deliverability</p>
    <p><small>Dec <var data-var='date'> 22</var>, <var data-var='time'>22:30:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Dec <var data-var='date'> 22</var>, <var data-var='time'>21:59:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified an issue with Connected Apps caused by a recent change and are currently implementing a fix..</p>
<p><small>Dec <var data-var='date'> 22</var>, <var data-var='time'>22:35:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.stytch.com,2005:Incident/cmjd3r38v04jk9pamutqhsi6d</id>
  <published>2025-12-19T16:30:00.000+00:00</published>
  <updated>2025-12-19T16:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.stytch.com/incident/cmjd3r38v04jk9pamutqhsi6d"/>
  <title>Elevated error rates for SAML SSO flow </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 9 minutes</p>
    <p><strong>Affected Components:</strong> Test API, Live API</p>
    <p><small>Dec <var data-var='date'> 19</var>, <var data-var='time'>16:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are actively investigating an elevated rate of SAML SSO errors..</p>
<p><small>Dec <var data-var='date'> 19</var>, <var data-var='time'>16:51:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Dec <var data-var='date'> 19</var>, <var data-var='time'>16:52:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. SAML SSO traffic is healthy..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.stytch.com,2005:Incident/cmi4jnk9j0003hilezbsh2r0k</id>
  <published>2025-11-18T11:30:00.000+00:00</published>
  <updated>2025-11-18T11:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.stytch.com/incident/cmi4jnk9j0003hilezbsh2r0k"/>
  <title>Elevated error rate in API</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Test API, Live API, Javascript SDK</p>
    <p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>11:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating an increase in errors in the Stytch API due to impact from an upstream provider outage..</p>
<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>12:01:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  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..</p>
<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>12:10:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  During [Cloudflare&#039;s 2025-11-18 incident](https://blog.cloudflare.com/18-november-2025-outage/), Stytch&#039;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&#039;ve created this incident for posterity for customers investigating downtime in their own systems..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.stytch.com,2005:Incident/cmi6np63m00t0ekn395p7bgpy</id>
  <published>2025-11-18T11:30:00.000+00:00</published>
  <updated>2025-11-18T11:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.stytch.com/incident/cmi6np63m00t0ekn395p7bgpy"/>
  <title>Inability to load frontend script from Cloudflare custom domain</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 40 minutes</p>
    <p><strong>Affected Components:</strong> Device Fingerprinting</p>
    <p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>11:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>12:10:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  During [Cloudflare&#039;s 2025-11-18 incident](https://blog.cloudflare.com/18-november-2025-outage/), loading of Device Fingerprinting&#039;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..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.stytch.com,2005:Incident/cmhximlrs03jwhqpozv9o1sgu</id>
  <published>2025-11-13T14:06:00.000+00:00</published>
  <updated>2025-11-13T14:06:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.stytch.com/incident/cmhximlrs03jwhqpozv9o1sgu"/>
  <title>Increased latency in the live API</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 34 minutes</p>
    <p><strong>Affected Components:</strong> Live API</p>
    <p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>14:06:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating issues with increased latency in the live API..</p>
<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>14:17:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>14:20:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.stytch.com,2005:Incident/cmhtl0iz3013i119rtwr51pzr</id>
  <published>2025-11-10T17:20:00.000+00:00</published>
  <updated>2025-11-10T17:20:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.stytch.com/incident/cmhtl0iz3013i119rtwr51pzr"/>
  <title>Device Fingerprinting pages unavailable in the Dashboard</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 47 minutes</p>
    <p><strong>Affected Components:</strong> Dashboard, Message deliverability</p>
    <p><small>Nov <var data-var='date'> 10</var>, <var data-var='time'>17:20:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  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..</p>
<p><small>Nov <var data-var='date'> 10</var>, <var data-var='time'>20:16:30</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.stytch.com,2005:Incident/cmgzdh3ty05sszejad6bwsml3</id>
  <published>2025-10-20T16:57:00.000+00:00</published>
  <updated>2025-10-20T16:57:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.stytch.com/incident/cmgzdh3ty05sszejad6bwsml3"/>
  <title>Elevated SMS OTP errors/ delays</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 39 minutes</p>
    <p><strong>Affected Components:</strong> Message deliverability</p>
    <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>16:57:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  SMS OTP error rates and delays are currently elevated due to an incident from our primary messaging provider (related to AWS outage). We&#039;re assessing whether it makes sense to switch to a backup provider..</p>
<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>18:38:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  The SMS OTP errors have subsided. We will continue to monitor the situation while our primary messaging provider investigates the incident..</p>
<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>18:40:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  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..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.stytch.com,2005:Incident/cmgzdn6k903jgjzg6u94ljjdh</id>
  <published>2025-10-20T16:29:00.000+00:00</published>
  <updated>2025-10-20T18:01:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.stytch.com/incident/cmgzdn6k903jgjzg6u94ljjdh"/>
  <title>SAML SSO requests failing</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 12 minutes</p>
    <p><strong>Affected Components:</strong> Test API, Live API, Javascript SDK</p>
    <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>18:01:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>16:29:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  SAML SSO requests are currently failing as a downstream affect of the AWS outage. We&#039;re currently investigating ways to mitigate the issue..</p>
<p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>21:27:25</var> GMT+0</small><br /><strong>Postmortem</strong> -
  **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..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.stytch.com,2005:Incident/cmgzbjcbr03huvl2l9w8k0f2z</id>
  <published>2025-10-20T15:57:01.211+00:00</published>
  <updated>2025-10-20T15:57:01.211+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.stytch.com/incident/cmgzbjcbr03huvl2l9w8k0f2z"/>
  <title>Elevated BLOCK rates</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 23 minutes</p>
    <p><strong>Affected Components:</strong> Device Fingerprinting</p>
    <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>15:57:01</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating elevated DFP BLOCK rates..</p>
<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>16:19:56</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.stytch.com,2005:Incident/cmginv6no00yysf24z9d323ze</id>
  <published>2025-10-09T00:10:04.363+00:00</published>
  <updated>2025-10-09T00:10:04.363+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.stytch.com/incident/cmginv6no00yysf24z9d323ze"/>
  <title>Investigating report of email deliverability issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day</p>
    <p><strong>Affected Components:</strong> Message deliverability</p>
    <p><small>Oct <var data-var='date'> 9</var>, <var data-var='time'>00:10:04</var> GMT+0</small><br /><strong>Investigating</strong> -
  We&#039;ve received several reports of potential issues with delivery login emails to Yahoo Email inboxes..</p>
<p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>00:10:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.stytch.com,2005:Incident/cmggz0uhc0360kdz6yhf3bw8m</id>
  <published>2025-10-07T18:27:00.000+00:00</published>
  <updated>2025-10-07T18:27:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.stytch.com/incident/cmggz0uhc0360kdz6yhf3bw8m"/>
  <title>The Stytch API is currently experiencing issues.</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 minute</p>
    <p><strong>Affected Components:</strong> Live API</p>
    <p><small>Oct <var data-var='date'> 7</var>, <var data-var='time'>18:27:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are investigating elevated API latencies..</p>
<p><small>Oct <var data-var='date'> 7</var>, <var data-var='time'>18:28:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.stytch.com,2005:Incident/cmggwmvvh01nybxnszgbyszvz</id>
  <published>2025-10-07T17:39:00.000+00:00</published>
  <updated>2025-10-07T17:39:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.stytch.com/incident/cmggwmvvh01nybxnszgbyszvz"/>
  <title>Increased errors in device fingerprinting</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 minutes</p>
    <p><strong>Affected Components:</strong> Device Fingerprinting</p>
    <p><small>Oct <var data-var='date'> 7</var>, <var data-var='time'>17:39:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are investigating an increase in errors in the device fingerprinting product..</p>
<p><small>Oct <var data-var='date'> 7</var>, <var data-var='time'>17:41:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.stytch.com,2005:Incident/cmekljo5h00c2rjh1tozl9dlb</id>
  <published>2025-08-20T22:40:00.000+00:00</published>
  <updated>2025-08-21T01:39:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.stytch.com/incident/cmekljo5h00c2rjh1tozl9dlb"/>
  <title>Increase in 500 errors</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 15 minutes</p>
    <p><strong>Affected Components:</strong> Test API</p>
    <p><small>Aug <var data-var='date'> 21</var>, <var data-var='time'>01:39:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  Fix has landed and 500&#039;s have resolved..</p>
<p><small>Aug <var data-var='date'> 20</var>, <var data-var='time'>22:40:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We&#039;ve received reports of 500 errors on Magic Link email sends. We are currently investigating this incident..</p>
<p><small>Aug <var data-var='date'> 21</var>, <var data-var='time'>01:45:00</var> GMT+0</small><br /><strong>Postmortem</strong> -
  A bug was shipped at approximately 22:40Z that caused some email templates in Test Projects to enter an unexpected state and return a 500 when used to send an Email Magic Link..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.stytch.com,2005:Incident/cmd90mg9r00bp9sbtdt8xwjpj</id>
  <published>2025-07-18T15:35:00.000+00:00</published>
  <updated>2025-07-18T16:36:26.181+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.stytch.com/incident/cmd90mg9r00bp9sbtdt8xwjpj"/>
  <title>Google incident causing increased errors for Google OAuth</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 1 minute</p>
    <p><strong>Affected Components:</strong> Live API</p>
    <p><small>Jul <var data-var='date'> 18</var>, <var data-var='time'>16:36:26</var> GMT+0</small><br /><strong>Resolved</strong> -
  Google has marked their incident as resolved..</p>
<p><small>Jul <var data-var='date'> 18</var>, <var data-var='time'>15:35:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  A Google incident impacting their OAuth flow has caused increased latency and errors.

https://www.google.com/appsstatus/dashboard/incidents/oFcAZTr4EVieF5Fr6Ee9

Google has closed the incident but we are continuing to monitor..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.stytch.com,2005:Incident/cmd7htqvd0002e01fwins3nep</id>
  <published>2025-07-17T09:20:00.000+00:00</published>
  <updated>2025-07-17T14:49:09.636+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.stytch.com/incident/cmd7htqvd0002e01fwins3nep"/>
  <title>Event log streaming delayed</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours and 29 minutes</p>
    <p><strong>Affected Components:</strong> Live API, Test API</p>
    <p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>14:49:09</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. Event logs should be streaming normally..</p>
<p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>14:27:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We have identified the root cause and are implementing a fix..</p>
<p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>09:20:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are investigating reports of event log streams being delayed..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.stytch.com,2005:Incident/cmcrxjdo400csi9i5imtihaqw</id>
  <published>2025-07-06T17:11:55.640+00:00</published>
  <updated>2025-07-06T17:11:55.640+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.stytch.com/incident/cmcrxjdo400csi9i5imtihaqw"/>
  <title>Bounce rate for email sending is high</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 34 minutes</p>
    <p><strong>Affected Components:</strong> Message deliverability</p>
    <p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>17:11:55</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>17:27:59</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>19:45:43</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.stytch.com,2005:Incident/cmbiy6qyn001d1pj9foxal57o</id>
  <published>2025-06-05T05:34:00.000+00:00</published>
  <updated>2025-06-05T05:34:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.stytch.com/incident/cmbiy6qyn001d1pj9foxal57o"/>
  <title>Spike in 5XX errors</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Live API</p>
    <p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>05:34:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.stytch.com,2005:Incident/cmb6ldzwe000h39arkjr9n4ft</id>
  <published>2025-05-27T14:08:57.543+00:00</published>
  <updated>2025-05-27T14:08:57.543+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.stytch.com/incident/cmb6ldzwe000h39arkjr9n4ft"/>
  <title>Some Dashboard pages inaccessible </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 30 minutes</p>
    <p><strong>Affected Components:</strong> Dashboard</p>
    <p><small>May <var data-var='date'> 27</var>, <var data-var='time'>14:08:57</var> GMT+0</small><br /><strong>Identified</strong> -
  An issue with a third-party service Stytch utilizes is experiencing issues which is preventing certain Dashboard pages, like the Device Fingerprinting Dashboard, from being accessible. 

We are working with this vendor on a fix..</p>
<p><small>May <var data-var='date'> 27</var>, <var data-var='time'>14:50:40</var> GMT+0</small><br /><strong>Monitoring</strong> -
  The vendor fixed the issue. You may still see issues as the cache is cleared. We are monitoring to verify the fix.</p>
<p><small>May <var data-var='date'> 27</var>, <var data-var='time'>15:39:11</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.stytch.com,2005:Incident/cmaydf09v0049q1m9bk1uxef7</id>
  <published>2025-05-21T18:45:00.000+00:00</published>
  <updated>2025-05-21T18:45:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.stytch.com/incident/cmaydf09v0049q1m9bk1uxef7"/>
  <title>Increase in inappropriate 429 errors for SMS Sends in Consumer</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 11 minutes</p>
    <p><strong>Affected Components:</strong> Message deliverability</p>
    <p><small>May <var data-var='date'> 21</var>, <var data-var='time'>18:45:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  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..</p>
<p><small>May <var data-var='date'> 21</var>, <var data-var='time'>19:56:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.stytch.com,2005:Incident/cma5kut9z001ooh5pte0te7fa</id>
  <published>2025-05-01T16:26:33.349+00:00</published>
  <updated>2025-05-01T16:26:33.349+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.stytch.com/incident/cma5kut9z001ooh5pte0te7fa"/>
  <title>Delayed SMS - AT&amp;T</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 hours and 39 minutes</p>
    <p><strong>Affected Components:</strong> Message deliverability</p>
    <p><small>May <var data-var='date'> 1</var>, <var data-var='time'>16:26:33</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are seeing delays in some SMS messages sent on AT&amp;T across multiple messaging providers. .</p>
<p><small>May <var data-var='date'> 1</var>, <var data-var='time'>19:46:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We are seeing a recovery in SMS delivery delays and are continuing to monitor. .</p>
<p><small>May <var data-var='date'> 2</var>, <var data-var='time'>01:05:10</var> GMT+0</small><br /><strong>Resolved</strong> -
  We have confirmed that traffic has returned to normal..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.stytch.com,2005:Incident/cm9al7g6i003tgg2xs7ag97fh</id>
  <published>2025-04-09T22:42:00.000+00:00</published>
  <updated>2025-04-09T22:42:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.stytch.com/incident/cm9al7g6i003tgg2xs7ag97fh"/>
  <title>Increased in errors in device fingerprinting</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 19 minutes</p>
    <p><strong>Affected Components:</strong> Device Fingerprinting</p>
    <p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>22:42:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>23:22:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  We implemented a fix and are currently monitoring the result. Affected users may need to clear their cache to fully resolve the issue..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.stytch.com,2005:Incident/cm8nlx1q300faaygk50zy8eil</id>
  <published>2025-03-24T21:56:43.912+00:00</published>
  <updated>2025-03-24T22:02:31.959+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.stytch.com/incident/cm8nlx1q300faaygk50zy8eil"/>
  <title>Increase in 4xx errors in Device Fingerprinting</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 minutes</p>
    <p><strong>Affected Components:</strong> Device Fingerprinting</p>
    <p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>22:02:31</var> GMT+0</small><br /><strong>Identified</strong> -
  Issue has been identified and we&#039;re rolling out a fix..</p>
<p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>22:04:46</var> GMT+0</small><br /><strong>Resolved</strong> -
  Fix has landed and Device Fingerprinting traffic is once again successful..</p>
<p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>21:56:43</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.stytch.com,2005:Maintenance/clms17owm34372bnodonp8z8a3</id>
  <published>2023-09-20T18:00:00.000+00:00</published>
  <updated>2023-09-20T19:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.stytch.com/maintenance/clms17owm34372bnodonp8z8a3"/>
  <title>Scheduled maintenance in our Test environment</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> Test API</p>
    <p><small>Sep <var data-var='date'> 20</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Sep <var data-var='date'> 20</var>, <var data-var='time'>18:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Sep <var data-var='date'> 20</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are performing routine database maintenance and our Test environment may experience some brief instability..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.stytch.com,2005:Maintenance/clmkswt8n162658bnonbb03fc9y</id>
  <published>2023-09-20T17:00:00.000+00:00</published>
  <updated>2023-09-20T17:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.stytch.com/maintenance/clmkswt8n162658bnonbb03fc9y"/>
  <title> Scheduled maintenance in our Test environment</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> Test API</p>
    <p><small>Sep <var data-var='date'> 20</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are planning for some scheduled maintenance in our Test environment. There may be increased 500&#039;s in our Test API during this time, there will be no impact to our Live environment..</p>
<p><small>Sep <var data-var='date'> 20</var>, <var data-var='time'>17:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Sep <var data-var='date'> 20</var>, <var data-var='time'>17:05:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>

        ]]>
  </content>
</entry>

</feed>