Clerk Outage History

Clerk experienced elevated internal API errors for 1.3 hours, causing minor service disruption. The team deployed a mitigation that successfully restored error rates to normal levels. The incident was resolved while investigation and monitoring continued.

Clerk experienced elevated 500 error rates affecting a subset of API responses, impacting both the Dashboard and backend API services. The incident lasted 1.2 hours, during which the team deployed fixes for the session service first, followed by mitigations for the Dashboard and backend API. Services returned to normal operation after the fixes were deployed and error rates rapidly declined.

An upstream provider issue impacted domain provisioning in the Clerk service for 6 hours. The provider implemented a fix and the service showed signs of recovery. The incident was classified as minor severity.

Clerk's SCIM services experienced intermittent errors for 29 minutes due to issues with their upstream database provider in a specific region. The rest of Clerk's services remained unaffected during the incident. The issue was resolved after monitoring confirmed no errors occurred in the final 10 minutes of the incident.

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.