Clerk Outage History

The Clerk Account Portal experienced a routing issue where some customers encountered 404 errors when accessing the root route instead of being properly redirected to the appropriate page. The service team deployed a mitigation fix and monitored the resolution. The incident lasted 2.4 hours and was classified as minor impact.

Clerk experienced a DNS-related issue that prevented Clerk JS from being downloaded, blocking sign-in and sign-up functionality for applications using Clerk components on affected domains. The incident lasted 3.7 hours and was traced to problems with DNS resolution for clerk.[domain].com subdomains. The issue was resolved after working with DNS providers to identify and fix the root cause.

The Clerk Dashboard experienced a major outage that lasted 40 minutes. The service was completely unavailable during this period, preventing users from accessing dashboard functionality. The Dashboard was restored and the incident was resolved with continued monitoring.

Clerk experienced an increased error rate affecting their APIs for 3.2 hours. The service team investigated the issue and deployed a fix. The incident was resolved with continued monitoring to ensure full recovery.

Clerk's development services experienced intermittent disruptions for 6.9 hours due to planned infrastructure updates. The issues were classified as minor and were part of expected maintenance activities. The disruptions have been resolved.

A subset of customers using Clerk's satellite domains experienced service failures starting at 1:44am UTC. The issue was identified and a revert was deployed to resolve the problem. Systems stabilized after 24 minutes with continued monitoring in place.

Clerk experienced degraded performance affecting a small subset of webhooks, causing small delays in webhook delivery. The service team investigated the issue for 28 minutes before resolving it. The incident was classified as minor with limited impact on webhook functionality.

The Clerk service experienced intermittent API errors causing elevated latency and request failures over a 7.3-hour period. The engineering team identified the root cause and applied mitigations to stabilize system performance. The incident was resolved after monitoring confirmed full recovery.

Clerk's JWT Templates service experienced increased 422 errors when organization IDs were present in requests. The issue affected JWT template functionality for 11 minutes. A fix was identified and implemented to resolve the error responses.

The Clerk service experienced increased latency and 500 errors on FAPI/BAPI endpoints for 1.6 hours. The incident affected service performance and availability, causing degraded user experience. The team implemented a mitigation mechanism that successfully restored normal operations and resolved the issue.