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
BPRODASHIP

Overview

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

By area

A+Production
0INCIDENTS
0mAFFECTED
Your users are hit: apps, APIs, databases, inference
Worst, 30dNothing.
12 in the last 6 months.
AShipping
1INCIDENTS
21d 2hAFFECTED
You can't deploy, build or manage: CI, CLI, dashboard, auth, billing
Worst, 30d
SEV 3Sep 28, 2026 · 21d 2h · some customersDevelopment instances only - Apple rejecting emails
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 down0
Sev 3 · Can't shipCan't deploy, build or manage it1
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, countries, data centres. An incident naming only a broad area (Europe, APAC) is counted under the map, not pinned.
1 place · 24 not pinned
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 12Sev 1–2

Incident history

Show all 25
Oct 21, 202645h 47mSEV 4
Issues with Documentation "Ask AI"The Ask AI feature in Clerk's documentation was broken for about two days; the API and dashboard were not mentioned.AI-graded · one model or feature
Why this grade
  1. RULES · SEV 4
    Sev 4 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · SINGLE · HIGH CONFIDENCE
    The Ask AI feature in Clerk's documentation was broken for about two days; the API and dashboard were not mentioned.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 latencyClerk investigated increased latency in the Clerk Dashboard starting October 1, 2026. The update at 16:00 UTC says latency was back to normal while work continued. A fix was implemented and monitored, and the incident was resolved on October 2 at 06:29 UTC. No customer app or API impact was 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
    Clerk Dashboard had increased latency for an unspecified period; the text names no API or customer app impact.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 deliveryWebhook deliveries were delayed for some Clerk customers starting 12:31 UTC on 2026-09-16. A mitigation was applied and delivery returned to normal pace by 13:24. The incident was resolved at 13:39, then reopened at 14:33 for similar delays, and was marked resolved again at 15:20.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 · BACK AFTER 53M
    Webhook deliveries to some customers were delayed; the provider reported normal pace after mitigation, with a brief recurrence later.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 2
Delayed email delivery to Microsoft (Outlook / Microsoft 365) recipientsEmails to Outlook.com, Hotmail and Microsoft 365 mailboxes were rate limited by the receiving side and delayed by several minutes, including one-time passcodes and verification links. Other recipients were delivered normally. Delivery returned to normal at about 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 2 · REGIONAL · HIGH CONFIDENCE · BACK AFTER 3H 28M
    Emails to Microsoft-hosted mailboxes, including one-time codes, were delayed by several minutes; other providers were unaffected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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-bA GCP incident in us-central1 disrupted the path between Clerk's services and its database, causing connection churn, elevated latency and error rates. Dashboard analytics also had impact and recovered first. Latency returned to baseline and error rates recovered by 19:13 UTC, when the incident was resolved.AI-graded · one location
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · LOCAL · MEDIUM CONFIDENCE
    Elevated errors and latency in requests between Clerk services and their database during a GCP us-central1 incident; the update does not give the share of customers hit.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 API requests, mainly user and organization data loading, experienced elevated latency and intermittent timeouts and failures from about 13:42 to 15:40 UTC on August 31. Cause was elevated traffic to the Backend API. Mitigation with additional safeguards stabilized performance and the incident was resolved.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 API requests showed elevated latency and intermittent failures for user and organization data for about two hours; scope was not specified.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 saw increased latency and errors in its FAPI and BAPI services, traced to an upstream provider. The upstream provider applied a fix, errors subsided, and the incident was resolved about 37 minutes 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 25M
    Increased latency and errors in Clerk's FAPI and BAPI services for about 37 minutes; the text does not say how many customers were hit.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 API error rate across all Clerk services for about five minutes; no components were named.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 · BACK AFTER 5M
    Elevated API error rate across all Clerk services for about five minutes; no components were named.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 provisioningElevated error rates occurred when provisioning custom domains, caused by degraded availability at a third-party infrastructure provider. Existing live applications and sign-in were not affected. A fix was implemented downstream, and provisioning was fully operational again at 13:00 UTC after about 37 minutes. Affected domains provision automatically.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 · HIGH CONFIDENCE
    Custom domain provisioning failed or was delayed for about 37 minutes; live apps and sign-in were not affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 reported elevated 429 error responses from API endpoints starting 13:04 UTC on July 16, 2026. A fix was deployed around 13:45 and error rates returned to baseline by 14:01 UTC.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 elevated 429 errors for about an hour; the text does not say how many customers were hit.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 2
