Vendor record
Clerk
Checked
Front door check counts and Clerk’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented Clerk endpoint and count the checks that got the answer it is documented to give.
Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
- Endpoint checked
- api.clerk.com
- Scope
- apiNo vendor region
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Clerk product, region or your app worked.
How we count front door checksClerk says
Incident posts from Clerk’s status page, with its titles, impact levels and times. They say what Clerk chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
9
incidents Clerk posted, last 90 days
Median recorded duration: 1h 58m. From 8 incidents with vendor-supplied starts and recorded closure times.
Most recent records · all dates
Dashboard increased latency
Not specifiedStarted, per Clerk
Closed in our record(14h 46m)
Development instances only - Apple rejecting emails
Not specifiedClerk’s postStarted, per Clerk
Latest status Clerk postedIdentified. No resolution posted.
Delays in webhook delivery
MinorClerk’s postStarted, per Clerk
Closed in our record(2h 49m)
Delayed email delivery to Microsoft (Outlook / Microsoft 365) recipients
MinorClerk’s postStarted, per Clerk
Closed in our record(4h 34m)
GCP incident in us-central1-b
MinorClerk’s postStarted, per Clerk
Closed in our record(3h 25m)
4 older records
Elevated API latency
MinorClerk’s postStarted, per Clerk
Closed in our record(1h 58m)
Increased API latency and errors
MinorClerk’s postStarted, per Clerk
Closed in our record(36m)
Increased error rate
MinorClerk’s postStarted, per Clerk
Closed in our record(53m)
Elevated error rate in domain provisioning
MinorClerk’s postStarted, per Clerk
Closed in our record(36m)
Your code, your dependencies
See which of your code paths call Clerk
Connect GitHub or GitLab to find where your public or private repository uses Clerk. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add Clerk status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is Clerk currently down?
Clerk's latest recorded status is Degraded. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did Clerk last have an outage?
The most recent closed incident record began 15 days ago and spans 14h 46m. The vendor reported an incident. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for Clerk?
No. CheckUpstream checks Clerk’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor Clerk in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track Clerk?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.