Is Clerk down?
Clerk status · Security & Identity · checked (8s 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.
We've written about Clerk
- 5 min readClerk's CLI and accountless setup: adding auth without signing up
Since 30 September 2026, one command adds Clerk to a Next.js app with no Clerk account at all. It is the latest step in a six-month push to move setup, deployment and debugging into a command line built for AI coding agents as much as for people.
- 4 min readClerk's createRouteMatcher bypass (CVE-2026-41248): check that you are patched
In April 2026 Clerk disclosed a critical flaw that let crafted requests skip middleware route protection in its Next.js, Nuxt and Astro SDKs. Six months on, here is what it was, which versions fix it, and why a middleware check should never be your only auth check.
- 5 min readClerk this week: self-serve Directory Sync, accountless setup and a Dashboard slowdown
What happened at Clerk between 28 September and 5 October 2026: customers' IT admins can now set up Directory Sync themselves, new projects no longer need a Clerk account, the Dashboard had a slow afternoon, and Apple is still rejecting emails from development instances.
Is Clerk down for you right now?
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.
What Clerk is
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.
What Clerk's status feed covers
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.
Clerk uptime, last 30 days
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.
- No outage reported (99%+)
- 95–99%
- 80–95%
- Under 80%
- No data
Other services reporting problems right now
10 other services isuptime tracks were also reporting a problem as of the same check, 8s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
CloudflarePartial System Outage
- Razorpay1 of 7 services down: Payments API
- ElasticPartial System Outage
GrafanaMinor Service Outage
- PlayStation NetworkPlayStation Store affected in Russia
- SalesforceDegraded Performance: 1 active incident
- ScalewayPartially Degraded Service
- SnowflakePartially Degraded Service
Clerk response time trend
Each point is one check of Clerk's status endpoint.
Clerk outage history
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.
- Elevated error rates for authentication requests
resolved · Nov 3, 07:43 AM (23h ago)
- SMS Delivery Issues
resolved · Oct 29, 05:40 PM (5d ago)
- Issues with Documentation "Ask AI"
resolved · Oct 21, 11:50 PM (13d ago)
- Dashboard increased latency
resolved · Oct 1, 04:10 PM (33d ago)
- Development instances only - Apple rejecting emails
resolved · Sep 28, 03:23 PM (36d ago)
- Delays in webhook delivery
resolved · Sep 16, 12:31 PM (48d ago)
- Delayed email delivery to Microsoft (Outlook / Microsoft 365) recipients
resolved · Sep 4, 10:06 AM (60d ago)
- GCP incident in us-central1-b
resolved · Sep 1, 03:48 PM (63d ago)
- Elevated API latency
resolved · Aug 31, 01:55 PM (64d ago)
- Increased API latency and errors
resolved · Aug 4, 11:03 PM (91d ago)
- Increased error rate
resolved · Aug 1, 10:00 AM (94d ago)
- Elevated error rate in domain provisioning
resolved · Jul 31, 12:23 PM (95d ago)
- Elevated API Errors
resolved · Jul 16, 01:04 PM (110d ago)
- Increased latency on our APIs
resolved · Jul 16, 07:56 AM (110d ago)
- Elevated errors while configuring domains
resolved · Jul 12, 10:05 PM (114d ago)
- Elevated errors in Account Portal
resolved · Jul 9, 08:38 PM (117d ago)
- Delay in webhook delivery
resolved · Jul 1, 05:12 PM (125d ago)
- SVGs are not loading properly
resolved · Jun 18, 08:21 PM (138d ago)
- Dashboard analytics not loading properly
resolved · Jun 18, 03:43 PM (138d ago)
- Elevated errors on Platform-API
resolved · Jun 15, 03:44 PM (141d ago)
Clerk status — frequently asked
- Is Clerk down right now?
- No — Clerk is not down. All Clerk systems are reported operational. Checked (8s ago).
- What is Clerk's status right now?
- Clerk is reporting “All Systems Operational” on its official status page — Operational — as of . That status feed answered our last check in 857 ms. isuptime reads this from Clerk's own published feed and does not test Clerk independently.
- When did Clerk last go down?
- The most recent incident Clerk published was “Elevated error rates for authentication requests”, opened Nov 3, 07:43 AM UTC (23h ago) and marked resolved Nov 3, 06:15 AM UTC. That is the latest entry in Clerk's own incident feed, not every problem users experienced.
- What is Clerk's uptime?
- isuptime does not measure Clerk's uptime directly — it reads Clerk's own published status feed. Over the last 30 days, Clerk's own status feed reported no outage in 100.00% of isuptime's checks. Periods the provider called degraded count as no-outage, and this is isuptime's own measurement, not a contractual SLA.
- Is it just me, or is Clerk down for everyone?
- Clerk reports all systems operational, so the problem is likely local to your network, browser or account. Try a different network or device.
Clerk says operational but it is not working for me
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.
Alternatives to Clerk
Clerk is reporting no problems right now. If it stops, these cover the same job — each shows its own live status.
If Clerk goes down
SupabaseOperationalHosted auth with sessions and a user table behind it
FirebaseOperationalFirebase Auth, for an app that already has a Google project
Status shown for each is read from that provider's own feed, on the same schedule as this page.