Hibob Outage History

Hibob is up right now

There were 6 Hibob outages since February 15, 2026 totaling 10h 53m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.hibob.io

Minor May 1, 2026

Sandbox Sync Delay Causing Outdated Data in Refreshes

Detected by Pingoru
May 01, 2026, 12:15 AM UTC
Resolved
May 01, 2026, 05:37 AM UTC
Duration
5h 22m
Affected: Sandbox
Timeline · 4 updates
  1. investigating Apr 30, 2026, 08:17 AM UTC

    We are currently investigating a delay in sandbox synchronization. During this time, sandbox refreshes may reflect data updated up to last night, while we work to restore full synchronization. Existing sandbox environments remain accessible. We will provide further updates as progress is made.

  2. identified Apr 30, 2026, 10:04 AM UTC

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

  3. monitoring May 01, 2026, 09:38 AM UTC

    We have restored the sandbox synchronization process, and sandbox refreshes now reflect current production data. We are continuing to monitor the system.

  4. resolved May 01, 2026, 09:40 AM UTC

    The sandbox synchronization delay has been resolved. The synchronization process was restored, and sandbox refreshes now reflect current production data.

Read the full incident report →

Notice April 14, 2026

We’ve identified an issue with our Surveys module

Detected by Pingoru
Apr 14, 2026, 12:35 PM UTC
Resolved
Apr 14, 2026, 12:35 PM UTC
Duration
Timeline · 1 update
  1. resolved Apr 14, 2026, 01:33 PM UTC

    The issue causing survey links to display empty pages and preventing responses has been resolved after fixing an error in the surveys service. We apologize for the inconvenience and thank you for your patience.

Read the full incident report →

Major April 7, 2026

Some users may experience slower-than-usual performance at the moment. Our team is aware of the issue and is actively working to identify the root cause and resolve it. We appreciate your patience and will share updates as we make progress.

Detected by Pingoru
Apr 07, 2026, 02:56 PM UTC
Resolved
Apr 07, 2026, 04:00 PM UTC
Duration
1h 4m
Affected: CompensationSurveysWorkforce planningSandboxTime OffYour VoiceLearningMobileShoutoutTime & AttendancePerformanceCoreDocsGoalsPublic pagesJob catalogEmployee Profile and FieldsReports and DirectoryTasksFlows
Timeline · 3 updates
  1. investigating Apr 07, 2026, 02:56 PM UTC

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

  2. monitoring Apr 07, 2026, 03:52 PM UTC

    System performance has been restored, and the incident is now resolved. We are continuing to monitor the system and conduct a thorough investigation to identify the root cause and implement preventive measures. Thank you for your patience during this time.

  3. resolved Apr 07, 2026, 05:29 PM UTC

    The issue that we had been experiencing has now been fully resolved, and everything is functioning as expected. After identifying the root cause and implementing the necessary fixes, we can confirm that the situation is under control and no further action is required at this time.

Read the full incident report →

Minor March 23, 2026

Investigating Performance Degradation in HiBob Application

Detected by Pingoru
Mar 23, 2026, 08:27 AM UTC
Resolved
Mar 23, 2026, 09:27 AM UTC
Duration
1h
Affected: CompensationSurveysPayroll HubPublic APIZapierWorkforce planningShoutoutTime & AttendanceCalendar integrationDocsProvisioningCollaborationJob catalog
Timeline · 7 updates
  1. investigating Mar 23, 2026, 08:27 AM UTC

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

  2. investigating Mar 23, 2026, 08:52 AM UTC

    We are currently experiencing elevated error rates and latency due to database query timeouts affecting the HiBob service, and are actively working to resolve the issue. We apologize for the disruption and thank you for your patience.

  3. identified Mar 23, 2026, 09:01 AM UTC

    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.

  4. monitoring Mar 23, 2026, 09:01 AM UTC

    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.

  5. monitoring Mar 23, 2026, 09:12 AM UTC

    We are continuing to monitor for any further issues.

  6. monitoring Mar 23, 2026, 09:20 AM UTC

    We are continuing to monitor for any further issues.

  7. resolved Mar 23, 2026, 09:27 AM UTC

    We identified a performance degradation in the HiBob application caused by resource contention and long-running database operations; mitigation actions were applied and the service has stabilized. We apologize for the disruption and thank you for your patience.

Read the full incident report →

Minor February 23, 2026

We’ve identified an issue with our main HiBob application

Detected by Pingoru
Feb 23, 2026, 08:54 AM UTC
Resolved
Feb 23, 2026, 11:34 AM UTC
Duration
2h 40m
Affected: CompensationSurveysPayroll HubPublic APIZapierWorkforce planningSandboxTime OffYour VoiceLearningMobileShoutoutTime & AttendanceCalendar integrationPerformanceCoreUS Payroll & Ben AdminDocsProvisioningGoalsPublic pagesUK PayrollCollaborationJob catalogEmployee Profile and FieldsReports and DirectoryTasksFlows
Timeline · 7 updates
  1. investigating Feb 23, 2026, 08:54 AM UTC

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

  2. identified Feb 23, 2026, 09:40 AM UTC

    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.

  3. identified Feb 23, 2026, 10:10 AM UTC

    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.

  4. identified Feb 23, 2026, 11:00 AM UTC

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

  5. identified Feb 23, 2026, 11:20 AM UTC

    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.

  6. monitoring Feb 23, 2026, 11:23 AM UTC

    A fix has been implemented and we are monitoring the results.

  7. resolved Feb 23, 2026, 11:34 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 19, 2026

Login Errors for Users Without Fully Configured SSO

Detected by Pingoru
Feb 19, 2026, 08:04 AM UTC
Resolved
Feb 19, 2026, 08:50 AM UTC
Duration
46m
Affected: Employee Profile and Fields
Timeline · 3 updates
  1. investigating Feb 19, 2026, 08:04 AM UTC

    Earlier today, we implemented a security update to our login process that affected users who attempted to log in via an external SSO provider without a fully configured SSO setup. As a result, some users encountered an error when trying to access the platform. We have since taken steps to address the issue and restore expected login behavior to ensure uninterrupted access. We are continuing to monitor the system to ensure stability. We apologize for the inconvenience and appreciate your patience.

  2. monitoring Feb 19, 2026, 08:23 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Feb 19, 2026, 08:50 AM UTC

    This incident has been resolved.

Read the full incident report →

Looking to track Hibob downtime and outages?

Pingoru polls Hibob's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Hibob reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Hibob alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Hibob for free

5 free monitors · No credit card required