Loading status…
Loading status…
Clerk status · Security & Identity · checked (1m ago)
Also searched as Clerk.com, Clerk Auth.
No — Clerk is not down. All Clerk systems are reported operational.
According to Clerk's official status page, Clerk was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Clerk's feed reported no outage in 100.00% of our checks.
Everything above is read from Clerk's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Clerk in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Clerk provides user authentication and management as a drop-in service — sign-in and sign-up components, sessions, organisations and multi-factor, mostly used from Next.js and React applications. It sits directly in front of the application, so an outage locks users out of a site that is otherwise healthy.
Clerk's status page separates the frontend API used by the browser components from the backend API used by your server, and separates both from the dashboard. That split is important: the dashboard being down does not affect signed-in users, while a frontend API incident stops anybody signing in even though the application itself is untouched.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Clerk's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Clerk was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 1m ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Clerk's status endpoint.
Clerk has published 25 incidents in the last 12 months, the 20 most recent shown here. Only what Clerk posted itself — not every problem users hit.
resolved · Sep 16, 12:31 PM (3d ago)
resolved · Sep 4, 10:06 AM (15d ago)
resolved · Sep 1, 03:48 PM (18d ago)
resolved · Aug 31, 01:55 PM (19d ago)
resolved · Aug 4, 11:03 PM (46d ago)
resolved · Aug 1, 10:00 AM (49d ago)
resolved · Jul 31, 12:23 PM (50d ago)
resolved · Jul 16, 01:04 PM (65d ago)
resolved · Jul 16, 07:56 AM (65d ago)
resolved · Jul 12, 10:05 PM (69d ago)
resolved · Jul 9, 08:38 PM (72d ago)
resolved · Jul 1, 05:12 PM (80d ago)
resolved · Jun 18, 08:21 PM (93d ago)
resolved · Jun 18, 03:43 PM (93d ago)
resolved · Jun 15, 03:44 PM (96d ago)
resolved · Jun 12, 02:48 PM (99d ago)
resolved · Jun 9, 09:56 PM (102d ago)
resolved · May 28, 07:16 PM (114d ago)
resolved · May 26, 09:19 PM (116d ago)
resolved · May 22, 03:48 PM (120d ago)
Existing sessions keep working during many Clerk incidents, so if only new sign-ins fail, that is consistent with an outage the page may not have posted yet. Development and production instances are separate — a failure in one says nothing about the other. Clock skew on a server breaks JWT verification with an error that looks exactly like an authentication outage.
Clerk is reporting no problems right now. If it stops, these cover the same job — each shows its own live status.
Status shown for each is read from that provider's own feed, on the same schedule as this page.