Hibob Outage History

We have identified the issue causing slowness in our Docs service and are working to restore normal performance.

We are currently experiencing delays with our Sandbox Refresh service. The issue has been addressed, and the service is gradually returning to normal. We apologize for the inconvenience and appreciate your patience.

We’ve identified issues affecting parts of our Hiring module. Some features may be temporarily unavailable while we work to resolve the issue. We’ll continue to provide updates as more information becomes available. We apologize for the inconvenience and thank you for your understanding.

We have identified the cause of the sandbox synchronization delay and are working to resolve it. Existing sandbox environments remain accessible.

The service is in the process of recovering, and we are continuing to monitor closely while investigating the root cause. We apologize for the disruption and thank you for your patience.

We are currently investigating a production issue that may be related to a database maintenance activity performed on Saturday during off-hours. As part of our mitigation efforts, we are reverting the recent change. This action will require restarting the production database, which may result in a brief service disruption of a few minutes. We will provide an additional update once the restart is complete and the system is fully stabilized. Thank you for your patience.

The rollback has been successfully completed, and the platform is up. However, we are still experiencing performance degradation in certain areas, and some users may encounter slowness. Our engineering team is actively investigating and working to fully restore system performance. We will continue to provide updates as we make progress.

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

We are currently running a database vacuum process to optimize performance following the rollback. This process helps reclaim storage, refresh database statistics, and improve overall query performance after the earlier maintenance and restart activities. At this time, system performance is stable, and the platform is operating normally across all core services. We are not observing any ongoing impact on customer workflows. Our engineering team continues to closely monitor the environment, reviewing performance metrics and system health indicators to ensure sustained stability and proactively address any anomalies that arise.

We are currently experiencing a delay in email delivery. This may impact several workflows. Users logging in with MFA may experience delays receiving authentication emails. Our team is working to resolve this as quickly as possible.

We are currently experiencing service disruption due to a widespread Cloudflare outage, which is affecting connectivity across multiple SaaS and internet services globally—not just HiBob. Because Cloudflare acts as a core part of internet routing and security infrastructure, the issue is causing degraded performance and temporary downtime for many platforms that rely on their network. Our systems are not the root cause, but we are impacted by the upstream failure. Current Status • HiBob services are experiencing partial or full unavailability depending on the region and network path. • Other SaaS providers and internet-facing services are also affected. • Engineering and SRE teams are monitoring the situation and validating service health as Cloudflare recovers.

Sandbox refresh operations are temporarily paused. 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.

We are currently investigating the issue. Thank you for your patience

We have identified the root cause and are working on a fix.

We’ve identified an issue where some webhooks are not receiving updates. Our team is actively investigating the root cause and working to reprocess the affected events. We’re sorry for the inconvenience and appreciate your patience.

Our team identified the root cause and is working on a fix.