Clerk Status
System status
View historical uptime →Incident overview
Total incidents
9
Active now
1
Resolved
8
Avg. resolution
3h 44m
Recent incidents
View all →Dashboard increased latency
Delays in webhook delivery
Delayed email delivery to Microsoft (Outlook / Microsoft 365) recipients
GCP incident in us-central1-b
Elevated API latency
Increased API latency and errors
Increased error rate
Elevated error rate in domain provisioning
Related Auth services
All Auth →
Uptime Comparisons
Frequently asked questions
Is Clerk down right now?
Clerk is currently experiencing issues with 1 active incident. Current status: Degraded. Check the incident details above for more information.
What is Clerk's current uptime?
Clerk has a measured 30-day uptime of 100.00%. Over the last 24 hours, uptime is 100.00%, and over 7 days it is 100.00%. These figures are computed from Clerk's official status page data.
How many incidents has Clerk had recently?
Clerk has experienced 9 incidents in the recent monitoring window. Resolved incidents were fixed in an average of 3h 44m. 1 incident is currently active.
What components does Clerk monitor?
DevHelm tracks 15 individual components for Clerk, including Authentication & User, Machine authentication, Webhooks, Hosted UIs (Account Portal), Session management, and 10 more. Each component has its own status and 90-day uptime history shown above.
How can I get notified about Clerk outages?
You can subscribe to Clerk's incident feed via Atom/RSS at devhelm.io/status/clerk/feed.xml for use in any feed reader. For real-time alerts via Slack, email, PagerDuty, or webhooks, add Clerk as a dependency in your DevHelm workspace.
What SLA does Clerk offer?
See the full Clerk SLA report at devhelm.io/sla/clerk — including their official uptime guarantee, pricing tiers, credit policy, and how their measured uptime compares to their SLA commitment.
About Clerk status monitoring
This page provides real-time operational status for Clerk, powered by DevHelm's continuous monitoring infrastructure. We track Clerk's official status page and aggregate component-level data into uptime percentages, incident timelines, and historical trends.
Clerk status data is refreshed every 30 seconds. We currently track 15 individual components, each with its own operational status and 90-day uptime history.
Uptime percentages represent the proportion of time all monitored components reported operational status. Incident data comes from vendor-published incident timelines and includes status updates, affected components, and resolution times.
Track Clerk in your stack
Get alerted when Clerk has issues — before your users notice. Set up in 30 seconds.