Incident Library

Organisation

Clerk

Clerk · clerk

3 cases · 2025 to 2026

Root cause Cloud provider outage1Query plan regression1Breaking change in an upgrade1
Component Database3Database proxy and connection pooler1Query planner and table statistics1
Contributing factor Monitoring blind spot2Inefficient query1Limited debug access1Harmful manual action1Overlapping failures1Retry storm1Unpinned version1
Symptom High latency3Database overload2High error rate2Service outage2Connection pool exhaustion1Lock contention or deadlock1

Cases

  1. IL-0318 Clerk's APIs went down with lock contention and 429s while a Google Cloud SQL live migration slowed its database diskClerk · 2026

    Root cause Cloud provider outage

  2. IL-0317 Clerk's Postgres slowed after an automatic analyze flipped a query plan, and over 95% of requests got 429Clerk · 2026

    Root cause Query plan regression

  3. IL-0498 Clerk's Postgres database had load spikes every 15 minutes and requests failed and slowed intermittently for four daysClerk · 2025

    Root cause Breaking change in an upgrade