Dev APIs / Auth / Stytch

Stytch

OPERATIONAL

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

CompareAdd to stackStatus page
GradeDLast 90 days
CPRODA+SHIP

Overview

30d90d1y
Admitted uptimeTime not covered by a widespread Sev 1 the provider posted itself. A best case.
99.959%Grade D
IncidentsEverything posted on the status page except scheduled maintenance.
201 Sev 1
Sev 1 downtimeTotal minutes of Sev 1 incidents, as posted.
3h 33m
Median fixMedian time to resolve. Half of incidents were fixed faster.
57m
LongestLongest Sev 1–2 incident, start to resolved.
16h 46m
Since lastTime since the last counted incident was resolved.
38h 26m

By area

DProduction
16INCIDENTS
46h 00mAFFECTED
Your users are hit: apps, APIs, databases, inference
Worst, 1y
SEV 1 · SECURITYAug 17, 2026 · 3h 33mEmails not being delivered
SEV 2Jun 15, 2026 · 16h 46m · some customersIssue causing invalid_email errors for some valid B2B email addresses
SEV 2Apr 6, 2026 · 2h 07mIssues with Email Risk API
Most hit
Message deliverability8
Live API6
Test API3
Device Fingerprinting3
Worse. 9 in the last 6 months, 7 in the 6 before.
AShipping
5INCIDENTS
5h 56mAFFECTED
You can't deploy, build or manage: CI, CLI, dashboard, auth, billing
Worst, 1y
SEV 3May 29, 2026 · 4h 30m · some customersErrors with custom auth domain creation
SEV 4Jan 28, 2026 · 32mInternal Logging Disruption
SEV 4Aug 28, 2026 · 31mDelayed Event Log Streams
Most hit
Dashboard2
Test API2
Live API2
Javascript SDK1
Worse. 3 in the last 6 months, 2 in the 6 before.
CleanSev 3–4Sev 1–2No data

Trend, last 12 months

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

Severity mix

Sev 1 · Lights outProd site, API or database down, or data loss1
Sev 2 · BleedingProd degraded or partly down15
Sev 3 · Can't shipCan't deploy, build or manage it1
Sev 4 · PapercutDocs, status page, slow dashboard3
1 security incident

When it breaks

Start times, last 12 months, UTC.

What breaks

Message deliverability9 incidents
Live API7 incidents
Dashboard4 incidents
Test API4 incidents
Javascript SDK3 incidents
Device Fingerprinting3 incidents

Communication

Updates eachStatus page updates per incident, on average.
3.1Last 12 months
Update gapMedian time between status page updates during an incident.
35mLast 12 months
PostmortemsSev 1–2 incidents with a published write-up.
3 of 16Sev 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
  1. RULES · SEV 1
    Sev 1 because Message deliverability had a partial outage
  2. 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.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
3 updates
  1. 16:00 UTC · investigating
    We are investigating missing or delayed SMS OTPs from our primary messaging provider to VOIP phone numbers.
  2. 18:15 UTC · monitoring
    We've failed over to our secondary messaging provider and are monitoring deliverability rates.
  3. 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
  1. RULES · SEV 2
    Sev 2 because Live API had degraded performance
  2. CLAUDE · SEV 2 · UNCLEAR · LOW CONFIDENCE
    Live API returned elevated 500 errors for about one minute; extent across customers was not stated.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
2 updates
  1. 16:48 UTC · investigating
    We're investigating an increase in 500 errors in our Live API.
  2. 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
  1. RULES · SEV 2
    Sev 2 because Message deliverability had degraded performance
  2. 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.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
3 updates
  1. 14:30 UTC · investigating
    We're currently investigating SMS deliverability issues to AT&T Wireless.
  2. 16:43 UTC · monitoring
    We've switched to an alternative messaging provider and are monitoring the result.
  3. 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
  1. RULES · SEV 2
    Sev 2 because Message deliverability had degraded performance
  2. 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.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
2 updates
  1. 16:30 UTC · investigating
    A small percentage of SMS requests are currently resulting in 500 / internal\_server\_errors due to an upstream messaging issue.
  2. 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
  1. RULES · SEV 4
    Sev 4 because Dashboard had degraded performance
  2. 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.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
2 updates
  1. 22:29 UTC · investigating
    We are currently investigating delayed logs in our Event Log Streaming feature.
  2. 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
  1. RULES · SEV 1
    Sev 2 because Message deliverability had degraded performance, raised to Sev 1 for security
  2. 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.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
4 updates
  1. 09:27 UTC · investigating
    We are currently investigating this incident.
  2. 12:14 UTC · monitoring
    We've mitigated the issue and emails are now being delivered. Currently monitoring.
  3. 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.
  4. 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
PostmortemSource
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
  1. RULES · SEV 2
    Sev 2 because Javascript SDK had degraded performance
  2. 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.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
3 updates
  1. 00:35 UTC · investigating
    We are currently investigating this incident.
  2. 00:36 UTC · resolved
    This incident has been resolved.
  3. 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.
