Clerk Outage History

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.

Clerk's development instances experienced a 54-minute outage due to DNS resolution issues affecting the accounts.dev domain. The incident was resolved through configuration changes and coordination with the DNS provider. Production instances remained unaffected throughout the incident.