Dev APIs / Auth / Clerk

Clerk

OPERATIONAL

Since May 2026 · 25 incidents · status.clerk.com · checked just now

User reportsVisitors who said it's down for them, per hour over 24 hours. Not from the status page. Never counted in grades.
…
CompareAdd to stackStatus page
GradeCLast 90 days
BPRODBSHIP

Overview

30d90d1y
Admitted uptimeCustomer time not hit, by the provider's own account. Regional and partial incidents count in part.
99.919%Grade C
IncidentsEverything posted on the status page except scheduled maintenance.
100 Sev 1
Fully downMost customers down, by the provider's own account.
0m
Median fixMedian time to resolve. Half of incidents were fixed faster.
3h 26m
LongestLongest Sev 1–2 incident, start to resolved.
3h 26m
Since lastTime since the last counted incident was resolved.
18h 24m

By area

BProduction
6INCIDENTS
11h 34mAFFECTED
Your users are hit: apps, APIs, databases, inference
Worst, 90d
SEV 2Aug 31, 2026 · 1h 45mElevated API latency
SEV 2Aug 4, 2026 · 37mIncreased API latency and errors
SEV 2Sep 16, 2026 · 1h 08m · some customersDelays in webhook delivery
11 in the last 6 months.
BShipping
2INCIDENTS
21d 2hAFFECTED
You can't deploy, build or manage: CI, CLI, dashboard, auth, billing
Worst, 90d
SEV 3Sep 28, 2026 · 21d 2h · some customersDevelopment instances only - Apple rejecting emails
SEV 3Jul 31, 2026 · 37mElevated error rate in domain provisioning
9 in the last 6 months.
CleanSev 3–4Sev 1–2No data

Trend, last 12 months

25 in the last 6 months.

Severity mix

Sev 1 · Lights outProd site, API or database down, or data loss0
Sev 2 · BleedingProd degraded or partly down5
Sev 3 · Can't shipCan't deploy, build or manage it3
Sev 4 · PapercutDocs, status page, slow dashboard2

When it breaks

Start times, last 12 months, UTC.

What breaks

No components named in the last 12 months.

Where it breaks

Last 12 monthsPlaces named on the status page: cloud regions, cities, data centres. Incidents that name none stay off the map.
1 place · 24 with none named
Iowa (us-central1): 1 incident · Clerk
Sev 1–2 time by place, 12 monthsTime with a Sev 1 or 2 open that names the place, any provider. Overlaps count once.
Iowa3h 26m

Communication

Updates eachStatus page updates per incident, on average.
3.4Last 12 months
Update gapMedian time between status page updates during an incident.
18mLast 12 months
PostmortemsSev 1–2 incidents with a published write-up.
0 of 11Sev 1–2

Incident history

Show all 25
Oct 21, 202645h 47mSEV 4
Issues with Documentation "Ask AI"The Ask AI assistant in Clerk's documentation was broken for an unspecified period; no API or account impact is described.AI-graded
Why this grade
  1. RULES · SEV 4
    Sev 4 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · UNCLEAR · HIGH CONFIDENCE
    The Ask AI assistant in Clerk's documentation was broken for an unspecified period; no API or account impact is described.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
2 updates
  1. 23:50 UTC · identified
    We are investigating an issue with the Ask AI functionality in the Clerk Docs.
  2. 21:37 UTC · resolved
    The Ask AI functionality in Clerk docs has been restored.
Source
Oct 1, 202614h 19mSEV 4
Dashboard increased latencyThe Clerk Dashboard had increased latency. An update says latency was back to normal, then a fix was deployed and monitored before the incident was resolved about 14 hours later. No API impact was reported.AI-graded
Why this grade
  1. RULES · SEV 4
    Sev 4 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · UNCLEAR · MEDIUM CONFIDENCE
    Clerk Dashboard experienced increased latency; the text does not say how widely or for how long it was felt, and no API impact is mentioned.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
4 updates
  1. 15:44 UTC · investigating
    We are investigating increased latency for the Clerk Dashboard!
  2. 16:00 UTC · identified
    Latency is back to normal. We have identified the issue and are actively working on fixing it.
  3. 18:34 UTC · monitoring
    We have implemented a fix for this incident and are monitoring to ensure the issue does not recur.
  4. 06:29 UTC · resolved
    The incident is now resolved
