Clerk outage: Analytics API I/O timeouts

1. resolvedJun 9, 2026, 22:37 UTC

   Between 21:21 and 21:56 UTC on June 9, 2026, a portion of requests to our Analytics service failed and Dashboard charts may have failed to load. The cause was a database connection that had been silently closed upstream but was still being reused by our connection pool. We resolved the issue at 21:56 UTC. No data was lost. To prevent recurrence, we are rolling out a change to detect and self-heal from such failures. We apologize for the disruption

2. monitoringJun 9, 2026, 22:11 UTC

   We've mitigated a connection issue with the Analytics API and are now monitoring.

3. investigatingJun 9, 2026, 21:56 UTC

   Endpoints that use analytics (such as dashboard charts) are encountering timeouts. 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.

• Akamai: Edge Delivery - HTTP Content Delivery in EuropeMinor · Jun 5, 2026, 16:36 UTC
• Snyk: Email-to-Case Temporarily DisabledMinor · Jun 8, 2026, 15:47 UTC
• LaunchDarkly: Delays in event ingestionMinor · Jun 9, 2026, 12:08 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