Clerk incident: Increased latency on our APIs

1. resolvedJul 16, 2026, 07:58 UTC

   There was a service degradation on our caching layer that affected the latency of our APIs. The caching layer is back to normal and latency dropped to normal levels.

2. investigatingJul 16, 2026, 07:56 UTC

   There is increased latency on our APIs. We are investigating.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Clerk's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Mux: video live and playback issuesCritical · Jul 15, 2026, 19:13 UTC
• Supabase: Projects in stuck state in EU-CENTRAL-1 (Frankfurt)Major · Jul 16, 2026, 07:00 UTC
• LaunchDarkly: LaunchDarkly is operational but customer action may be requiredMinor · Jul 10, 2026, 16:00 UTC
• Confluent Cloud: Kafka cluster performance degradation for clusters in AWS region eu-central-1Minor · Jul 15, 2026, 23:33 UTC
• Akamai: Application Load Balancer reporting availability issuesMinor · Jul 16, 2026, 04:21 UTC
• Vercel: Missing Build CPU Minutes Usage DataMinor · Jul 16, 2026, 06:07 UTC

How often does Clerk have incidents?

Clerk reported 13 incidents in the last 90 days, 1 of them major or critical. A typical incident lasted 1h 2m. See Clerk's uptime and incident history