Factorial HR incident
Higher error rates originating in a cache instance
Resolved after 23 minutes, affecting API & backend and Factorial website, on November 12, 2025.
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.
Affected components
Update timeline
- 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.
- 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.
Your product runs on more than Factorial HR
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