<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Stytch Status - Incident history</title>
    <link>https://status.stytch.com</link>
    <description>Stytch</description>
    <pubDate>Wed, 28 Jan 2026 20:23:00 +0000</pubDate>
    
<item>
  <title>Internal Logging Disruption</title>
  <description>
    Type: Incident
    Duration: 4 hours and 51 minutes

    
    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. Jan 28, 20:55:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 51 minutes</p>
    
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:23:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:55:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 28 Jan 2026 20:23:00 +0000</pubDate>
  <link>https://status.stytch.com/incident/cmkyikbok054dah4dhiwrbqid</link>
  <guid>https://status.stytch.com/incident/cmkyikbok054dah4dhiwrbqid</guid>
</item>

<item>
  <title>Outlook incident - emails not getting delivered</title>
  <description>
    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&#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/) 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  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/).&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 27 Jan 2026 13:00:00 +0000</pubDate>
  <link>https://status.stytch.com/incident/cmkwydalq0033ff6nvlej3xjw</link>
  <guid>https://status.stytch.com/incident/cmkwydalq0033ff6nvlej3xjw</guid>
</item>

<item>
  <title>Gmail incident - delayed emails</title>
  <description>
    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, 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: &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. Jan 24, 17:22:06 GMT+0 - Monitoring - Continuing to monitor. Jan 24, 21:12:10 GMT+0 - Monitoring - Reports of delivery issues has dropped but is still not back to normal.

We&#039;re continuing to monitor. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 14 hours and 29 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;03:30:57&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:02:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:22:06&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Continuing to monitor..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:12:10&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Reports of delivery issues has dropped but is still not back to normal.

We&#039;re continuing to monitor..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 24 Jan 2026 13:02:00 +0000</pubDate>
  <link>https://status.stytch.com/incident/cmksksz0j0jkj8iu99xldo8fy</link>
  <guid>https://status.stytch.com/incident/cmksksz0j0jkj8iu99xldo8fy</guid>
</item>

<item>
  <title>Increased 4XX and 5XX errors with Connected Apps</title>
  <description>
    Type: Incident
    Duration: 36 minutes

    Affected Components: Device Fingerprinting, Test API, Live API, Dashboard, Javascript SDK, Message deliverability
    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. Dec 22, 22:35:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 36 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , </p>
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the result..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:59:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have identified an issue with Connected Apps caused by a recent change and are currently implementing a fix..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:35:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 22 Dec 2025 21:59:00 +0000</pubDate>
  <link>https://status.stytch.com/incident/cmjhptdsw08jo14bla3r0ftv0</link>
  <guid>https://status.stytch.com/incident/cmjhptdsw08jo14bla3r0ftv0</guid>
</item>

<item>
  <title>Elevated error rates for SAML SSO flow </title>
  <description>
    Type: Incident
    Duration: 9 minutes

    Affected Components: Test API, Live API
    Dec 19, 16:30:00 GMT+0 - Investigating - We are actively investigating an elevated rate of SAML SSO errors. Dec 19, 16:51:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Dec 19, 16:52:00 GMT+0 - Resolved - This incident has been resolved. SAML SSO traffic is healthy. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 9 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are actively investigating an elevated rate of SAML SSO errors..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:51:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the result..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:52:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved. SAML SSO traffic is healthy..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 19 Dec 2025 16:30:00 +0000</pubDate>
  <link>https://status.stytch.com/incident/cmjd3r38v04jk9pamutqhsi6d</link>
  <guid>https://status.stytch.com/incident/cmjd3r38v04jk9pamutqhsi6d</guid>
</item>

<item>
  <title>Elevated error rate in API</title>
  <description>
    Type: Incident
    

    Affected Components: Test API, Live API, Javascript SDK
    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. 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, 12:10:00 GMT+0 - Resolved - 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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating an increase in errors in the Stytch API due to impact from an upstream provider outage..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:01:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:10:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  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..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 18 Nov 2025 11:30:00 +0000</pubDate>
  <link>https://status.stytch.com/incident/cmi4jnk9j0003hilezbsh2r0k</link>
  <guid>https://status.stytch.com/incident/cmi4jnk9j0003hilezbsh2r0k</guid>
</item>

<item>
  <title>Inability to load frontend script from Cloudflare custom domain</title>
  <description>
    Type: Incident
    Duration: 1 hour and 40 minutes

    Affected Components: Device Fingerprinting
    Nov 18, 11:30:00 GMT+0 - Investigating - We are currently investigating this incident. Nov 18, 12:10:00 GMT+0 - Resolved - 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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 40 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:10:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  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..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 18 Nov 2025 11:30:00 +0000</pubDate>
  <link>https://status.stytch.com/incident/cmi6np63m00t0ekn395p7bgpy</link>
  <guid>https://status.stytch.com/incident/cmi6np63m00t0ekn395p7bgpy</guid>