Source
Sep 28, 202621d 2hSEV 3
Development instances only - Apple rejecting emailsSince September 28, 2026, emails sent from Clerk development instances to icloud.com and me.com addresses have been rejected by Apple. Clerk is still waiting on Apple for a fix. It will show a warning on sign-in from development instances using Apple emails and has closed the incident notice. Test emails or non-Apple addresses work as workarounds.AI-graded · some customers
Why this grade
  1. RULES · SEV 3
    Sev 3 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · SUBSET · MEDIUM CONFIDENCE
    Emails from development instances to Apple addresses were rejected by Apple for over a month; production instances were not affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
2 updates
  1. 15:23 UTC · identified
    We discovered today that emails sent only from development instances to Apple email addresses (icloud.com, me.com) are being rejected by Apple. We have reached out to Apple to inquire further and are hoping for a swift resolution on their end. In the meantime, we recommend using test emails (<https://clerk.com/docs/guides/development/testing/test-emails-and-phones#email-addresses>) or an email address from a non-Apple domain to test/send emails from your development instances.
  2. 17:39 UTC · resolved
    Despite extensive efforts to reach out to Apple about this issue we still do not have a resolution from them. As this incident has been ongoing for over a month, we have decided to move towards displaying a warning message on sign in from development instance when apple emails are used to sign in and taking down this incident notification. We apologize for the inconvenience and genuinely hope that we hear back from Apple soon on this matter.
Source
Sep 16, 20261h 08mSEV 2
Delays in webhook deliveryClerk webhook deliveries were delayed for some customers starting 12:31 UTC on 16 September 2026. A mitigation was applied and deliveries returned to normal pace by 13:24. The delays recurred from 14:33 and webhook delivery was reported normal again by 14:58. The provider did not give a root cause.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
    Webhook deliveries to customer apps were delayed for some customers in two episodes; delivery returned to normal pace each time.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
6 updates
  1. 12:31 UTC · identified
    Currently there are delays for some customers in webhook delivery. The issue has been identified and we are working towards a resolution
  2. 13:24 UTC · monitoring
    A mitigation has been applied. Webhooks are being delivered at the normal pace. We continue monitoring
  3. 13:39 UTC · resolved
    All systems are working
  4. 14:33 UTC · investigating
    Delays in webhook deliveries for some customers
  5. 14:58 UTC · monitoring
    Webhook delivery is normal at the moment. We are closely monitoring
  6. 15:20 UTC · resolved
    All systems are functional
Source
Sep 4, 20264h 34mSEV 3
Delayed email delivery to Microsoft (Outlook / Microsoft 365) recipientsEmails to Outlook.com, Hotmail and Microsoft 365 recipients were delayed by several minutes due to receiver-side rate limiting, including one-time passcodes and verification links. Other providers delivered normally. Delivery returned to normal around 12:40 UTC, and all delayed emails were delivered.AI-graded · regional
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · REGIONAL · HIGH CONFIDENCE
    Emails to Microsoft-hosted mailboxes were delayed several minutes by receiver-side rate limiting for about three hours; other providers were unaffected.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
4 updates
  1. 10:06 UTC · investigating
    We are seeing delays in email delivery for recipients on Microsoft-hosted mailboxes (Outlook.com, Hotmail, Microsoft 365). Affected emails, including one-time passcodes and verification links, may arrive late or require re-sending. Emails to other providers are delivering normally. We are working with our email provider to restore normal delivery.
  2. 11:37 UTC · identified
    We've found the cause. Emails to Microsoft-hosted mailboxes (Outlook.com, Hotmail, Microsoft 365) are being rate limited on the receiving side, and other email senders are seeing the same thing today. Emails are still accepted but some are delayed by several minutes while they're retried. Emails to all other providers are delivering normally. We're monitoring and will update when delivery times return to normal. If a code hasn't arrived, requesting a new one is the fastest workaround.
  3. 13:33 UTC · monitoring
    Delivery to Microsoft-hosted mailboxes returned to normal at about 12:40 UTC and delayed emails have been delivered. We are monitoring to confirm it stays that way.
  4. 14:40 UTC · resolved
    Delivery to Microsoft-hosted mailboxes has been normal since 12:40 UTC. All delayed emails were delivered. This incident is resolved.
Source
Sep 1, 20263h 26mSEV 2
GCP incident in us-central1-bClerk's services in us-central1 were impacted by several GCP incidents. The path to the database caused connection churn and elevated error rates, and dashboard analytics and metrics were also affected. Error rates and latency returned to baseline and the incident was resolved after about three and a half hours.AI-graded · regional
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Auth API requests in us-central1 saw elevated errors and latency for about three hours due to GCP problems; dashboard analytics were also affected.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
6 updates
  1. 15:48 UTC · monitoring
    GCP has several incidents open in us-central1 currently. We are proactively monitoring impact to customer traffic and have so far noted impact to analytics and some of our metrics. We will update shortly with further information.
  2. 16:13 UTC · monitoring
    Dashboard analytics have recovered and we're continuing to monitor for additional impact from the GCP incidents.
  3. 17:30 UTC · monitoring
    The path between our services and the database provider is currently impacted, leading to connection churn and elevated error rates.
  4. 17:49 UTC · monitoring
    We are noting recovery in the path between our services and the database provider, but latency and error rate are still elevated above baseline.
  5. 18:35 UTC · monitoring
    latency metrics have returned to baseline, and we're seeing recovery in error rates. We are continuing to monitor for any signs of resurgence and will update accordingly.
  6. 19:13 UTC · resolved
    Latency and error rates have held steady since the last update. We will re-open if there is a resurgence in errors or latency.
Source
Aug 31, 20261h 45mSEV 2
Elevated API latencyClerk's Backend API had elevated latency and intermittent timeouts when loading user and organization data, caused by elevated traffic. Mitigation and extra safeguards were applied, performance stabilized, and the incident was resolved about 1h45m after it started.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE · BACK AFTER 1H 27M
    Clerk Backend API requests saw elevated latency and intermittent failures for user and organization data; the text does not say how many customers were hit.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
4 updates
  1. 13:42 UTC · investigating
    We're investigating elevated latency and intermittent timeouts affecting Clerk API requests. Some customers may see slow responses when loading user and organization data. Our team is looking into it and will post another update once we have more information.
  2. 14:18 UTC · identified
    We identified elevated traffic affecting the Backend API and user-related requests, causing increased latency and intermittent failures. We've applied mitigation and are monitoring its effect. We'll provide another update once we confirm service stability.
  3. 15:22 UTC · monitoring
    Mitigation has been applied and API performance has stabilized. We've deployed additional safeguards and are monitoring to confirm continued stability.
  4. 15:40 UTC · resolved
    API performance has remained stable following mitigation. This incident has been resolved.
Source
Aug 4, 202637mSEV 2
Increased API latency and errorsClerk's FAPI and BAPI services had increased latency and errors from 23:03 to 23:40 UTC on 4 August 2026. The cause was an upstream provider issue, which they fixed. Clerk resolved the incident after monitoring the recovery. No customer scope was given.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Clerk's frontend and backend APIs had elevated latency and errors for about 37 minutes due to an upstream provider issue; scope was not stated.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
4 updates
  1. 23:03 UTC · investigating
    We are currently investigating an increase in latency and errors in our FAPI and BAPI services.
  2. 23:14 UTC · identified
    We've identified the issue with our upstream provider and are working on resolution.
  3. 23:29 UTC · monitoring
    Our upstream provider has applied a fix and we've seen latency and errors subside. We continue to monitor the situation.
  4. 23:40 UTC · resolved
    We've resolved the issue with our upstream provider.
Source
Aug 1, 20265mSEV 2
Increased error rateElevated error rate across all Clerk services for about five minutes, then resolved; no partial outage described.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · GLOBAL · MEDIUM CONFIDENCE
    Elevated error rate across all Clerk services for about five minutes, then resolved; no partial outage described.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
2 updates
  1. 10:04 UTC · identified
    Elevated error rate across all service
  2. 10:04 UTC · resolved
    All systems are operational
Source
Jul 31, 202637mSEV 3
Elevated error rate in domain provisioningClerk saw elevated errors when provisioning custom domains from 12:23 to 13:00 UTC on July 31, 2026, caused by degraded availability at a third-party infrastructure provider. Existing live apps, sign-in, sign-up and sessions were unaffected. Affected domains were to provision automatically once the provider recovered; a fix was applied and provisioning was declared fully operational.AI-graded
Why this grade
  1. RULES · SEV 3
    Sev 3 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · UNCLEAR · MEDIUM CONFIDENCE
    Custom domain provisioning failed or delayed for about 37 minutes; live apps, sign-in and sessions were not affected.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
4 updates
  1. 12:23 UTC · investigating
    Elevated error rates when provision a custom domain. Existing live applications and sign-in/sign-up and sessions are not affected.
  2. 12:28 UTC · identified
    Domain provisioning is currently delayed due to degraded availability at a third-party infrastructure provider. Existing live applications and session/sign-in/sign-up traffic are not affected. Affected domains will provision automatically once the provider recovers. No action is needed on your side. We will update once resolved.
  3. 12:52 UTC · monitoring
    A fix has been implement by the downstream provider. We are closely monitoring.
  4. 13:00 UTC · resolved
    Custom domain provisioning is fully operational again
Source
Jul 16, 202656mSEV 2
Elevated API ErrorsClerk API endpoints returned unexpected 429 rate-limit errors from about 13:04 to 14:01 UTC on July 16, 2026. A fix was deployed around 13:45 and error rates returned to baseline by 14:01. The text gives no count of affected customers.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    API endpoints returned spurious 429 errors for about an hour; the text does not say how many customers were hit.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
5 updates
  1. 13:04 UTC · investigating
    Reports of 429 error responses from API endpoints
  2. 13:08 UTC · investigating
    We're continuing to investigate.
  3. 13:27 UTC · investigating
    We're continuing to investigate.
  4. 13:45 UTC · monitoring
    We've deployed a fix and are seeing error rates decrease. We are monitoring.
  5. 14:01 UTC · resolved
    We have confirmed that error rates have returned to baseline.
Source
Jul 16, 20262mSEV 4
Increased latency on our APIsClerk APIs had increased latency for about 90 seconds from a caching-layer degradation; no failures reported.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 · BACK AFTER 2M
    Clerk APIs had increased latency for about 90 seconds from a caching-layer degradation; no failures reported.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
2 updates
  1. 07:56 UTC · investigating
    There is increased latency on our APIs. We are investigating.
  2. 07:58 UTC · resolved
    There was a service degradation on our caching layer that affected the latency of our APIs. The caching layer is back to normal and latency dropped to normal levels.
Source
Jul 12, 20263h 32mSEV 3
Elevated errors while configuring domainsDomain provisioning failed with elevated errors for about 3.5 hours due to a downstream provider issue; blocked setup of new domains.AI-graded
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · UNCLEAR · MEDIUM CONFIDENCE
    Domain provisioning failed with elevated errors for about 3.5 hours due to a downstream provider issue; blocked setup of new domains.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
3 updates
  1. 22:05 UTC · monitoring
    We are observing elevated errors while provisioning domains
  2. 23:10 UTC · monitoring
    The underlying issue has been resolved, a downstream provider incident. Domains which failed to be provisioned are now being reprocessed and succeeding. We are continuing to monitor.
  3. 01:37 UTC · resolved
    All domains have been processed from this incident.
Source
Jul 9, 20265mSEV 4
Elevated errors in Account PortalClerk's Account Portal showed elevated errors for about five minutes before being fully restored; no customer apps were named as affected.AI-graded
Why this grade
  1. RULES · SEV 4
    Sev 4 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · UNCLEAR · MEDIUM CONFIDENCE
    Clerk's Account Portal showed elevated errors for about five minutes before being fully restored; no customer apps were named as affected.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
2 updates
  1. 20:38 UTC · investigating
    We are observing evaluated errors in account portal and actively investigating the source of the problem
  2. 20:43 UTC · resolved
    The underlying issue has been identified and the Account Portal is now fully functioning again.
Source
Jul 1, 202614mSEV 2
Delay in webhook deliveryClerk webhook deliveries to customer apps were delayed for about 14 minutes; the scope of affected customers is not stated.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Clerk webhook deliveries to customer apps were delayed for about 14 minutes; the scope of affected customers is not stated.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
2 updates
  1. 17:12 UTC · investigating
    We are investigating delays in webhook delivery. We have deployed mitigations and are continuing to monitor.
  2. 17:26 UTC · resolved
    We have identified the cause of the delays and our mitigations have been successful. We are continuing to monitor webhook delivery.
Source
Jun 18, 20262mSEV 2
SVGs are not loading properlySVG assets failed to load properly for an unspecified share of users for about two hours; no scope was given.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · LOW CONFIDENCE
    SVG assets failed to load properly for an unspecified share of users for about two hours; no scope was given.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
3 updates
  1. 18:26 UTC · investigating
    SVGs are not loading properly, the team is investigating a fix
  2. 20:13 UTC · monitoring
    A fix has been deployed and we're seeing improved rates of resolution on the SVGs
  3. 20:23 UTC · resolved
    A fix has been published and confirmed it's now resolving SVGs correctly
Source
Jun 18, 202635mSEV 4
Dashboard analytics not loading properlyClerk's dashboard Overview page was not loading properly. The issue was identified, a fix was implemented and monitored, and the incident was resolved about 35 minutes after it started. No customer app or API impact is described.AI-graded
Why this grade
  1. RULES · SEV 4
    Sev 4 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · UNCLEAR · MEDIUM CONFIDENCE · BACK AFTER 15M
    Clerk's dashboard Overview analytics page failed to load for a period; the text does not describe impact on customer apps or API requests.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
4 updates
  1. 15:32 UTC · investigating
    Dashboard Overview page is not loading properly.
  2. 15:50 UTC · identified
    Issue identified
  3. 15:59 UTC · monitoring
    A fix has been implemented, we are currently monitoring the affected services.
  4. 16:18 UTC · resolved
    Services are up and running.
Source
Jun 15, 20260mSEV 3
Elevated errors on Platform-APIPlatform API requests returned elevated errors for about nine minutes due to an upstream service problem; customer apps were not described as affected.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · UNCLEAR · LOW CONFIDENCE
    Platform API requests returned elevated errors for about nine minutes due to an upstream service problem; customer apps were not described as affected.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
2 updates
  1. 15:17 UTC · investigating
    Elevated errors were observed in platform API when communicating with an upstream service
  2. 15:26 UTC · resolved
    Systems are fully operational
Source
Jun 12, 202641mSEV 3
Elevated errors or delays for Clerk application going liveErrors or delays hit Clerk applications going live during an upstream partial outage for about 40 minutes; scope not stated.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · UNCLEAR · LOW CONFIDENCE
    Errors or delays hit Clerk applications going live during an upstream partial outage for about 40 minutes; scope not stated.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
3 updates
  1. 14:48 UTC · identified
    An upstream provider has a partial outage. Errors or delays might be encountered when a Clerk application goes live. We are monitoring the situation.
  2. 15:03 UTC · monitoring
    A fix has been implemented by the upstream provider. We are monitoring the results
  3. 15:29 UTC · resolved
    All systems are operational
Source
Jun 9, 202641mSEV 4
Analytics API I/O timeoutsClerk's Analytics service failed a portion of requests from about 21:21 to 21:56 UTC on June 9, 2026, so dashboard charts may not have loaded. The cause was a database connection silently closed upstream but still reused by the connection pool. The issue was resolved and no data was lost. A change to detect and self-heal from such failures is rolling out.AI-graded
Why this grade
  1. RULES · SEV 1
    Sev 1 because the provider reported data loss or exposure
  2. CLAUDE · SEV 4 · UNCLEAR · MEDIUM CONFIDENCE · BACK AFTER 15M
    Analytics API requests timed out for a portion of calls; dashboard charts may have failed to load, with no data loss.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
3 updates
  1. 21:56 UTC · investigating
    Endpoints that use analytics (such as dashboard charts) are encountering timeouts. We are investigating.
  2. 22:11 UTC · monitoring
    We've mitigated a connection issue with the Analytics API and are now monitoring.
  3. 22:37 UTC · resolved
    Between 21:21 and 21:56 UTC on June 9, 2026, a portion of requests to our Analytics service failed and Dashboard charts may have failed to load. The cause was a database connection that had been silently closed upstream but was still being reused by our connection pool. We resolved the issue at 21:56 UTC. No data was lost. To prevent recurrence, we are rolling out a change to detect and self-heal from such failures. We apologize for the disruption
Source

Peers, 90 days

Compare
MailerSendGrade A+100.00% up0 incidentsMTTR –LoopsGrade A+100.00% up1 incidentMTTR 1h 34mKindeGrade A+99.99% up2 incidentsMTTR 1h 12mCloudinaryGrade A99.97% up5 incidentsMTTR 1h 47mPaddleGrade A99.99% up3 incidentsMTTR 47mAblyGrade A99.98% up7 incidentsMTTR 7mMailgunGrade A99.96% up9 incidentsMTTR 42mPusherGrade A99.96% up2 incidentsMTTR 3h 45mResendGrade B99.87% up25 incidentsMTTR 24mInngestGrade B99.75% up14 incidentsMTTR 43mMapboxGrade C99.91% up2 incidentsMTTR 12h 38mClerkGrade C99.92% up10 incidentsMTTR 3h 26mWorkOSGrade C99.49% up21 incidentsMTTR 1h 05mStytchGrade C99.79% up7 incidentsMTTR 57mPlaidGrade F98.16% up18 incidentsMTTR 3h 38mTwilioGrade F96.40% up56 incidentsMTTR 7h 26m

README badge

Clerk's live grade, for your README.

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