Hibob incident
We’ve identified an issue with our main Bob application
Hibob experienced a critical incident on October 29, 2025 affecting Compensation and Surveys and 1 more component, lasting 20h 12m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 29, 2025, 09:32 AM UTC
Our engineering team is aware of the issue and actively investigating. We’ll provide another update as soon as we have more information.
- identified Oct 29, 2025, 09:33 AM UTC
Our team is actively investigating the issue with the highest priority. Thank you for your patience
- identified Oct 29, 2025, 10:16 AM UTC
We're currently experiencing an issue affecting our database availability. Our team is working to restore full service as quickly as possible. We apologize for the disruption and appreciate your patience.
- identified Oct 29, 2025, 11:38 AM UTC
The platform has been partially available over the past period, and our team is now fully focused on stabilizing all services to ensure full availability. We’ll share more updates soon. Thank you for your continuous patience.
- monitoring Oct 29, 2025, 12:36 PM UTC
The platform is now operational, and services have been stabilized. The issue was related to a configuration update, which has since been resolved. Our team will continue to monitor performance closely to ensure stability. Thank you for your patience and understanding throughout the incident.
- resolved Oct 30, 2025, 05:27 AM UTC
The platform is now operational, and services have been stabilized. An earlier incident, related to a configuration update, caused a temporary disruption that has since been fully resolved. During the recovery process, between 10:45 and 11:15 UTC, the system was available but not fully stable. As a result, some processes or actions performed during that time may not have completed as expected. As a precaution, sandbox refresh operations are temporarily paused while we complete full remediation and validation to ensure continued stability. An update will be provided once the refresh capability is restored. Our team continues to monitor performance closely and implement improvements to prevent similar issues in the future.