Stytch had 23 outages in the last 2 years totaling 16h 46m of downtime — averaging 0.9 incidents per month.
There were 23 Stytch outages since July 6, 2025 totaling 16h 46m of downtime. Each is summarised below — incident details, duration, and resolution information.
We've identified an issue causing invalid\_email errors for some B2B users with valid email addresses.
This issue has been resolved.
Type: Incident Duration: 1 hour and 2 minutes Affected Components: Message deliverability Jun 2, 18:41:00 GMT+0 - Monitoring - We have failed over to our secondary messaging provider and are monitoring the status. You may see fewer SMSDelivery event logs than expected during this time. Jun 2, 18:00:00 GMT+0 - Investigating - We are actively investigating SMS delivery delays with our primary messaging provider. Jun 2, 19:00:00 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 4 hours and 30 minutes Affected Components: Dashboard May 29, 18:12:00 GMT+0 - Identified - We have identified the root cause and are currently implementing a fix for errors with custom auth domain creation. Existing custom domains are not impacted. May 29, 22:41:34 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 1 hour and 52 minutes Affected Components: Javascript SDK, Device Fingerprinting, Test API, Live API, Dashboard, Message deliverability Apr 6, 14:52:56 GMT+0 - Investigating - We are currently investigating elevated 500 errors in the email risk API. Apr 6, 16:45:00 GMT+0 - Monitoring - A fix has been implemented and we are currently monitoring the result. Apr 6, 17:00:00 GMT+0 - Resolved - This incident has been resolved.
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.
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'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'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/)
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: We'll be monitoring and will resolve this incident when we'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're continuing to monitor.
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.
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.
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's 2025-11-18 incident](https://blog.cloudflare.com/18-november-2025-outage/), 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.
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.
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.
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'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.
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.
Type: Incident Duration: 1 day Affected Components: Message deliverability Oct 9, 00:10:04 GMT+0 - Investigating - We'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.
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.
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.
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's have resolved. Aug 20, 22:40:00 GMT+0 - Investigating - We'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.
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.
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.
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.