We have confirmed that error rates have returned to baseline.

There was a service degradation on our caching layer that affected the latency of our APIs. The caching layer is back to normal and latency dropped to normal levels.

All domains have been processed from this incident.

The underlying issue has been identified and the Account Portal is now fully functioning again.

We have identified the cause of the delays and our mitigations have been successful. We are continuing to monitor webhook delivery.

A fix has been published and confirmed it's now resolving SVGs correctly

Services are up and running.

Systems are fully operational

All systems are operational

Between 21:21 and 21:56 UTC on June 9, 2026, a portion of requests to our Analytics service failed and Dashboard charts may have failed to load. The cause was a database connection that had been silently closed upstream but was still being reused by our connection pool. We resolved the issue at 21:56 UTC. No data was lost. To prevent recurrence, we are rolling out a change to detect and self-heal from such failures. We apologize for the disruption

APIs have returned to normal operation.

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

Systems are back to normal.

The database upgrade is now completed!

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

The issue has been resolved.

The maintenance on the SCIM database is complete.

We continue to work with our DNS provider to discover the source of the issue. We currently believe approximately 0.37% of traffic was impacted by being unable to resolve DNS of the CDN that provides ClerkJS.

We have identified the root cause and are putting in place mitigations to ensure this does not happen in the future.

The issue has been resolved

The issue has been resolved

Maintenance has completed

Development services are back to normal.

All Platform API functionality has been fully restored.