Clerk incident: Dashboard increased latency

1. resolvedOct 2, 2026, 06:29 UTC

   The incident is now resolved

2. monitoringOct 1, 2026, 18:34 UTC

   We have implemented a fix for this incident and are monitoring to ensure the issue does not recur.

3. identifiedOct 1, 2026, 16:00 UTC

   Latency is back to normal. We have identified the issue and are actively working on fixing it.

4. investigatingOct 1, 2026, 15:44 UTC

   We are investigating increased latency for the Clerk Dashboard!

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.

• Contentful: Issues with advanced caching on Content Delivery APIMajor · Oct 1, 2026, 09:27 UTC
• MongoDB Atlas: Trigger processing may be delayed globallyMajor · Oct 1, 2026, 15:41 UTC
• OpenAI: Issues with login, signup, and adsMajor · Oct 1, 2026, 18:46 UTC
• Shippo: Elevated error rate on Canada Post Shipment APIMajor · Oct 1, 2026, 20:05 UTC
• Shippo: Elevated error rate on USPS Shipment APIMajor · Oct 1, 2026, 22:46 UTC
• PyPI: PyPI Backends Partial AvailabilityMajor · Oct 2, 2026, 01:15 UTC
• Shippo: USPS Tracking disruptionMajor · Oct 2, 2026, 05:36 UTC
• Akamai: Origin Server Connectivity Issues with Elevated Errors in APAC RegionMinor · Sep 22, 2026, 14:28 UTC
• Cloudflare: Cloudflare One Clients are incorrectly challenged on some sitesMinor · Sep 22, 2026, 19:23 UTC
• Zoom: Service Degradation Affecting Customer Using Polycom Devices Going OfflineMinor · Sep 25, 2026, 17:45 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