api.clerk.io recovered
Timeline · 1 update
- resolved Apr 27, 2026, 06:07 AM UTC
api.clerk.io recovered
There were 4 Clerk.io outages since February 8, 2026 totaling 6m of downtime. Each is summarised below — incident details, duration, and resolution information.
api.clerk.io recovered
clerk.io recovered
docs.clerk.io recovered
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.
Services have recovered. Post-mortem analysis underway.
Pingoru polls Clerk.io's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
5 free monitors · No credit card required