User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
clerk.com · AI
Is Clerk down?
Something is off: our checks are slower than usual or had a single recent failure.
What to try while Clerk is having problems
- Try a private/incognito window, or another browser or device.
- Switch between Wi-Fi and mobile data to rule out your network.
- Wait a few minutes; most incidents clear on their own.
Live diagnosis
Is it just me?
Tests clerk.com from your browser and compares it with our checks, the official status, and user reports.
Your browser → clerk.com—
Your browser → us—
Our checksSlow or flaky
Official · ReportsAll clear · Near baseline
Press Run testNothing leaves your browser except a request to the site and to us.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
What's broken
Our checks
Slow or flaky
Last check reached it in 955 ms · 5 min ago.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:00 | 0 | 0.0 | 413 ms | 0 |
| 03:15 | 0 | 0.0 | 507 ms | 0 |
| 03:30 | 0 | 0.0 | 439 ms | 0 |
| 03:45 | 0 | 0.0 | 350 ms | 0 |
| 04:00 | 0 | 0.0 | 661 ms | 0 |
| 04:15 | 0 | 0.0 | 265 ms | 0 |
| 04:30 | 0 | 0.0 | 366 ms | 0 |
| 04:45 | 0 | 0.0 | 750 ms | 0 |
| 05:00 | 0 | 0.0 | 1139 ms | 0 |
| 05:15 | 0 | 0.0 | 164 ms | 0 |
| 05:30 | 0 | 0.0 | 880 ms | 0 |
| 05:45 | 0 | 0.0 | 374 ms | 0 |
| 06:00 | 0 | 0.0 | 631 ms | 0 |
| 06:15 | 0 | 0.0 | 328 ms | 0 |
| 06:30 | 0 | 0.0 | 385 ms | 0 |
| 06:45 | 0 | 0.0 | 459 ms | 0 |
| 07:00 | 0 | 0.0 | 333 ms | 0 |
| 07:15 | 0 | 0.0 | 167 ms | 0 |
| 07:30 | 0 | 0.0 | 169 ms | 0 |
| 07:45 | 0 | 0.0 | 380 ms | 0 |
| 08:00 | 0 | 0.0 | 702 ms | 0 |
| 08:15 | 0 | 0.0 | 967 ms | 0 |
| 08:30 | 0 | 0.0 | 955 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
Embed a live Clerk status badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · JSON · MCP server
Past outages
No outages on record for Clerk yet. Outages of 10 minutes or more get their own page here.
Having trouble with Clerk?
One report per service every 10 minutes from this network. No account.
Follow Clerk
Get an email when Clerk goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Clerk alerts to Slack, Discord or a webhook — free.
Questions
Is Clerk down right now?
Something is off: our checks are slower than usual or had a single recent failure.
Clerk not working for me but the status is fine. What now?
If Clerk is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Clerk's side.
How does Damn is it down decide Clerk's status?
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
How often is Clerk checked?
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.