Stytch

OPERATIONAL

Since Oct 2025 · 25 incidents · status.stytch.com · checked just now

Compare Add to stack Status page

GradeDLast 90 days

CPRODA+SHIP

Overview

30d 90d 1y

Admitted uptime

Time not covered by a widespread Sev 1 the provider posted itself. A best case.

99.836%Grade D

Incidents

Everything posted on the status page except scheduled maintenance.

71 Sev 1

Sev 1 downtime

Total minutes of Sev 1 incidents, as posted.

3h 33m

Median fix

Median time to resolve. Half of incidents were fixed faster.

57m

Longest

Longest Sev 1–2 incident, start to resolved.

3h 33m

Since last

Time since the last counted incident was resolved.

23h 22m

By area

CProduction

6INCIDENTS

9h 31mAFFECTED

Your users are hit: apps, APIs, databases, inference

Worst, 90d

SEV 1 · SECURITYAug 17, 2026 · 3h 33mEmails not being delivered

SEV 2Oct 22, 2026 · 2h 29m · some customersMissing or delayed SMS OTPs

SEV 2Sep 9, 2026 · 2h 30m · regionalInvestigating SMS deliverability issues to AT&T Wireless

Most hit

Message deliverability4

Live API2

Javascript SDK1

Test API1

Better. 9 in the last 6 months, 10 in the 6 before.

A+Shipping

2INCIDENTS

32mAFFECTED

You can't deploy, build or manage: CI, CLI, dashboard, auth, billing

Worst, 90d

SEV 4Aug 28, 2026 · 31mDelayed Event Log Streams

SEV 3Jul 27, 2026 · 1mIncrease in 500 errors

Most hit

Dashboard1

Javascript SDK1

Test API1

Live API1

Better. 2 in the last 6 months, 3 in the 6 before.

CleanSev 3–4Sev 1–2No data

Trend, last 12 months

Worse. 11 in the last 6 months, 10 in the 6 before.

Severity mix

Sev 1 · Lights outProd site, API or database down, or data loss1

Sev 2 · BleedingProd degraded or partly down5

Sev 3 · Can't shipCan't deploy, build or manage it0

Sev 4 · PapercutDocs, status page, slow dashboard1

1 security incident

When it breaks

Start times, last 12 months, UTC.

Mon

Tue

Wed

Thu

Fri

Sat

Sun

0006121823

What breaks

Message deliverability9 incidents

Live API7 incidents

Dashboard4 incidents

Test API4 incidents

Javascript SDK3 incidents

Device Fingerprinting3 incidents

Communication

Updates each

Status page updates per incident, on average.

3.1Last 12 months

Update gap

Median time between status page updates during an incident.

35mLast 12 months

Postmortems

Sev 1–2 incidents with a published write-up.

3 of 19Sev 1–2

Incident history

Show all 25

Oct 22, 20262h 29mSEV 2

Missing or delayed SMS OTPsSMS OTP delivery to VOIP phone numbers was missing or delayed for about 2.5 hours until failover to a secondary provider.AI-graded · some customers · Message deliverability

Why this grade

RULES · SEV 1
Sev 1 because Message deliverability had a partial outage
CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
SMS OTP delivery to VOIP phone numbers was missing or delayed for about 2.5 hours until failover to a secondary provider.
Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record

3 updates

16:00 UTC · investigating
We are investigating missing or delayed SMS OTPs from our primary messaging provider to VOIP phone numbers.
18:15 UTC · monitoring
We've failed over to our secondary messaging provider and are monitoring deliverability rates.
18:29 UTC · resolved
This incident has been resolved.

Source

Oct 6, 20261mSEV 2

Increase in 500 errorsLive API returned elevated 500 errors for about one minute; extent across customers was not stated.AI-graded · Live API

Why this grade

RULES · SEV 2
Sev 2 because Live API had degraded performance
CLAUDE · SEV 2 · UNCLEAR · LOW CONFIDENCE
Live API returned elevated 500 errors for about one minute; extent across customers was not stated.
Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record

2 updates

16:48 UTC · investigating
We're investigating an increase in 500 errors in our Live API.
16:49 UTC · resolved
This incident has been resolved.

Source

Sep 9, 20262h 30mSEV 2

Investigating SMS deliverability issues to AT&T WirelessSMS delivery to AT&T numbers failed for about two and a half hours; other carriers were not reported affected.AI-graded · regional · Message deliverability

Why this grade

RULES · SEV 2
Sev 2 because Message deliverability had degraded performance
CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
SMS delivery to AT&T numbers failed for about two and a half hours; other carriers were not reported affected.
Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record

3 updates

14:30 UTC · investigating
We're currently investigating SMS deliverability issues to AT&T Wireless.
16:43 UTC · monitoring
We've switched to an alternative messaging provider and are monitoring the result.
17:00 UTC · resolved
SMS are being sent successfully to AT&T numbers.

Source

Sep 1, 202657mSEV 2

Small percentage of SMS requests resulting in 500 errorsA small percentage of SMS API requests returned 500 errors for about an hour due to an upstream messaging issue.AI-graded · some customers · Message deliverability