</item>

<item>
  <title>Increased latency in the live API</title>
  <description>
    Type: Incident
    Duration: 34 minutes

    Affected Components: Live API
    Nov 13, 14:06:00 GMT+0 - Investigating - We are currently investigating issues with increased latency in the live API. Nov 13, 14:17:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Nov 13, 14:20:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 34 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:06:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating issues with increased latency in the live API..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:17:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the result..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:20:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 13 Nov 2025 14:06:00 +0000</pubDate>
  <link>https://status.stytch.com/incident/cmhximlrs03jwhqpozv9o1sgu</link>
  <guid>https://status.stytch.com/incident/cmhximlrs03jwhqpozv9o1sgu</guid>
</item>

<item>
  <title>Device Fingerprinting pages unavailable in the Dashboard</title>
  <description>
    Type: Incident
    Duration: 47 minutes

    Affected Components: Dashboard, Message deliverability
    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. Nov 10, 20:16:30 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 47 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:20:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:16:30&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 10 Nov 2025 17:20:00 +0000</pubDate>
  <link>https://status.stytch.com/incident/cmhtl0iz3013i119rtwr51pzr</link>
  <guid>https://status.stytch.com/incident/cmhtl0iz3013i119rtwr51pzr</guid>
</item>

<item>
  <title>Elevated SMS OTP errors/ delays</title>
  <description>
    Type: Incident
    Duration: 3 hours and 39 minutes

    Affected Components: Message deliverability
    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&#039;re assessing whether it makes sense to switch to a backup provider. 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, 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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 39 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:57:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:38:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The SMS OTP errors have subsided. We will continue to monitor the situation while our primary messaging provider investigates the incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:40:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  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..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 20 Oct 2025 16:57:00 +0000</pubDate>
  <link>https://status.stytch.com/incident/cmgzdh3ty05sszejad6bwsml3</link>
  <guid>https://status.stytch.com/incident/cmgzdh3ty05sszejad6bwsml3</guid>
</item>

<item>
  <title>SAML SSO requests failing</title>
  <description>
    Type: Incident
    Duration: 1 hour and 12 minutes

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

<item>
  <title>Elevated BLOCK rates</title>
  <description>
    Type: Incident
    Duration: 23 minutes

    Affected Components: Device Fingerprinting
    Oct 20, 15:57:01 GMT+0 - Investigating - We are currently investigating elevated DFP BLOCK rates. Oct 20, 16:19:56 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 23 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:57:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating elevated DFP BLOCK rates..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:19:56&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 20 Oct 2025 15:57:01 +0000</pubDate>
  <link>https://status.stytch.com/incident/cmgzbjcbr03huvl2l9w8k0f2z</link>
  <guid>https://status.stytch.com/incident/cmgzbjcbr03huvl2l9w8k0f2z</guid>
</item>

<item>
  <title>Investigating report of email deliverability issues</title>
  <description>
    Type: Incident
    Duration: 1 day

    Affected Components: Message deliverability
    Oct 9, 00:10:04 GMT+0 - Investigating - We&#039;ve received several reports of potential issues with delivery login emails to Yahoo Email inboxes. Oct 10, 00:10:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:10:04&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We&#039;ve received several reports of potential issues with delivery login emails to Yahoo Email inboxes..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:10:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 9 Oct 2025 00:10:04 +0000</pubDate>
  <link>https://status.stytch.com/incident/cmginv6no00yysf24z9d323ze</link>
  <guid>https://status.stytch.com/incident/cmginv6no00yysf24z9d323ze</guid>
</item>

<item>
  <title>The Stytch API is currently experiencing issues.</title>
  <description>
    Type: Incident
    Duration: 1 minute

    Affected Components: Live API
    Oct 7, 18:27:00 GMT+0 - Investigating - We are investigating elevated API latencies. Oct 7, 18:28:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 minute</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:27:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are investigating elevated API latencies..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:28:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 7 Oct 2025 18:27:00 +0000</pubDate>
  <link>https://status.stytch.com/incident/cmggz0uhc0360kdz6yhf3bw8m</link>
  <guid>https://status.stytch.com/incident/cmggz0uhc0360kdz6yhf3bw8m</guid>
</item>

<item>
  <title>Increased errors in device fingerprinting</title>
  <description>
    Type: Incident
    Duration: 2 minutes

    Affected Components: Device Fingerprinting
    Oct 7, 17:39:00 GMT+0 - Investigating - We are investigating an increase in errors in the device fingerprinting product. Oct 7, 17:41:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:39:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are investigating an increase in errors in the device fingerprinting product..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:41:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 7 Oct 2025 17:39:00 +0000</pubDate>
  <link>https://status.stytch.com/incident/cmggwmvvh01nybxnszgbyszvz</link>
  <guid>https://status.stytch.com/incident/cmggwmvvh01nybxnszgbyszvz</guid>
