Is Clerk Down?

No — Clerk is up

Clerk's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 323 ms

Right now

The verdict is the worse of these two. How we decide

Clerk's status page

status.clerk.com · read 4 minutes ago · checked every 3 minutes

Operational

Clerk's components, as its status page reports them
Component	Status
Authentication & User	Operational
Machine authentication	Operational
Webhooks	Operational
Hosted UIs (Account Portal)	Operational
Session management	Operational
Multi-tenant authentication	Operational
SCIM	Operational
Billing	Operational
Email delivery	Operational
SMS delivery	Operational
Dashboard	Operational
Dashboard analytics	Operational

4 more, all operational · show all 16

All of Clerk's components
Component	Status
Authentication & User	Operational
Machine authentication	Operational
Webhooks	Operational
Hosted UIs (Account Portal)	Operational
Session management	Operational
Multi-tenant authentication	Operational
SCIM	Operational
Billing	Operational
Email delivery	Operational
SMS delivery	Operational
Dashboard	Operational
Dashboard analytics	Operational
Dashboard search	Operational
Application "Go live"	Operational
Platform API	Operational
Ask AI	Operational

Open their status page

FlareWarden checks

clerk.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 323 ms
Checked: 5 hours ago

By region

Amsterdam reachable, 128 ms
Chicago reachable, 310 ms
Paris reachable, 219 ms
San Jose reachable, 252 ms
Singapore reachable, 278 ms
Stockholm reachable, 380 ms
Sydney reachable, 494 ms
Toronto reachable, 527 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	15 ms	7 ms	20 ms	92 ms
Chicago	190 ms	1 ms	23 ms	267 ms
Paris	18 ms	10 ms	18 ms	153 ms
San Jose	155 ms	2 ms	8 ms	225 ms
Singapore	194 ms	2 ms	10 ms	244 ms
Stockholm	300 ms	1 ms	10 ms	357 ms
Sydney	188 ms	1 ms	7 ms	481 ms
Toronto	242 ms	11 ms	29 ms	359 ms

We check that clerk.com loads, not every feature behind it. Test it yourself

History

Incidents Clerk reported

Since Oct 22, 15 days · from status.clerk.com

Incidents: 2
Major or critical: 1
Median to resolve: 23h 11m

SMS Delivery Issues
major · Oct 29
lasted 36m
Issues with Documentation "Ask AI"
minor · Oct 21
lasted 1d 21h

Clerk website availability

Measured by FlareWarden · clerk.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 340ms

Last 30 days

65-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of clerk.com from multiple regions every 6 hours. Clerk's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 65 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Clerk does

Clerk is a user authentication and management service for web and mobile applications. It provides hosted sign-in and sign-up screens, session handling, multi-factor codes, organization and multi-tenant support, and SCIM provisioning for enterprise customers. Applications call its frontend and backend APIs on nearly every request, which makes it a dependency for anyone reaching a signed-in page.

What an outage looks like

Users cannot sign in or are signed out mid-session, and sign-up screens hang or return errors. Clerk reports Frontend API, Backend API and Session management separately, so already signed-in users often continue while new sign-ins fail. Email Delivery and SMS Delivery are their own components, so one-time codes stop arriving while passwords still work.

What to do about it

Read status.clerk.com and check whether the affected row is Production Deployment Services or Development Services, because those are reported separately and an incident in one says nothing about the other. If Email Delivery or SMS Delivery is the failing row, tell users the code is delayed rather than asking them to reset a password. Avoid rotating keys during an incident.

Is it down for everyone, or just you?

If this page says Clerk is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Clerk outage FAQ

Users are signed in but nobody new can sign in. Is Clerk down?

That is the usual shape of a Clerk incident. Session management is reported separately from the sign-in path, so existing sessions keep being validated while new authentications fail. Impact grows over minutes as sessions expire rather than arriving all at once. Check status.clerk.com and watch the Session management and Frontend API rows.

My development instance is broken. Does that mean production is down?

Not necessarily. Clerk publishes Production Deployment Services and Development Services as separate components, so an incident affecting development instances can leave production untouched. Confirm which row is affected on status.clerk.com before pausing a release. The reverse also holds, so a healthy development instance is not evidence that production is fine.

One-time codes are not arriving. Is that a Clerk problem?

It can be. Clerk reports Email Delivery and SMS Delivery as components separate from its APIs, so sign-in can work while the code never reaches the user. If those rows are affected, the account is not locked and the password is not wrong. Tell users to wait rather than starting a password reset that also depends on email.

Does a Clerk outage take my whole application down?

Only the parts behind authentication. Pages that do not call Clerk keep serving, so marketing pages and public content usually stay up while signed-in areas fail. Clerk also reports the Clerk Dashboard separately from the APIs your application calls, so you may be unable to open the dashboard while your users are unaffected.

How we measure this

We request Clerk's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Clerk publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Clerk itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Clerk goes down

We check Clerk every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required