Why this grade

RULES · SEV 2
Sev 2 because Message deliverability had degraded performance
CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
A small percentage of SMS API requests returned 500 errors for about an hour due to an upstream messaging issue.
Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record

2 updates

16:30 UTC · investigating
A small percentage of SMS requests are currently resulting in 500 / internal\_server\_errors due to an upstream messaging issue.
17:27 UTC · resolved
This issue has been resolved.

Source

Aug 28, 202631mSEV 4

Delayed Event Log StreamsEvent Log Streaming delivered logs late for about 30 minutes; the text does not say how many customers were hit.AI-graded · Dashboard

Why this grade

RULES · SEV 4
Sev 4 because Dashboard had degraded performance
CLAUDE · SEV 4 · UNCLEAR · MEDIUM CONFIDENCE
Event Log Streaming delivered logs late for about 30 minutes; the text does not say how many customers were hit.
Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record

2 updates

22:29 UTC · investigating
We are currently investigating delayed logs in our Event Log Streaming feature.
23:00 UTC · resolved
This incident has been resolved. Delayed logs are now delivered.

Source

Aug 17, 20263h 33mSEV 1 · SECURITY

Emails not being deliveredFree-tier spam abuse exhausted the primary email provider quota, and failover to the secondary provider accepted sends that were never delivered. All email from 02:15 to 05:15 PT failed. Malicious accounts were banned and safeguards added. Some deliverability issues may linger as sender reputation recovers.AI-graded · Message deliverability

Why this grade

RULES · SEV 1
Sev 2 because Message deliverability had degraded performance, raised to Sev 1 for security
CLAUDE · SEV 1 · GLOBAL · MEDIUM CONFIDENCE · SECURITY
All outbound email failed for about three hours, including magic links and OTPs; sender reputation hit lingered afterward.
Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record

4 updates

09:27 UTC · investigating
We are currently investigating this incident.
12:14 UTC · monitoring
We've mitigated the issue and emails are now being delivered. Currently monitoring.
13:00 UTC · resolved
The incident should be resolved; we have put in mitigations and will continue to monitor. A small percentage of users may see some lingering deliverability issues as we catch up. We apologize for the inconvenience.
00:00 UTC · postmortem
We extend our sincerest apologies for this outage. On 17 August 2026, between 02:15 and 05:15 PT (09:15–12:15 UTC), all outbound email from Stytch failed, including email magic links, email OTPs, and password reset emails. Service was restored at 05:15 PT. **What happened**: This outage was triggered by abuse of free-tier email sending, a pattern we defend against continuously. In this case, our abuse controls did not engage in time, and a large volume of spam was sent before we intervened. That volume exhausted our sending quota with our primary email provider, which normally handles the majority of traffic. Automated failover and alerting fired, and our on-call engineer fully failed over to our secondary email provider within 20 minutes. That failover appeared to succeed: The secondary provider accepted our sends and reported them as successful 200s. However, the secondary provider was not delivering those emails due to the previous spam volume. As a result, we believed email had been restored when it had not. We received customer reports beginning at 03:15 PT and confirmed the true state of email sends at 05:01 PT. We restored service at 05:15 PT, banned the malicious accounts, and implemented new safeguards against the abuse seen. **Impact**: All email sent during the window failed permanently. Any authentication email a user requested between 02:15 and 05:15 PT never arrived, and users would need to request a new one after 05:15 PT. **Ongoing impact on deliverability**: The spam volume sent from our infrastructure has affected our sender reputation for `[email protected]`. For some time, a higher-than-normal share of legitimate emails may land in recipients' spam folders. We are working with our providers on reputation remediation and expect this to improve over the coming days. No action is required. If your users report missing authentication emails, please ask them to check their spam folder. **What we're changing**: We have already implemented new safeguards against the abuse seen. To prevent future attacks, we are also reviewing our systems and processes, including: * Rate limits and quotas * Verification of failover paths * Abuse detection at signup and message send time

Postmortem Source

Jul 27, 20261mSEV 2

Increase in 500 errorsLive API returned elevated 500 errors for about 1.5 minutes after a database update; the text does not name regions.AI-graded · Javascript SDK +2

Why this grade

RULES · SEV 2
Sev 2 because Javascript SDK had degraded performance
CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
Live API returned elevated 500 errors for about 1.5 minutes after a database update; the text does not name regions.
Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record

3 updates

00:35 UTC · investigating
We are currently investigating this incident.
00:36 UTC · resolved
This incident has been resolved.
01:11 UTC · postmortem
An update to our DB caused around 1.5 minutes of increased 500's in our API. Apologies for the interruption.

Postmortem Source

Jul 24, 202615mSEV 2

Increase in 5XX errorsLive API requests timed out or returned 5XX errors for about 15 minutes due to a network degradation in one hosting region.AI-graded · regional · Live API

Why this grade

RULES · SEV 2
Sev 2 because Live API had degraded performance
CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
Live API requests timed out or returned 5XX errors for about 15 minutes due to a network degradation in one hosting region.
Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record

3 updates

