Elevated API latency

What to do

• Check whether your product depends on Clerk. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1h 45m it lasted.

  Anything that failed between 2026-08-31 13:55 UTC and 2026-08-31 15:40 UTC may need a replay.

• Subscribe to Clerk's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=clerk works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Clerk 4

1. investigatingAug 31, 2026, 1:42 PM UTC

   We're investigating elevated latency and intermittent timeouts affecting Clerk API requests. Some customers may see slow responses when loading user and organization data. Our team is looking into it and will post another update once we have more information.

   provider

2. identifiedAug 31, 2026, 2:18 PM UTC

   We identified elevated traffic affecting the Backend API and user-related requests, causing increased latency and intermittent failures. We've applied mitigation and are monitoring its effect. We'll provide another update once we confirm service stability.

   provider

3. monitoringAug 31, 2026, 3:22 PM UTC

   Mitigation has been applied and API performance has stabilized. We've deployed additional safeguards and are monitoring to confirm continued stability.

   provider

4. resolvedAug 31, 2026, 3:40 PM UTC

   API performance has remained stable following mitigation. This incident has been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.