Is Clerk down?
No, Clerk is not down.
Clerk’s status page reports no incidents, api.clerk.com responded from 6 regions, and nobody reported problems in the last hour.
- Official statusNo incidentsstatus.clerk.com
- Reachable6 of 6 regionsClerk Backend API · api.clerk.com
- Reports in the last hour0Normal
Clerk’s status page
From status.clerk.com. Read at
- Authentication & User Core servicesOperational
- Machine authentication Core servicesOperational
- Webhooks Core servicesOperational
- Hosted UIs (Account Portal) Core servicesOperational
- Session management Session managementOperational
- Multi-tenant authentication Enterprise / Multi-tenantOperational
- SCIM Enterprise / Multi-tenantOperational
- Billing BillingOperational
Show all 16 components
- Email delivery Communication servicesOperational
- SMS delivery Communication servicesOperational
- Dashboard Dashboard & AdministrationOperational
- Dashboard analytics Dashboard & AdministrationOperational
- Dashboard search Dashboard & AdministrationOperational
- Application "Go live" Dashboard & AdministrationOperational
- Platform API Dashboard & AdministrationOperational
- Ask AI DocumentationOperational
Not working for me
Pick what’s broken. Reports from everyone show up on the chart below within 5 minutes.
Last 24 hours
No problems in the last 24 hours, median response 169 ms, and 0 reports.
- Operational
- Degraded
- Partial outage
- Major outage
- No data
- Reachability check (api.clerk.com)
By region
| Region | Clerk Backend API api.clerk.com |
|---|---|
| N. Virginia us-east-1 | 401 · 94 ms |
| Oregon us-west-2 | 401 · 95 ms |
| Frankfurt eu-central-1 | 401 · 170 ms |
| Singapore ap-southeast-1 | 401 · 254 ms |
| Tokyo ap-northeast-1 | 401 · 173 ms |
| São Paulo sa-east-1 | 401 · 178 ms |
Two regions check Clerk every minute, and any failure is rechecked from all of them. Each row shows the latest result. How we check
Last 90 days
We have checked Clerk ourselves since Oct 28, 2026. Earlier days come from its status page.
32 days with problems in the last 90 days.
Recent incidents
Incidents: 3 in the last 30 days and 10 in the last 90, lasting a median of 3 h 7 min.
- Issues with Documentation "Ask AI"Degraded1 day
- Dashboard increased latencyDegraded14 h 18 min
- Development instances only - Apple rejecting emailsDegraded21 days
- Delays in webhook deliveryDegraded2 h 49 min
- Delayed email delivery to Microsoft (Outlook / Microsoft 365) recipientsDegraded4 h 34 min
- GCP incident in us-central1-bDegraded3 h 25 min
- Elevated API latencyDegraded1 h 44 min
- Increased API latency and errorsDegraded36 min
- Increased error rateDegraded53 min
- Elevated error rate in domain provisioningDegraded36 min
If Clerk isn’t working for you
Clerk is an authentication and user management platform for web and mobile apps, with prebuilt sign-in components.
Common Clerk errors
| Error | What it means | Usually | What to do |
|---|---|---|---|
Too many verification code requests. Please wait at least 30 seconds to receive your code before trying again. | A 429: verification codes were requested too often. | Your side | Wait 30 seconds before requesting another code. Source |
This verification has expired. You must create a new one. | The code or link expired before it was used. | Your side | Request a new code or link. Source |
is incorrect | The verification code entered is wrong. | Your side | Check the latest code and try again. Source |
Is it just you?
- If sign-in fails in one app only, check that app's Clerk instance and domain settings.
- Check the Clerk dashboard logs for the exact error code.
- Check status.clerk.com and the reports on this page.
Alternatives to Clerk
Questions
Most sign-in errors are about the code, password or session, such as an expired or incorrect verification code. If sign-in fails for everyone in several apps, check Clerk's status page.
Clerk posts incidents at status.clerk.com. If sign-in fails in several apps that use Clerk at once, Clerk is a more likely cause than any one app.
Sources: clerk.com, status.clerk.com
Get alerted when Clerk breaks your app.
If your product or your team depends on Clerk, its outage is your outage, and your users will blame you, not Clerk. Point a Site Qwality monitor at the Clerk endpoint you actually rely on, put your own site next to it, and we alert you on Slack, email, SMS or any webhook the moment either one stops answering.