We’ve identified an issue with our main HiBob application

Earlier, our platform experienced a full service outage due to an unintended side effect of a legacy configuration in our production environment. During routine maintenance performed on a different, non-production cluster, a configuration that was shared behind the scenes caused an unexpected and unplanned impact on production. This legacy setup triggered the removal of a critical authentication mapping, which unexpectedly disconnected production nodes from the control plane and resulted in temporary downtime.

This effect was not expected, and the maintenance itself was completely unrelated to production. Our engineering team quickly identified the root of the issue, restored the correct configuration, and verified that all production nodes and services returned to full functionality.

The platform has remained stable since recovery, and all systems are operating normally.

We are continuing to collaborate with our internal teams and AWS Support to fully understand how this legacy dependency created such an unintended side effect.
We will implement additional safeguards and configuration isolation to ensure this scenario cannot happen again.

We experienced a temporary cluster connectivity issue that caused parts of the platform to become unavailable. The connection has been successfully restored, and all services are recovering.

We are currently investigating the root cause.

Please note that the platform may remain slow for a few minutes as systems fully stabilize.

We will provide further updates as we learn more.
Thank you for your patience.

We are continuing to work on a fix for this issue.

We confirm there is a problem with our main HiBob application, and we’re working to resolve it.