Clerk.io incident

Search and Recommendations ...

Minor Resolved View vendor source →

Clerk.io experienced a minor incident on June 17, 2025 affecting Services (Search) and Services (Recommendations), lasting 20m. The incident has been resolved; the full update timeline is below.

Started
Jun 17, 2025, 09:02 AM UTC
Resolved
Jun 17, 2025, 09:22 AM UTC
Duration
20m
Detected by Pingoru
Jun 17, 2025, 09:02 AM UTC

Affected components

Services (Search)Services (Recommendations)

Update timeline

  1. investigating Jun 17, 2025, 09:02 AM UTC

    A release of Clerk.js at 10:43 AM CET introduced an error that mistakenly converted limit values from integers to strings. This caused issues for some customers where search and recommendation features were impacted, depending on the integration method used. We were alerted to the issue at 11:02 AM CET and had it fully resolved by 11:22 AM CET. Timeline: • 10:43 AM CET: Faulty release deployed • 11:02 AM CET: Issue identified and investigation started • 11:22 AM CET: Issue fully resolved We continuously analyze incidents like this to understand the root cause and improve our systems to prevent similar issues in the future. We are sorry for the inconvenience

  2. resolved Jun 17, 2025, 09:22 AM UTC

    The issue was fully resolved.