Partial API Outage
Affected: API (api.clerk.io)
Clerk.io Outage History
Clerk.io is up right nowClerk.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.
API Downtime
Affected: API (api.clerk.io)Services (Search)Services (Recommendations)Services (Chat)Website's (my.clerk.io)
Timeline · 1 update
- resolved Aug 27, 2026, 02:30 PM UTC
The issue has been resolved, and the API is fully operational again. From 16:11 to 16:22 CEST, v2/search, v2/recommendations, and the dashboard were unavailable due to a database disruption. We are currently reviewing the incident and implementing measures to prevent such incidents from happening in the future. We apologize for the inconvenience.
clerk.io recovered
Timeline · 1 update
- resolved Jul 19, 2026, 04:48 AM UTC
clerk.io recovered
api.clerk.io recovered
Timeline · 1 update
- investigating Jun 05, 2026, 10:13 AM UTC
api.clerk.io went down
docs.clerk.io recovered
Timeline · 1 update
- investigating May 28, 2026, 02:24 PM UTC
docs.clerk.io went down
Intermittent failures to v2...
Affected: API (api.clerk.io)
Timeline · 3 updates
- investigating Feb 24, 2026, 06:19 AM UTC
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.
- resolved Feb 24, 2026, 06:25 AM UTC
Services have recovered. Post-mortem analysis underway.
- resolved Feb 24, 2026, 06:25 AM UTC
Services have recovered. Post-mortem analysis underway.
API Slowdown
Affected: API (api.clerk.io)Services (Search)Services (Recommendations)Services (Chat)Services (Email)Website's (my.clerk.io)
Timeline · 2 updates
- investigating Jan 20, 2026, 09:08 AM UTC
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.
- resolved Jan 20, 2026, 09:25 AM UTC
The issue has been resolved, and the API is fully operational again. We are currently reviewing the incident and implementing measures to prevent such incidents from happening in the future.
My.clerk.io and Support are...
Affected: Website's (my.clerk.io)
Timeline · 2 updates
- investigating Oct 20, 2025, 07:58 AM UTC
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.
- resolved Oct 21, 2025, 05:14 AM UTC
Service is now fully restored. At 00:53 CEST, AWS reported their services as fully recovered. At 03:33 CEST, our downstream provider reported their service restored as well, automatically restoring full and reliable access to my.clerk.io. We would like to reiterate that the production API and CDNs, which are used to provide the search, recommendations, and chat services for your webshop, as well as our email-related products, were unaffected during this time. Only my.clerk.io was sporadically unavailable. Nevertheless, we will be undertaking a project to ensure that the availability of my.clerk.io will not be relying on third parties to this degree but will instead gracefully degrade and let you access all your data using usual clerk.io tools, minus whatever component is currently having issues, whether that is payments or support chat.
Intermittent failures to se...
Affected: API (api.clerk.io)Services (Search)Services (Recommendations)
Timeline · 2 updates
Search and Recommendations ...
Affected: API (api.clerk.io)Services (Search)Services (Recommendations)
Timeline · 2 updates
Slowdown
Affected: API (api.clerk.io)
Timeline · 2 updates
- investigating Jul 08, 2025, 07:05 AM UTC
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.
- resolved Jul 08, 2025, 07:30 AM UTC
The issue is resolved and we keep investigating further.
Database Zone 2 Down
Affected: API (api.clerk.io)Services (Search)Services (Recommendations)Services (Chat)Services (Email)Services (Audience)Data (Data Sync)Data (Data Analyzation)
Timeline · 2 updates
- investigating Dec 09, 2024, 02:10 PM UTC
We are currently experiencing issues with our datastore zone 2. This is now only effecting customers in datastore zone 2.
- resolved Dec 09, 2024, 02:45 PM UTC
Recap: At around 15:03 CET one of our database servers began timing out on new connections, leading to API requests for stores on that particular database to experience long wait times which led to system instability. The devops team was notified by automatic monitoring and by 15:10 CET all affected stores had been put into maintenance mode, stabilizing the API operations for all other customers. The issue was diagnosed as a bug in our database software, and the affected machine was patched and re-validated before being put back into production. By 15:21 CET the first batch of stores was pulled from maintenance mode and put back into full production under monitoring. By 15:32 CET the final store was back to full production.