- Service Status
- /
- Clerk

Is Clerk Down?
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
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 streakReachability 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.
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.
Related services
Clerk outage FAQ
Users are signed in but nobody new can sign in. Is Clerk down?
My development instance is broken. Does that mean production is down?
One-time codes are not arriving. Is that a Clerk problem?
Does a Clerk outage take my whole application down?
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
403or429means 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


