Elevated 500 rates on API responses

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 7m it lasted.

  Anything that failed between 2026-05-26 21:19 UTC and 2026-05-26 22:26 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 7

1. investigatingMay 26, 2026, 9:19 PM UTC

   We are investigating elevated 500s affecting a subset of our API responses.

   provider

2. investigatingMay 26, 2026, 9:32 PM UTC

   We have implemented remediation for our session service. We are still investigating remediation for the Dashboard and backend API.

   provider

3. investigatingMay 26, 2026, 9:47 PM UTC

   We are deploying a mitigation for the Dashboard and Backend API

   provider

4. investigatingMay 26, 2026, 9:53 PM UTC

   We are continuing to work to deploy a mitigation for the backend API and Dashboard issues.

   provider

5. investigatingMay 26, 2026, 10:00 PM UTC

   We have deployed a fix and are observing rapid decline in error rates. We continue to monitor the situation.

   provider

6. monitoringMay 26, 2026, 10:08 PM UTC

   We have deployed a fix for this issue and our services appear to have returned to normal operation. We continue to monitor.

   provider

7. resolvedMay 26, 2026, 10:26 PM UTC

   The root cause has been identified and addressed. We will continue to monitor going forward.

   provider

Corrections

None so far.

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