10:56 UTC · investigating
We are investigating an increase in 5XX errors in the Stytch API.
11:11 UTC · resolved
This incident has been resolved.
17:00 UTC · postmortem
A network connectivity degradation in one of the regions where our infrastructure is hosted disrupted traffic, resulting in some timeouts. Steps will be taken to mitigate this in the future.

Postmortem Source

Jun 15, 202616h 46mSEV 2

Issue causing invalid_email errors for some valid B2B email addressesSev 2 because Message deliverability had degraded performanceMessage deliverability

2 updates

22:07 UTC · investigating
We've identified an issue causing invalid\_email errors for some B2B users with valid email addresses.
14:53 UTC · resolved
This issue has been resolved.

Source

Jun 2, 20261h 00mSEV 2

SMS delivery is currently experiencing some delays.Sev 2 because Message deliverability had degraded performanceMessage deliverability

3 updates

18:00 UTC · investigating
We are actively investigating SMS delivery delays with our primary messaging provider.
18:41 UTC · 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.
19:00 UTC · resolved
This incident has been resolved.

Source

May 29, 20264h 30mSEV 4

Errors with custom auth domain creationSev 4 because Dashboard had degraded performanceDashboard

2 updates

18:12 UTC · 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.
22:41 UTC · resolved
This incident has been resolved.

Source

Apr 6, 20262h 07mSEV 2

Issues with Email Risk APISev 2 because Device Fingerprinting had degraded performanceDevice Fingerprinting

3 updates

14:52 UTC · investigating
We are currently investigating elevated 500 errors in the email risk API.
16:45 UTC · monitoring
A fix has been implemented and we are currently monitoring the result.
17:00 UTC · resolved
This incident has been resolved.

Source

Jan 28, 202632mSEV 2

Internal Logging DisruptionSev 2 from the incident title (no components listed)

2 updates

20:23 UTC · 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.
20:55 UTC · resolved
This incident has been resolved.

Source

Jan 27, 20260mSEV 2

Outlook incident - emails not getting deliveredSev 2 from the incident title (no components listed)

1 update

13:00 UTC · 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/)

Source

Jan 24, 202614h 29mSEV 2

Gmail incident - delayed emailsSev 2 because Message deliverability had degraded performanceMessage deliverability

4 updates

13:02 UTC · investigating
Gmail is currently experiencing an incident that is causing delayed emails for end users. You can follow along with their incident here: <https://www.google.com/appsstatus/dashboard/incidents/NNnDkY9CJ36annsfytjQ> We'll be monitoring and will resolve this incident when we've confirmed delivery returns to normal for Gmail users.
17:22 UTC · monitoring
Continuing to monitor.
21:12 UTC · monitoring
Reports of delivery issues has dropped but is still not back to normal. We're continuing to monitor.
03:30 UTC · resolved
This incident has been resolved.

Source

Dec 22, 202536mSEV 2

Increased 4XX and 5XX errors with Connected AppsSev 2 because Device Fingerprinting had degraded performanceDevice Fingerprinting +5

3 updates

21:59 UTC · identified
We have identified an issue with Connected Apps caused by a recent change and are currently implementing a fix.
22:30 UTC · monitoring
We implemented a fix and are currently monitoring the result.
22:35 UTC · resolved
This incident has been resolved.

Source

Dec 19, 202522mSEV 2

Elevated error rates for SAML SSO flowSev 2 because Live API had degraded performanceTest API +1

3 updates

16:30 UTC · investigating
We are actively investigating an elevated rate of SAML SSO errors.
16:51 UTC · monitoring
We implemented a fix and are currently monitoring the result.
16:52 UTC · resolved
This incident has been resolved. SAML SSO traffic is healthy.

Source

Nov 18, 202540mSEV 2

Elevated error rate in APISev 2 because Live API had degraded performanceTest API +2

3 updates

11:30 UTC · investigating
We are currently investigating an increase in errors in the Stytch API due to impact from an upstream provider outage.
12:01 UTC · 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.
12:10 UTC · resolved
During [Cloudflare's 2025-11-18 incident](https://blog.cloudflare.com/18-november-2025-outage/), Stytch's services continued to operate as normal. However Stytch customers that use Cloudflare in their own infrastructure may have seen their requests to Stytch, either client or server side requests, fail to make it to the Stytch API, thus causing their auth flows to fail. Though the Cloudflare incident did not cause any downtime in Stytch services, due to the popularity of Cloudflare, we've created this incident for posterity for customers investigating downtime in their own systems.

Source

Nov 18, 202540mSEV 2

Inability to load frontend script from Cloudflare custom domainSev 2 because Device Fingerprinting had degraded performanceDevice Fingerprinting

2 updates

11:30 UTC · investigating
We are currently investigating this incident.
12:10 UTC · 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.

Source

Nov 13, 202514mSEV 2

Increased latency in the live APISev 2 because Live API had degraded performanceLive API

3 updates

14:06 UTC · investigating
We are currently investigating issues with increased latency in the live API.
14:17 UTC · monitoring
We implemented a fix and are currently monitoring the result.
14:20 UTC · resolved
This incident has been resolved.

Source