PostmortemSource
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
  1. RULES · SEV 2
    Sev 2 because Live API had degraded performance
  2. 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.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
3 updates
  1. 10:56 UTC · investigating
    We are investigating an increase in 5XX errors in the Stytch API.
  2. 11:11 UTC · resolved
    This incident has been resolved.
  3. 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.
PostmortemSource
Jun 15, 202616h 46mSEV 2
Issue causing invalid_email errors for some valid B2B email addressesSome B2B users with valid email addresses received invalid_email errors during authentication for about 17 hours.AI-graded · some customers · Message deliverability
Why this grade
  1. RULES · SEV 2
    Sev 2 because Message deliverability had degraded performance
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Some B2B users with valid email addresses received invalid_email errors during authentication for about 17 hours.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
2 updates
  1. 22:07 UTC · investigating
    We've identified an issue causing invalid\_email errors for some B2B users with valid email addresses.
  2. 14:53 UTC · resolved
    This issue has been resolved.
Source
Jun 2, 20261h 00mSEV 2
SMS delivery is currently experiencing some delays.SMS delivery was delayed for about an hour while the primary messaging provider was degraded; traffic moved to a secondary provider. The text does not say how many customers were hit.AI-graded · Message deliverability
Why this grade
  1. RULES · SEV 2
    Sev 2 because Message deliverability had degraded performance
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    SMS delivery was delayed for about an hour while the primary messaging provider was degraded; traffic moved to a secondary provider. The text does not say how many customers were hit.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
3 updates
  1. 18:00 UTC · investigating
    We are actively investigating SMS delivery delays with our primary messaging provider.
  2. 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.
  3. 19:00 UTC · resolved
    This incident has been resolved.
Source
May 29, 20264h 30mSEV 3
Errors with custom auth domain creationCreating custom auth domains failed in the Stytch dashboard; existing custom domains were not affected.AI-graded · some customers · Dashboard
Why this grade
  1. RULES · SEV 4
    Sev 4 because Dashboard had degraded performance
  2. CLAUDE · SEV 3 · SUBSET · MEDIUM CONFIDENCE
    Creating custom auth domains failed in the Stytch dashboard; existing custom domains were not affected.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
2 updates
  1. 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.
  2. 22:41 UTC · resolved
    This incident has been resolved.
Source
Apr 6, 20262h 07mSEV 2
Issues with Email Risk APIEmail Risk API returned elevated 500 errors for about two hours; the text does not say how many customers were hit.AI-graded · Device Fingerprinting
Why this grade
  1. RULES · SEV 2
    Sev 2 because Device Fingerprinting had degraded performance
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Email Risk API returned elevated 500 errors for about two hours; the text does not say how many customers were hit.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
3 updates
  1. 14:52 UTC · investigating
    We are currently investigating elevated 500 errors in the email risk API.
  2. 16:45 UTC · monitoring
    A fix has been implemented and we are currently monitoring the result.
  3. 17:00 UTC · resolved
    This incident has been resolved.
Source
Jan 28, 202632mSEV 4
Internal Logging DisruptionEvent log streaming and Dashboard internal logging were interrupted for about 32 minutes; the text does not say how many customers were hit.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · UNCLEAR · MEDIUM CONFIDENCE
    Event log streaming and Dashboard internal logging were interrupted for about 32 minutes; the text does not say how many customers were hit.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
2 updates
  1. 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.
  2. 20:55 UTC · resolved
    This incident has been resolved.
Source
Jan 27, 20260mSEV 2
Outlook incident - emails not getting deliveredEmail sent through Stytch to Microsoft Outlook addresses was delayed or blocked for several days due to an upstream Microsoft issue. Stytch reports no downtime in its own services and has no fix; Microsoft has not commented. Affected customers were told to file an OLC support request with Microsoft.AI-graded · some customers
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Emails to Microsoft Outlook mailboxes were deferred or blocked upstream; Stytch says it had no downtime of its own services.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
1 update
  1. 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 emailsEmails sent through Stytch to Gmail users were delayed due to an ongoing Gmail incident. Stytch monitored delivery from January 24 13:02 UTC and resolved the incident at January 25 03:30 UTC. The text gives no Stytch-side cause or fix.AI-graded · regional · Message deliverability
Why this grade
  1. RULES · SEV 2
    Sev 2 because Message deliverability had degraded performance
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Email delivery to Gmail users was delayed for about 14 hours because of a Gmail-side incident; other mailbox providers were not mentioned.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
4 updates
  1. 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.
  2. 17:22 UTC · monitoring
    Continuing to monitor.
  3. 21:12 UTC · monitoring
    Reports of delivery issues has dropped but is still not back to normal. We're continuing to monitor.
  4. 03:30 UTC · resolved
    This incident has been resolved.
