Skip to main content
Clerk logo

Is Clerk Down?

No — Clerk is up

Reachable from all 8 checked regions

Average response time: 361ms

Last checked · checks run every 6 hours

Official status page: https://status.clerk.com

Clerk uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
208ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 19 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

19-day clean streak
Aug 22: no data
Aug 23: no data
Aug 24: no data
Aug 25: no data
Aug 26: no data
Aug 27: no data
Aug 28: no data
Aug 29: no data
Aug 30: no data
Aug 31: no data
Sep 1: no data
Sep 2: 100.00% uptime, 8 checks
Sep 3: 100.00% uptime, 24 checks
Sep 4: 100.00% uptime, 29 checks
Sep 5: 100.00% uptime, 28 checks
Sep 6: 100.00% uptime, 23 checks
Sep 7: 100.00% uptime, 32 checks
Sep 8: 100.00% uptime, 48 checks
Sep 9: 100.00% uptime, 30 checks
Sep 10: 100.00% uptime, 32 checks
Sep 11: 100.00% uptime, 32 checks
Sep 12: 100.00% uptime, 32 checks
Sep 13: 100.00% uptime, 32 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 30 checks
Sep 18: 100.00% uptime, 40 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 24 checks
Aug 22 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
597ms
DNS 285ms TCP 8ms TLS 25ms TTFB 369ms
arn
472ms
DNS 330ms TCP 1ms TLS 10ms TTFB 436ms
bom
351ms
DNS 259ms TCP 3ms TLS 24ms TTFB 324ms
cdg
194ms
DNS 66ms TCP 10ms TLS 15ms TTFB 140ms
dfw
512ms
DNS 255ms TCP 25ms TLS 28ms TTFB 378ms
ewr
374ms
DNS 281ms TCP 1ms TLS 20ms TTFB 352ms
fra
113ms
DNS 35ms TCP 1ms TLS 8ms TTFB 88ms
gru
276ms
DNS 178ms TCP 1ms TLS 7ms TTFB 246ms

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 18 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.
  • 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. We only change the 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. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Clerk goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required