Clerk incident: SCIM services are facing intermittent errors

1. resolvedMay 14, 2026, 21:05 UTC

   The upstream provider marked the issue as resolved, we're continuing to monitor the database, but no error was observed.

2. monitoringMay 14, 2026, 20:47 UTC

   We're monitoring the database health, no error has been found on the last 10 minutes.

3. investigatingMay 14, 2026, 20:37 UTC

   Our upstream database provider is facing issues with a specific region where our database is deployed, we're currently seeing intermittent errors on the SCIM services. The rest of clerk is not affected

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.

• Confluent Cloud: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4Major · May 8, 2026, 01:14 UTC
• PlanetScale: There is an incident in PlanetScale GCP us-central1 region impacting Postgres database availability. We are actively investigating and will update as soon as we have more information.Major · May 14, 2026, 20:30 UTC
• Linode: [DirtyFrag] Linux Privilege Escalation VulnerabilityMinor · May 8, 2026, 13:40 UTC
• Linode: [Fragnesia] Linux Privilege Escalation VulnerabilityMinor · May 13, 2026, 21:02 UTC
• DigitalOcean: DNS service, Certificates and Managed MongoDBMinor · May 14, 2026, 13:57 UTC
• Expo: High queue times and concurrency errors for Android buildsMinor · May 14, 2026, 17:12 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