Source
Dec 22, 202536mSEV 2
Increased 4XX and 5XX errors with Connected AppsConnected Apps requests returned elevated 4XX and 5XX errors for about 36 minutes after a recent change; the text does not say how many customers were hit.AI-graded · one model or feature · Device Fingerprinting +5
Why this grade
  1. RULES · SEV 2
    Sev 2 because Device Fingerprinting had degraded performance
  2. CLAUDE · SEV 2 · SINGLE · MEDIUM CONFIDENCE
    Connected Apps requests returned elevated 4XX and 5XX errors for about 36 minutes after a recent change; the text does not say how many customers were hit.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
3 updates
  1. 21:59 UTC · identified
    We have identified an issue with Connected Apps caused by a recent change and are currently implementing a fix.
  2. 22:30 UTC · monitoring
    We implemented a fix and are currently monitoring the result.
  3. 22:35 UTC · resolved
    This incident has been resolved.
Source
Dec 19, 202522mSEV 2
Elevated error rates for SAML SSO flowElevated errors in the SAML SSO flow on the Live API for about 22 minutes; other sign-in methods were not described as affected.AI-graded · one model or feature · Test API +1
Why this grade
  1. RULES · SEV 2
    Sev 2 because Live API had degraded performance
  2. CLAUDE · SEV 2 · SINGLE · MEDIUM CONFIDENCE
    Elevated errors in the SAML SSO flow on the Live API for about 22 minutes; other sign-in methods were not described as affected.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
3 updates
  1. 16:30 UTC · investigating
    We are actively investigating an elevated rate of SAML SSO errors.
  2. 16:51 UTC · monitoring
    We implemented a fix and are currently monitoring the result.
  3. 16:52 UTC · resolved
    This incident has been resolved. SAML SSO traffic is healthy.
Source
Nov 18, 202540mNOT COUNTED
Elevated error rate in APIStytch's API showed errors during Cloudflare's November 18, 2025 outage. Stytch says its services ran normally. Customers whose traffic to Stytch went through Cloudflare may have had failed requests and broken auth flows. Resolved after about 40 minutes.AI-graded · Test API +2
Why this grade
  1. RULES · SEV 2
    Sev 2 because Live API had degraded performance
  2. CLAUDE · SEV 0 · UNCLEAR · MEDIUM CONFIDENCE
    Stytch says its own services stayed up; customers routing through Cloudflare saw requests to Stytch fail during the upstream outage.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
3 updates
  1. 11:30 UTC · investigating
    We are currently investigating an increase in errors in the Stytch API due to impact from an upstream provider outage.
  2. 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.
  3. 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 domainDevice Fingerprinting script failed to load for customers using Cloudflare-powered custom domains for about 40 minutes; other customers were unaffected.AI-graded · some customers · Device Fingerprinting
Why this grade
  1. RULES · SEV 2
    Sev 2 because Device Fingerprinting had degraded performance
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Device Fingerprinting script failed to load for customers using Cloudflare-powered custom domains for about 40 minutes; other customers were unaffected.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
2 updates
  1. 11:30 UTC · investigating
    We are currently investigating this incident.
  2. 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 APILive API latency rose for about 14 minutes before a fix was applied; the update does not say how many customers were affected.AI-graded · Live API
Why this grade
  1. RULES · SEV 2
    Sev 2 because Live API had degraded performance
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Live API latency rose for about 14 minutes before a fix was applied; the update does not say how many customers were affected.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
3 updates
  1. 14:06 UTC · investigating
    We are currently investigating issues with increased latency in the live API.
  2. 14:17 UTC · monitoring
    We implemented a fix and are currently monitoring the result.
  3. 14:20 UTC · resolved
    This incident has been resolved.
Source

Peers, 90 days

Compare
MailerSendGrade A+100.00% up0 incidentsMTTR –LoopsGrade A+100.00% up1 incidentMTTR 1h 34mKindeGrade A+100.00% up2 incidentsMTTR 1h 12mPaddleGrade A100.00% up3 incidentsMTTR 47mResendGrade B100.00% up25 incidentsMTTR 24mInngestGrade B100.00% up14 incidentsMTTR 43mMapboxGrade C100.00% up2 incidentsMTTR 12h 38mAblyGrade C99.98% up7 incidentsMTTR 7mMailgunGrade C100.00% up9 incidentsMTTR 42mCloudinaryGrade C100.00% up7 incidentsMTTR 1h 22mPusherGrade C100.00% up2 incidentsMTTR 3h 45mClerkGrade C100.00% up10 incidentsMTTR 3h 26mWorkOSGrade C100.00% up21 incidentsMTTR 1h 05mStytchGrade D99.84% up7 incidentsMTTR 57mPlaidGrade F100.00% up18 incidentsMTTR 3h 38mTwilioGrade F100.00% up55 incidentsMTTR 7h 26m

README badge

Stytch's live grade, for your README.

Stytch grade badge
[![stytch on downagain.dev](https://downagain.dev/badge/stytch.svg)](https://downagain.dev/p/stytch)