Clerk.io incident
Intermittent failures to v2/search and v2/recommendations
Resolved after 6 minutes, affecting API (api.clerk.io) and API (api.clerk.io), on February 24, 2026.
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.
Affected components
Update timeline
- 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.
Your product runs on more than Clerk.io
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services