</item>

<item>
  <title>Increase in 500 errors</title>
  <description>
    Type: Incident
    Duration: 1 hour and 15 minutes

    Affected Components: Test API
    Aug 21, 01:39:00 GMT+0 - Resolved - Fix has landed and 500&#039;s have resolved. Aug 20, 22:40:00 GMT+0 - Investigating - We&#039;ve received reports of 500 errors on Magic Link email sends. We are currently investigating this incident. Aug 21, 01:45:00 GMT+0 - Postmortem - 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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 15 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:39:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Fix has landed and 500&#039;s have resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:40:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We&#039;ve received reports of 500 errors on Magic Link email sends. We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:45:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Postmortem&lt;/strong&gt; -
  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..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 20 Aug 2025 22:40:00 +0000</pubDate>
  <link>https://status.stytch.com/incident/cmekljo5h00c2rjh1tozl9dlb</link>
  <guid>https://status.stytch.com/incident/cmekljo5h00c2rjh1tozl9dlb</guid>
</item>

<item>
  <title>Google incident causing increased errors for Google OAuth</title>
  <description>
    Type: Incident
    Duration: 1 hour and 1 minute

    Affected Components: Live API
    Jul 18, 16:36:26 GMT+0 - Resolved - Google has marked their incident as resolved. Jul 18, 15:35:00 GMT+0 - Monitoring - 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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 1 minute</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:36:26&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Google has marked their incident as resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:35:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  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..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 18 Jul 2025 15:35:00 +0000</pubDate>
  <link>https://status.stytch.com/incident/cmd90mg9r00bp9sbtdt8xwjpj</link>
  <guid>https://status.stytch.com/incident/cmd90mg9r00bp9sbtdt8xwjpj</guid>
</item>

<item>
  <title>Event log streaming delayed</title>
  <description>
    Type: Incident
    Duration: 5 hours and 29 minutes

    Affected Components: Live API, Test API
    Jul 17, 14:49:09 GMT+0 - Resolved - This incident has been resolved. Event logs should be streaming normally. Jul 17, 14:27:00 GMT+0 - Monitoring - We have identified the root cause and are implementing a fix. Jul 17, 09:20:00 GMT+0 - Identified - We are investigating reports of event log streams being delayed. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours and 29 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:49:09&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved. Event logs should be streaming normally..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:27:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We have identified the root cause and are implementing a fix..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:20:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are investigating reports of event log streams being delayed..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 17 Jul 2025 09:20:00 +0000</pubDate>
  <link>https://status.stytch.com/incident/cmd7htqvd0002e01fwins3nep</link>
  <guid>https://status.stytch.com/incident/cmd7htqvd0002e01fwins3nep</guid>
</item>

<item>
  <title>Bounce rate for email sending is high</title>
  <description>
    Type: Incident
    Duration: 2 hours and 34 minutes

    Affected Components: Message deliverability
    Jul 6, 17:11:55 GMT+0 - Investigating - We are currently investigating this incident. Jul 6, 17:27:59 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jul 6, 19:45:43 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 34 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:11:55&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:27:59&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the result..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:45:43&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 6 Jul 2025 17:11:55 +0000</pubDate>
  <link>https://status.stytch.com/incident/cmcrxjdo400csi9i5imtihaqw</link>
  <guid>https://status.stytch.com/incident/cmcrxjdo400csi9i5imtihaqw</guid>
</item>

<item>
  <title>Spike in 5XX errors</title>
  <description>
    Type: Incident
    

    Affected Components: Live API
    Jun 5, 05:34:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:34:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 5 Jun 2025 05:34:00 +0000</pubDate>
  <link>https://status.stytch.com/incident/cmbiy6qyn001d1pj9foxal57o</link>
  <guid>https://status.stytch.com/incident/cmbiy6qyn001d1pj9foxal57o</guid>
</item>

<item>
  <title>Some Dashboard pages inaccessible </title>
  <description>
    Type: Incident
    Duration: 1 hour and 30 minutes

    Affected Components: Dashboard
    May 27, 14:08:57 GMT+0 - Identified - 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. May 27, 14:50:40 GMT+0 - Monitoring - The vendor fixed the issue. You may still see issues as the cache is cleared. We are monitoring to verify the fix May 27, 15:39:11 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 30 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:08:57&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:50:40&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The vendor fixed the issue. You may still see issues as the cache is cleared. We are monitoring to verify the fix.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:39:11&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 27 May 2025 14:08:57 +0000</pubDate>
  <link>https://status.stytch.com/incident/cmb6ldzwe000h39arkjr9n4ft</link>
  <guid>https://status.stytch.com/incident/cmb6ldzwe000h39arkjr9n4ft</guid>