Increased latency on our APIsA caching-layer degradation raised API latency for about 90 seconds; 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 2 · UNCLEAR · MEDIUM CONFIDENCE · BACK AFTER 2M
    A caching-layer degradation raised API latency for about 90 seconds; the text does not say how many customers were hit.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 domainsElevated errors while provisioning custom domains; failed provisions were retried and completed after a downstream provider fix.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
    Elevated errors while provisioning custom domains; failed provisions were retried and completed after a downstream provider fix.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 returned elevated errors for about five minutes before being fully restored; the affected scope is not stated.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 returned elevated errors for about five minutes before being fully restored; the affected scope is not stated.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 deliveryWebhook deliveries to customer apps were delayed for about 15 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 2 · UNCLEAR · MEDIUM CONFIDENCE
    Webhook deliveries to customer apps were delayed for about 15 minutes; the text does not say how many customers were hit.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 4
SVGs are not loading properlySVG images failed to load for an unspecified period and scope; the text names no product or region, so impact is hard to judge.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · UNCLEAR · LOW CONFIDENCE
    SVG images failed to load for an unspecified period and scope; the text names no product or region, so impact is hard to judge.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 from about 15:32 to 16:18 UTC on June 18, 2026. The provider identified the issue, deployed a fix, and monitored before resolving. No customer app or API impact was stated.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
    Dashboard Overview page failed to load properly for about 45 minutes; no API or app impact was described.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 showed elevated errors from an upstream service dependency for a short period before being resolved; affected customers and extent 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 · BACK AFTER -19M
    Platform API showed elevated errors from an upstream service dependency for a short period before being resolved; affected customers and extent not stated.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 some Clerk applications being taken live, caused by an upstream provider's partial outage; scope and rate 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 · MEDIUM CONFIDENCE
    Errors or delays hit some Clerk applications being taken live, caused by an upstream provider's partial outage; scope and rate not stated.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 API timed out for a portion of requests, so dashboard charts may have failed to load. The cause was a database connection closed upstream but still reused by the connection pool. Fixed by 21:56 UTC per the update; a self-healing change is being rolled out. No data was lost.AI-graded · some customers
Why this grade
  1. RULES · SEV 1
    Sev 1 because the provider reported data loss or exposure
  2. CLAUDE · SEV 4 · SUBSET · MEDIUM CONFIDENCE
    Analytics API requests failed for a portion of callers, mainly dashboard charts, for about 35 minutes; no data lost.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 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 –MapboxGrade A+99.99% up2 incidentsMTTR 12h 38mPaddleGrade A+100.00% up3 incidentsMTTR 47mLoopsGrade A+100.00% up1 incidentMTTR 1h 34mKindeGrade A+99.99% up2 incidentsMTTR 1h 12mCloudinaryGrade A99.97% up5 incidentsMTTR 1h 47mAblyGrade A99.88% up8 incidentsMTTR 27mMailgunGrade A99.96% up9 incidentsMTTR 42mPusherGrade A99.97% up2 incidentsMTTR 3h 45mInngestGrade B99.63% up14 incidentsMTTR 43mClerkGrade C99.91% up10 incidentsMTTR 3h 26mResendGrade C99.85% up26 incidentsMTTR 24mWorkOSGrade C99.56% up18 incidentsMTTR 1h 03mStytchGrade C99.83% up6 incidentsMTTR 2h 29mPlaidGrade D98.22% up18 incidentsMTTR 3h 38mTwilioGrade D98.98% up75 incidentsMTTR 9h 31m

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)