CheckUpstream measured Clerk at 100.000% availability across 2827 independent checks (global · api). 4 incidents were recorded in the past 12 months; the most recent resolved earlier today after 2 hours. Status signals are polled from Clerk's official Atlassian Statuspage status page, alongside independent probes and community reports.
30 days measured availability how this is computed
100.000%
global · api · n=2827 · p95 315ms (30d)
Share of our own checks against Clerk endpoints that returned Clerk's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 2 incidents · 28 of 30 days with none posted · 1h 39m of declared impact
Fewer incidents in the last 30 days than 34% of 232 tracked services.
Share of each window with no impact declared by Clerk
7d
99.339%
30d
99.770%
90d
99.895%
180d
99.948%
1y
99.974%
Downtime like this can be refundable
If you're a paying Clerk customer, outages in these windows may count against Clerk's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Clerk entitlement →Does Clerk actually matter to you?
A Clerk outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →Aug 31, 13:55 UTC · resolved in 1h 35m · Resolved
Aug 4, 23:03 UTC · resolved in 46m · Resolved
Aug 1, 10:04 UTC · resolved in 36m · Resolved
Jul 31, 12:28 UTC · resolved in 37m · Resolved
4signals across 1 source
Synthetic probes 4
All of these are CheckUpstream's own probes. Nobody else has reported Clerk in this window, so nothing here is corroboration.
Live Clerk status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/clerk)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Clerk is currently Operational. CheckUpstream tracks Clerk in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Clerk's last resolved incident started earlier today and lasted 1h 35m (a partial outage).
Looking for the live "is Clerk down" view? See the Clerk Live status page.
Clerk's 30-day measured availability is 100.000%, from CheckUpstream's own probes against Clerk endpoints. It is the share of checks that returned the expected response, not a figure taken from Clerk's status page.
Sign up to CheckUpstream and add Clerk to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Clerk's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.