Clerk outage: Elevated 500 rates on API responses

1. resolvedMay 26, 2026, 22:26 UTC

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

2. monitoringMay 26, 2026, 22:08 UTC

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

3. investigatingMay 26, 2026, 22:00 UTC

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

4. investigatingMay 26, 2026, 21:53 UTC

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

5. investigatingMay 26, 2026, 21:47 UTC

   We are deploying a mitigation for the Dashboard and Backend API

6. investigatingMay 26, 2026, 21:32 UTC

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

7. investigatingMay 26, 2026, 21:19 UTC

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

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.

• Inngest: Issues connecting to data store for events/runs/metrics pagesMajor · May 26, 2026, 09:26 UTC
• ReadMe: Slow performance across customer hubsMajor · May 26, 2026, 17:41 UTC
• LiveKit: Partial data outage on LiveKit Cloud DashboardMajor · May 26, 2026, 19:53 UTC
• Inngest: Downstream provider causing dashboard loading errorsMajor · May 26, 2026, 21:31 UTC
• Elasticsearch: Missing Metrics in Cloud Console - Azure Southeast AsiaMajor · May 26, 2026, 21:35 UTC
• Linode: [Fragnesia] Linux Privilege Escalation VulnerabilityMinor · May 13, 2026, 21:02 UTC
• Akamai: Reporting Issues affecting URL Traffic and URL Responses reportsMinor · May 19, 2026, 10:13 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