60 Bob incidents · luglio 2025 — official updates, affected components, duration and resolution details.
Stiamo attualmente indagando su un problema che causa ritardi con il nostro servizio Sandbox Refresh, e stiamo lavorando per risolverlo.
Abbiamo identificato il problema che colpisce Sandbox Refresh e stiamo lavorando attivamente per affrontarlo.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Noi confermiamo che c'è un problema con i tavoli di lavoro del profilo del dipendente, e stiamo lavorando per risolverlo.
Abbiamo identificato un problema in cui gli utenti possono incontrare errori durante l'aggiunta o l'aggiornamento delle righe nelle tabelle di storia all'interno del profilo del dipendente. Il nostro team ha trovato la causa principale e sta lavorando per risolvere il problema.
Abbiamo implementato una correzione per il problema che riguarda gli aggiornamenti dei profili dei dipendenti e stiamo monitorando i risultati per confermare il problema è completamente risolto.
Il problema è stato risolto. Una regressione ha causato la validazione per eseguire tutte le voci della tabella di storia, comprese le righe storiche contenenti valori archiviati, che hanno causato l'errore di aggiornamenti. Abbiamo aggiornato la validazione per applicare solo alle righe che sono state modificate.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Stiamo indagando su un problema con il nostro Talent servizio impatto Surveys and Performance. Stiamo lavorando per risolverlo.
Noi confermiamo che c'è un problema con il nostro servizio Talent, che interessa Performance e Survey, e stiamo lavorando per risolverlo.
Una correzione è stata applicata per affrontare i problemi che interessano Performance e Surveys nel modulo Talent, e stiamo monitorando i risultati.
Il problema che riguarda il modulo Talent è stato risolto. Un problema dell'infrastruttura ha causato una maggiore latenza che ha colpito Surveys and Performance. Il servizio è rimasto stabile dopo l'attuazione di una correzione, e stiamo prendendo misure per prevenire la ricorrenza.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Abbiamo identificato un problema con il nuovo flusso di noleggio in cui solo gli amministratori possono creare nuovi noleggi.
Abbiamo identificato la causa principale e risolto il problema che riguarda il flusso di noleggio nuovo. Stiamo monitorando i risultati.
Il problema che riguarda il flusso di New Hire, dove solo gli amministratori potrebbero creare nuovi assunti, è stato risolto.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Gli utenti stanno vivendo lentezza in Bob. Stiamo lavorando per risolvere il problema.
Gli utenti stanno vivendo lentezza, interruzioni e errori in Bob, con alcune aree non funzionanti come previsto. Stiamo lavorando per risolvere il problema.
Bob è ora stabile, e stiamo continuando a monitorare il sistema.
Questo incidente è stato risolto.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
We confirm there is a problem with our Workforce Planning module, and we’re working to resolve it. Users may be unable to open existing positions and may encounter a "general error."
We have identified the issue affecting the Workforce Planning module and causing the "general error" when opening existing positions. Our team is actively working to resolve the issue as quickly as possible.
We have implemented a fix for the issue affecting the Workforce Planning module. Users should now be able to open existing positions without encountering the "general error." We are continuing to monitor the system to ensure the issue is fully resolved.
This incident has been resolved. We apologize for the inconvenience and appreciate your patience while we worked to resolve the issue.
Abbiamo identificato un problema che causa la lentezza in Bob, e stiamo lavorando per risolverlo.
Abbiamo identificato la causa della lentezza in Bob e stiamo lavorando per ripristinare le prestazioni normali.
La lentezza che colpisce Bob è migliorata. Stiamo continuando a indagare su un problema che impedisce alle cartelle e ai documenti dei dipendenti di caricare, e stiamo lavorando attivamente per ripristinare la piena funzionalità.
Tutti i servizi sono tornati alla normalità. Continuiamo a monitorare il servizio per confermare la stabilità.
L'incidente è stato risolto. Tutti i servizi sono ora operativi normalmente.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Noi confermiamo che c'è un problema che causa la lentezza con il nostro servizio Docs, e stiamo lavorando per risolverlo.
Abbiamo identificato il problema causando lentezza nel nostro servizio Docs e stiamo lavorando per ripristinare le prestazioni normali.
Una soluzione è stata applicata per il problema causando lentezza nel nostro servizio Docs. Continuiamo a monitorare il servizio per garantire che le prestazioni rimangano stabili.
Il problema che causa la lentezza nel nostro servizio Docs è stato risolto. Abbiamo applicato una correzione e confermato che il servizio è rimasto stabile durante il periodo di monitoraggio.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Attualmente stiamo vivendo ritardi con il nostro servizio Sandbox Refresh. Il problema è stato affrontato, e il servizio sta gradualmente tornando alla normalità. Ci scusiamo per l'inconveniente e apprezziamo la vostra pazienza.
Il problema è stato risolto.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
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.
The issue affecting parts of our Hiring module has been resolved. Affected features are now available again. We apologize for the inconvenience and thank you for your understanding.
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.
We have identified the cause of the sandbox synchronization delay and are working to resolve it. Existing sandbox environments remain accessible.
We have restored the sandbox synchronization process, and sandbox refreshes now reflect current production data. We are continuing to monitor the system.
The sandbox synchronization delay has been resolved. The synchronization process was restored, and sandbox refreshes now reflect current production data.
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.
We confirm there is a problem with our main HiBob application, and we’re working to resolve it.
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.
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.
We confirm there is a problem with our main HiBob application, and we’re working to resolve it.
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.
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.
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 continuing to monitor for any further issues.
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.
We confirm there is a problem with our main HiBob application and we’re working to resolve it.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We have identified an issue affecting Docs, Goals, and Surveys. Our team is actively working to resolve the problem and restore normal functionality.
We are continuing to investigate this issue.
The issue affecting Docs has been resolved. We are still experiencing issues with Goals and Surveys, and our team is actively working to resolve them.
The issue affecting Docs, Goals, and Surveys has been resolved. All services are now operating normally.
This incident has been resolved.
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.
The root cause has been identified, and email delivery is improving. A backlog of emails is still pending, and we’re monitoring closely as the sending rate continues to recover. Thank you for your patience.
The issue has been resolved, and all services are now operating normally. The email delivery delays were caused by a system issue that led to an unexpected spike in outbound email volume. We apologise for the inconvenience and thank you for your patience.
We confirm there is a problem with our main HiBob application, and we’re working to resolve it.
We detected a brief internal issue in the HiBob application. There was little to no customer impact, and the system is operating normally. We continue to monitor.
We are currently investigating this issue.
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.
We are continuing to investigate this issue.
Cloudflare has deployed a hotfix to address the root cause of the global outage. Following this change, we are seeing steady recovery across HiBob’s services. Current Status • Platform availability and connectivity are improving as Cloudflare’s network stabilizes. • Most affected flows are beginning to recover, with latency decreasing and error rates dropping. • Our Engineering and SRE teams are actively monitoring all services to ensure full restoration.
Cloudflare has confirmed that the issue is resolved and their network is back to normal. As a result, HiBob services — along with the rest of the internet that was affected — have fully recovered. Platform performance and availability are back to expected levels with no remaining degradation. We will continue working with the Cloudflare team to understand the root cause, and we will share a full post-incident review once the analysis is complete.