Clerk statusLiveFetched seconds agoSource: status.clerk.com
Is Clerk down?
Live status check · All systems operational
Live status pulled from status.clerk.com, cached and revalidated every 60 seconds. Below: the components that can break, what to do during an incident, and how to keep your scheduled jobs running independently.
About Clerk status
Clerk handles sign-in, sign-up, sessions, JWT verification, and organization management for many React, Next.js, and Remix apps. When Clerk degrades, users can't log in and your server can't verify existing tokens — both at once.
Components and surfaces that can break
- Surface 01
Hosted sign-in / sign-up flows.
- Surface 02
Frontend API (used by @clerk/* SDKs).
- Surface 03
Backend API (token verification, user management), webhooks.
Recent Clerk incidents
Clerk maintains a public incident history. Read the latest entries to see whether you're hitting a known issue, and look at the post-mortems for context on how long similar incidents typically take to clear.
What to do if Clerk is actually down
Existing sessions usually keep working briefly
Clerk's JWT-based sessions cache locally. Users already signed in may keep working until their next token refresh (around 60s default). Fresh sign-ins will fail.
Don't loop the sign-in component during the incident
Some apps auto-redirect to /sign-in when an auth call fails. During a Clerk outage that creates a redirect loop. Show an explicit 'authentication is currently unavailable' message instead.
Webhook delivery may be delayed, not lost
Clerk webhooks (user.created, user.updated, session.created) retry on failure. If your endpoint missed events during the incident, they'll usually arrive once Clerk recovers.
Keep firing through the incident
Schedule your own Clerk health check with Crontap
Recurring Clerk admin tasks (nightly user export, stale-session cleanup, organization invite reminders) are HTTP cron against your backend that wraps the Clerk Backend API. Crontap fires the endpoint reliably and retries on transient Clerk API errors.
External HTTP cron hits your endpoint on the cadence you pick, stores every response, and emails you the moment a run fails. Pro schedules down to 1 minute; $3.25/mo annual flat for unlimited jobs.
Go deeper
Clerk status: FAQ
- Where do I check Clerk status?
- status.clerk.com publishes component status for the dashboard, the Frontend API, and the Backend API. The history page has incident summaries.
- Why can users still browse but not sign in?
- Existing JWTs cached by the @clerk/* SDKs remain valid until the next refresh. Sign-ins, sign-ups, and token refreshes hit Clerk's Frontend API live — those are the ones that fail during an incident.
- How do I get alerted if my Clerk integration breaks?
- Crontap can probe a /api/auth/health endpoint on your app every minute. The endpoint does a small Clerk API call (e.g. clerkClient.users.getCount()); if it fails, Crontap emails you within the next minute — independent of Clerk's own status page.