Factorial HR incident

Higher error rates originating in a cache instance

Minor Resolved View vendor source →

Factorial HR experienced a minor incident on November 12, 2025 affecting API & backend and Factorial website, lasting 23m. The incident has been resolved; the full update timeline is below.

Started
Nov 12, 2025, 04:15 PM UTC
Resolved
Nov 12, 2025, 04:39 PM UTC
Duration
23m
Detected by Pingoru
Nov 12, 2025, 04:15 PM UTC

Affected components

API & backendFactorial website

Update timeline

  1. monitoring Nov 12, 2025, 04:15 PM UTC

    We are seeing application and delayed background processing due to connectivity errors to a cache instance. We have already replaced the former instance with a new one, and metrics have improved, but we are seeing a remanent of errors that we are investigating.

  2. resolved Nov 12, 2025, 04:39 PM UTC

    The issue has been resolved. We have restarted the application instances that were causing errors, and the new cache servers are being used. We will keep monitoring the situation. We apologize for the inconvenience, although we estimate the impact to have been minor.