Histórico de interrupções do Bob

1. 7 Gwengolo 2026 da 09:41 UTCinvestigating

   Atualmente estamos investigando um problema que causa atrasos com o nosso serviço Sandbox Refresh, e estamos trabalhando para resolvê-lo.

2. 7 Gwengolo 2026 da 11:55 UTCidentified

   Nós identificamos o problema impactando Sandbox Refresh e estamos trabalhando ativamente para lidar com isso.

3. 8 Gwengolo 2026 da 05:39 UTCmonitoring

   Aplicámos uma correção para os atrasos de atualização Sandbox, e o problema foi resolvido. As actualizações devem agora ser completadas de acordo com o calendário. Continuamos a monitorizar o serviço para garantir a estabilidade.

Traduzido automaticamente da atualização oficial do incidente.

1. 31 Eost 2026 da 11:33 UTCinvestigating

   Confirmamos que há um problema com as tabelas de trabalho do perfil do funcionário, e estamos trabalhando para resolvê-lo.

2. 31 Eost 2026 da 12:55 UTCidentified

   Nós identificamos um problema onde os usuários podem encontrar erros ao adicionar ou atualizar linhas em tabelas de histórico dentro do perfil do funcionário. A nossa equipa encontrou a causa principal e está a trabalhar para resolver o problema.

3. 31 Eost 2026 da 15:24 UTCmonitoring

   Implantamos uma correção para o problema que afeta atualizações de perfis de funcionários e estamos monitorando os resultados para confirmar que o problema está totalmente resolvido.

4. 31 Eost 2026 da 15:59 UTCresolved

   A questão foi resolvida. Uma regressão fez com que a validação passasse por todas as entradas da tabela de histórico, incluindo linhas históricas contendo valores arquivados, o que fez com que as atualizações falhassem. Atualizamos a validação para aplicar apenas às linhas que foram alteradas.

Traduzido automaticamente da atualização oficial do incidente.

1. 26 Eost 2026 da 07:29 UTCinvestigating

   Estamos investigando um problema com nosso serviço de Talent impactando pesquisas e desempenho. Estamos trabalhando para resolvê-lo.

2. 26 Eost 2026 da 07:34 UTCidentified

   Confirmamos que há um problema com nosso serviço de Talentos, afetando Performance e Surveys, e estamos trabalhando para resolvê-lo.

3. 26 Eost 2026 da 07:52 UTCmonitoring

   Uma correção foi aplicada para resolver os problemas que afetam Performance e Surveys no módulo Talent, e estamos monitorando os resultados.

4. 26 Eost 2026 da 08:38 UTCresolved

   O problema que afeta o módulo Talent foi resolvido. Um problema de infraestrutura causou um aumento da latência que afetou Levantamentos e Desempenho. O serviço permaneceu estável após a implementação de uma correção, e estamos tomando medidas para evitar a recorrência.

Traduzido automaticamente da atualização oficial do incidente.

1. 19 Eost 2026 da 07:44 UTCinvestigating

   Identificamos um problema com o fluxo New Hire, onde só os administradores podem criar novas contratações.

2. 19 Eost 2026 da 08:02 UTCmonitoring

   Identificamos a causa raiz e corrigimos o problema que afeta o fluxo New Hire. Estamos a acompanhar os resultados.

3. 19 Eost 2026 da 08:32 UTCresolved

   O problema que afeta o fluxo New Hire, onde apenas administradores poderiam criar novas contratações, foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 17 Eost 2026 da 08:31 UTCidentified

   Os usuários estão experimentando lentidão em Bob. Estamos trabalhando para resolver o problema.

2. 17 Eost 2026 da 08:41 UTCinvestigating

   Os usuários estão experimentando lentidão, interrupções e erros em Bob, com algumas áreas não funcionando como esperado. Estamos trabalhando para resolver o problema.

3. 17 Eost 2026 da 09:16 UTCmonitoring

   Bob agora está estável, e estamos continuando a monitorar o sistema.

4. 17 Eost 2026 da 09:56 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 4 Eost 2026 da 16:46 UTCinvestigating

   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."

2. 4 Eost 2026 da 16:49 UTCidentified

   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.

3. 4 Eost 2026 da 18:46 UTCmonitoring

   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.

4. 4 Eost 2026 da 19:14 UTCresolved

   This incident has been resolved. We apologize for the inconvenience and appreciate your patience while we worked to resolve the issue.

1. 3 Eost 2026 da 08:18 UTCinvestigating

   Identificamos um problema que causa lentidão em Bob, e estamos trabalhando para resolvê-lo.

2. 3 Eost 2026 da 08:57 UTCidentified

   Identificamos a causa da lentidão em Bob e estamos trabalhando para restaurar o desempenho normal.

3. 3 Eost 2026 da 09:31 UTCidentified

   A lentidão que afeta Bob melhorou. Continuamos a investigar um problema que impede o carregamento de pastas e documentos dos funcionários, e estamos trabalhando ativamente para restaurar toda a funcionalidade.

4. 3 Eost 2026 da 09:44 UTCmonitoring

   Todos os serviços voltaram ao normal. Continuamos a monitorizar o serviço para confirmar a estabilidade.

