Clerk outage: Elevated errors while configuring domains

1. resolvedJul 13, 2026, 01:37 UTC

   All domains have been processed from this incident.

2. monitoringJul 12, 2026, 23:10 UTC

   The underlying issue has been resolved, a downstream provider incident. Domains which failed to be provisioned are now being reprocessed and succeeding. We are continuing to monitor.

3. monitoringJul 12, 2026, 22:05 UTC

   We are observing elevated errors while provisioning domains

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.

• Sentry: Ingestion delayed for spans, logs, crons in US regionCritical · Jul 13, 2026, 00:58 UTC
• Inngest: Issues Affecting Function Triggering from EventsMajor · Jul 10, 2026, 17:44 UTC
• LaunchDarkly: LaunchDarkly is operational but customer action may be requiredMinor · Jul 10, 2026, 16:00 UTC
• Pinecone: [Serverless][AWS][us-east-1] Increase in freshness lag for some namespacesMinor · Jul 12, 2026, 23:21 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