Clerk status
Is Clerk down? This is Clerk’s current status, its components and its recent incidents, read from Clerk’s official status page and refreshed every 2 minutes.
All Systems Operational
As reported by Clerk’s status page, read Oct 24, 2026, 17:32 UTC.
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 |
What a degraded performance status means, and how much downtime an SLA allows: the uptime calculator.
Recent Clerk incidents
- Issues with Documentation "Ask AI" · Oct 21, 2026, 23:50 UTC · resolved, minor impact, lasted 45 h 47 min
The Ask AI functionality in Clerk docs has been restored.
- Development instances only - Apple rejecting emails · Sep 28, 2026, 15:23 UTC · resolved, minor impact, lasted 506 h 16 min
Despite extensive efforts to reach out to Apple about this issue we still do not have a resolution from them. As this incident has been ongoing for over a month, we have decided to move towards displaying a warning message on sign in from development instance when apple emails…
- Dashboard increased latency · Oct 1, 2026, 16:10 UTC · resolved, minor impact, lasted 14 h 19 min
The incident is now resolved
- Delays in webhook delivery · Sep 16, 2026, 12:31 UTC · resolved, minor impact, lasted 1 h 8 min
All systems are functional
- Delayed email delivery to Microsoft (Outlook / Microsoft 365) recipients · Sep 4, 2026, 10:06 UTC · resolved, minor impact, lasted 4 h 34 min
Delivery to Microsoft-hosted mailboxes has been normal since 12:40 UTC. All delayed emails were delivered. This incident is resolved.
- GCP incident in us-central1-b · Sep 1, 2026, 15:48 UTC · resolved, minor impact, lasted 3 h 26 min
Latency and error rates have held steady since the last update. We will re-open if there is a resurgence in errors or latency.
- Elevated API latency · Aug 31, 2026, 13:55 UTC · resolved, minor impact, lasted 1 h 45 min
API performance has remained stable following mitigation. This incident has been resolved.
- Increased API latency and errors · Aug 4, 2026, 23:03 UTC · resolved, minor impact, lasted 37 min
We've resolved the issue with our upstream provider.
- Increased error rate · Aug 1, 2026, 10:00 UTC · resolved, minor impact, lasted 5 min
All systems are operational
- Elevated error rate in domain provisioning · Jul 31, 2026, 12:23 UTC · resolved, minor impact, lasted 37 min
Custom domain provisioning is fully operational again
- Elevated API Errors · Jul 16, 2026, 13:04 UTC · resolved, minor impact, lasted 56 min
We have confirmed that error rates have returned to baseline.
- Increased latency on our APIs · Jul 16, 2026, 07:56 UTC · resolved, minor impact, lasted 2 min
There was a service degradation on our caching layer that affected the latency of our APIs. The caching layer is back to normal and latency dropped to normal levels.
- Elevated errors while configuring domains · Jul 12, 2026, 22:05 UTC · resolved, major impact, lasted 3 h 32 min
All domains have been processed from this incident.
- Elevated errors in Account Portal · Jul 9, 2026, 20:38 UTC · resolved, minor impact, lasted 5 min
The underlying issue has been identified and the Account Portal is now fully functioning again.
- Delay in webhook delivery · Jul 1, 2026, 17:12 UTC · resolved, minor impact, lasted 14 min
We have identified the cause of the delays and our mitigations have been successful. We are continuing to monitor webhook delivery.
Source: Clerk, Clerk’s public status page, read Oct 24, 2026, 17:32 UTC. Uptimely is not affiliated with Clerk; incident text is Clerk’s own.
Is it down for you, or for everyone?
A status page shows what the vendor has confirmed, which often lags what users see. Run a live check of clerk.com to see whether it answers right now.
Get alerted when Clerk has an incident
Uptimely’s External Status Page monitor watches Clerk’s status page and alerts your team by email, SMS, phone call, Slack, Discord or browser push when it reports a problem, next to the monitors for your own services.
Status of similar services
- GitHub status
- Bitbucket status
- npm status
- Docker status
- Twilio status
- Datadog status
- Sentry status
- Supabase status
- PlanetScale status
- MongoDB Atlas status
- Elastic Cloud status
- Snowflake status
- Grafana Cloud status
- CircleCI status
- Mailgun status
- Resend status
- Segment status
- Cloudinary status
Is Clerk down right now?
The status at the top of this page is Clerk's own, read from its public status page every couple of minutes. It shows what Clerk's team has confirmed. For an independent check of whether clerk.com answers right now, use the live check on the is-it-down page.
Where is Clerk's official status page?
Clerk publishes its status at https://status.clerk.com. This page shows the same data with the recent incident history in one place, and links each incident to Clerk's own write-up.
Why does Clerk not work for me when its status says operational?
A status page lists the incidents a vendor has confirmed, and confirmation takes time: problems often reach users minutes before they reach the status page, and some partial or regional problems never appear on it. Your own network, account or region can also be the cause.
How can I get alerted when Clerk has an incident?
Add an External Status Page monitor in Uptimely pointed at https://status.clerk.com. It reads the page on a schedule and alerts your team by email, SMS, phone call, Slack, Discord or browser push when Clerk reports a problem, beside the monitors for your own services.