5. 3 Eost 2026 da 10:24 UTCresolved

   O incidente foi resolvido. Todos os serviços estão agora a funcionar normalmente.

Traduzido automaticamente da atualização oficial do incidente.

1. 29 Gouere 2026 da 10:01 UTCinvestigating

   Confirmamos que há um problema que causa lentidão com nosso serviço Docs, e estamos trabalhando para resolvê-lo.

2. 29 Gouere 2026 da 11:08 UTCidentified

   Nós identificamos o problema causando lentidão em nosso serviço Docs e estamos trabalhando para restaurar o desempenho normal.

3. 29 Gouere 2026 da 11:18 UTCmonitoring

   Foi aplicada uma correção para o problema que causa lentidão no nosso serviço Docs. Continuamos a monitorar o serviço para garantir que o desempenho permaneça estável.

4. 29 Gouere 2026 da 11:57 UTCresolved

   A questão que causa lentidão no nosso serviço médico foi resolvida. Aplicou-se correção e confirmou-se que o serviço permaneceu estável durante o período de monitoramento.

Traduzido automaticamente da atualização oficial do incidente.

1. 2 Gouere 2026 da 19:14 UTCidentified

   Atualmente estamos passando por atrasos com nosso serviço Sandbox Refresh. A questão foi abordada, e o serviço está gradualmente voltando ao normal. Pedimos desculpa pela inconveniência e apreciamos a sua paciência.

2. 3 Gouere 2026 da 06:42 UTCresolved

   A questão foi resolvida.

Traduzido automaticamente da atualização oficial do incidente.

1. 15 Mezheven 2026 da 10:08 UTCidentified

   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.

2. 15 Mezheven 2026 da 10:32 UTCresolved

   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.

1. 30 Ebrel 2026 da 08:17 UTCinvestigating

   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. 30 Ebrel 2026 da 10:04 UTCidentified

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

3. 1 Mae 2026 da 09:38 UTCmonitoring

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

4. 1 Mae 2026 da 09:40 UTCresolved

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

1. 14 Ebrel 2026 da 13:33 UTCresolved

   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.

1. 7 Ebrel 2026 da 14:56 UTCinvestigating

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

2. 7 Ebrel 2026 da 15:52 UTCmonitoring

   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. 7 Ebrel 2026 da 17:29 UTCresolved

   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.

1. 23 Meurzh 2026 da 08:27 UTCinvestigating

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

2. 23 Meurzh 2026 da 08:52 UTCinvestigating

   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. 23 Meurzh 2026 da 09:01 UTCidentified

   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. 23 Meurzh 2026 da 09:01 UTCmonitoring

   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. 23 Meurzh 2026 da 09:20 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 23 Meurzh 2026 da 09:27 UTCresolved

   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.

1. 23 Cʼhwevrer 2026 da 08:54 UTCinvestigating

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

2. 23 Cʼhwevrer 2026 da 09:40 UTCidentified

   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. 23 Cʼhwevrer 2026 da 10:10 UTCidentified

   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. 23 Cʼhwevrer 2026 da 11:00 UTCidentified

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

5. 23 Cʼhwevrer 2026 da 11:20 UTCidentified

   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. 23 Cʼhwevrer 2026 da 11:23 UTCmonitoring

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

7. 23 Cʼhwevrer 2026 da 11:34 UTCresolved

   This incident has been resolved.

1. 19 Cʼhwevrer 2026 da 08:04 UTCinvestigating

   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. 19 Cʼhwevrer 2026 da 08:23 UTCmonitoring

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

3. 19 Cʼhwevrer 2026 da 08:50 UTCresolved

   This incident has been resolved.

1. 15 Cʼhwevrer 2026 da 14:26 UTCinvestigating

   We have identified an issue affecting Docs, Goals, and Surveys. Our team is actively working to resolve the problem and restore normal functionality.

2. 15 Cʼhwevrer 2026 da 14:38 UTCinvestigating

   We are continuing to investigate this issue.

3. 15 Cʼhwevrer 2026 da 14:47 UTCinvestigating

   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.

4. 15 Cʼhwevrer 2026 da 14:52 UTCmonitoring

   The issue affecting Docs, Goals, and Surveys has been resolved. All services are now operating normally.

5. 15 Cʼhwevrer 2026 da 14:58 UTCresolved

   This incident has been resolved.

1. 29 Genver 2026 da 11:32 UTCidentified

   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.

2. 29 Genver 2026 da 13:37 UTCmonitoring

   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.

3. 29 Genver 2026 da 14:21 UTCresolved

   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.

1. 26 Genver 2026 da 10:19 UTCidentified

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

2. 26 Genver 2026 da 10:34 UTCresolved

   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.

1. 5 Kerzu 2025 da 09:06 UTCinvestigating

   We are currently investigating this issue.

2. 5 Kerzu 2025 da 09:09 UTCidentified

   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.

3. 5 Kerzu 2025 da 09:09 UTCinvestigating

   We are continuing to investigate this issue.

4. 5 Kerzu 2025 da 09:17 UTCmonitoring

   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.

5. 5 Kerzu 2025 da 09:29 UTCresolved

   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.