Clerk.io had 12 outages in the last 2 years totaling 37h 37m of downtime — averaging 0.5 incidents per month.
There were 12 Clerk.io outages since December 9, 2024 totaling 37h 37m of downtime. Each is summarised below — incident details, duration, and resolution information.
Today between 07:05 CEST and 07:13 CEST the main API (search and recommendations) was partially unavailable because of a database crash. We are currently investigating the crash and will be working to mitigate this in the future. We are very sorry for any inconvenience this has caused for you and your customers.
During a brief window from 07:19 (CET) to 07:24 (CET) today a faulty deployment let to instability in the API that handles search and recommendations for the /v2/ API routes. The cause was a feature update behaving differently in development vs production. The error was highlighted within minutes and the deployment was rolled back. We will perform a root cause analysis, finding out both why the bug doesn't trigger during development and how to automate detection of this case to prevent it from happening again. We sincerely apologize for any inconvenience this has caused and will continue striving to deliver an even better service.
We are currently experiencing an API slowdown caused by issues with one of our databases. The root cause has been identified, and our team is actively working on resolving the problem. We will provide updates as progress is made.
My.clerk.io and support are unavailable The production API is currently not affected - you will still see search and recommendation results on your store. Several of our service providers are currently experiencing issues, leading to timeouts and errors that prevent us from loading your account information into my.clerk.io or accessing our support tools. As this appears to be a wider internet issue, there is not much you or we can actively do at this time. We are monitoring the situation closely and will provide updates here as soon as we have more information.
We are currently experiencing intermittent failures to requests for search and recommendations. Engineering is working to restore regular service. More information and RCA will follow.
Doing internal updates of dependencies, we encountered a problem that affected some parts of our search and recommendations. We are very sorry for the inconvenience
We have experienced a slowdown in our API performance. It's solved, and we are actively working to investigate what caused the issue. We appreciate your patience.
We are currently experiencing issues with our datastore zone 2. This is now only effecting customers in datastore zone 2.