</item>

<item>
  <title>Increase in inappropriate 429 errors for SMS Sends in Consumer</title>
  <description>
    Type: Incident
    Duration: 1 hour and 11 minutes

    Affected Components: Message deliverability
    May 21, 18:45:00 GMT+0 - 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. May 21, 19:56:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 11 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:45:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:56:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 21 May 2025 18:45:00 +0000</pubDate>
  <link>https://status.stytch.com/incident/cmaydf09v0049q1m9bk1uxef7</link>
  <guid>https://status.stytch.com/incident/cmaydf09v0049q1m9bk1uxef7</guid>
</item>

<item>
  <title>Delayed SMS - AT&amp;T</title>
  <description>
    Type: Incident
    Duration: 8 hours and 39 minutes

    Affected Components: Message deliverability
    May 1, 16:26:33 GMT+0 - Investigating - We are seeing delays in some SMS messages sent on AT&amp;T across multiple messaging providers.  May 1, 19:46:00 GMT+0 - Monitoring - We are seeing a recovery in SMS delivery delays and are continuing to monitor.  May 2, 01:05:10 GMT+0 - Resolved - We have confirmed that traffic has returned to normal. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 hours and 39 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:26:33&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are seeing delays in some SMS messages sent on AT&amp;T across multiple messaging providers. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:46:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We are seeing a recovery in SMS delivery delays and are continuing to monitor. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:05:10&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We have confirmed that traffic has returned to normal..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 1 May 2025 16:26:33 +0000</pubDate>
  <link>https://status.stytch.com/incident/cma5kut9z001ooh5pte0te7fa</link>
  <guid>https://status.stytch.com/incident/cma5kut9z001ooh5pte0te7fa</guid>
</item>

<item>
  <title>Increased in errors in device fingerprinting</title>
  <description>
    Type: Incident
    Duration: 1 hour and 19 minutes

    Affected Components: Device Fingerprinting
    Apr 9, 22:42:00 GMT+0 - Investigating - We are currently investigating this incident. Apr 9, 23:22:00 GMT+0 - Resolved - We implemented a fix and are currently monitoring the result. Affected users may need to clear their cache to fully resolve the issue. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 19 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:42:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:22:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the result. Affected users may need to clear their cache to fully resolve the issue..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 9 Apr 2025 22:42:00 +0000</pubDate>
  <link>https://status.stytch.com/incident/cm9al7g6i003tgg2xs7ag97fh</link>
  <guid>https://status.stytch.com/incident/cm9al7g6i003tgg2xs7ag97fh</guid>
</item>

<item>
  <title>Increase in 4xx errors in Device Fingerprinting</title>
  <description>
    Type: Incident
    Duration: 8 minutes

    Affected Components: Device Fingerprinting
    Mar 24, 22:02:31 GMT+0 - Identified - Issue has been identified and we&#039;re rolling out a fix. Mar 24, 22:04:46 GMT+0 - Resolved - Fix has landed and Device Fingerprinting traffic is once again successful. Mar 24, 21:56:43 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:02:31&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Issue has been identified and we&#039;re rolling out a fix..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:04:46&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Fix has landed and Device Fingerprinting traffic is once again successful..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:56:43&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 24 Mar 2025 21:56:43 +0000</pubDate>
  <link>https://status.stytch.com/incident/cm8nlx1q300faaygk50zy8eil</link>
  <guid>https://status.stytch.com/incident/cm8nlx1q300faaygk50zy8eil</guid>
</item>

<item>
  <title>Scheduled maintenance in our Test environment</title>
  <description>
    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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are performing routine database maintenance and our Test environment may experience some brief instability..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 20 Sep 2023 18:00:00 +0000</pubDate>
  <link>https://status.stytch.com/maintenance/clms17owm34372bnodonp8z8a3</link>
  <guid>https://status.stytch.com/maintenance/clms17owm34372bnodonp8z8a3</guid>
</item>

<item>
  <title> Scheduled maintenance in our Test environment</title>
  <description>
    Type: Maintenance
    Duration: 5 minutes

    Affected Components: Test API
    Sep 20, 17:00:00 GMT+0 - Identified - 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. Sep 20, 17:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 20, 17:05:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:05:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 20 Sep 2023 17:00:00 +0000</pubDate>
  <link>https://status.stytch.com/maintenance/clmkswt8n162658bnonbb03fc9y</link>
  <guid>https://status.stytch.com/maintenance/clmkswt8n162658bnonbb03fc9y</guid>
</item>

  </channel>
  </rss>