Previous incidents

We have released fix for the issue and have observed that the error rate has decreased. We expect that the issue has been resolved.

At approximately Feb 6, 2025 9:43 PM UTC we performed a configuration update to upgrade ~3700 Clerk instances with a legacy setting. Unfortunately, this update contained an error. As a result, application code ran into an error on a majority of API requests, causing downtime for the impacted instances.

We identified and addressed the root cause, with an update that ran on Feb 6, 2025, at 10:06 PM UTC. We have observed no further occurrences of this error, and performance of Clerk systems app...

Performance has been restored on both Frontend API and Backend API. We'll continue to monitor.

We applied a patch that resolves the issue. We have implemented additional tests to the area of the codebase to ensure this doesn't happen again.

The issue affecting ticket-based flows in the account portal has been identified and reverted, restoring full functionality to magic link and organization invitation based sign-ups.

The cause of the development environment errors has been identified and the issues have been resolved. If you're experiencing any other issues, please reach out to our support team.

The JSON.stringify issue has been resolved, sorry for the inconvenience.

SAML sign-in issues have been resolved.