Histórico de interrupções do Float

1. 21 Here 2026 da 19:35 UTCresolved

   Em 21 de outubro de 2026, uma vulnerabilidade de segurança foi divulgada publicamente em um popular componente de software de código aberto usado em toda a indústria, inclusive em partes de nossa infraestrutura web. Após a divulgação, nossa equipe de engenharia avaliou prontamente o impacto potencial nos serviços da Float, implementou medidas de proteção provisórias e implantou atualizações de segurança emitidas por fornecedores em todos os sistemas afetados. Todas as atualizações foram aplicadas sem interrupção do serviço. Nossa investigação não encontrou evidências de que esta vulnerabilidade foi explorada contra a Float ou que quaisquer dados de clientes foram afetados. Continuamos a monitorar nosso ambiente como parte de nossas práticas de segurança padrão. Nenhuma ação é necessária aos clientes. Se tiver alguma dúvida, contacte a nossa equipa de apoio. Atualização — 22 de outubro de 2026: Para referência, este incidente abordou duas vulnerabilidades relacionadas no tempo de execução do PHP, CVE-2026-109618 e CVE-2026-109619, coletivamente conhecido como "PHP2Shell"

Traduzido automaticamente da atualização oficial do incidente.

1. 9 Here 2026 da 08:34 UTCresolved

   Entre aproximadamente 14:30 e 15:00 UTC em 8 de outubro de 2026, alguns clientes foram incapazes de alcançar Float. Identificamos a causa como uma atualização de configuração de rede de rotina, que resultou em problemas de disponibilidade inesperados e isolados. O problema foi resolvido, e estamos a trabalhar com o nosso fornecedor para garantir que não volte a acontecer.

Traduzido automaticamente da atualização oficial do incidente.

1. 14 Mae 2026 da 08:37 UTCinvestigating

   We are currently experiencing issues with the search and filter function. Our team is actively working on a fix.

2. 14 Mae 2026 da 08:48 UTCmonitoring

   We've implemented a fix for the issues reported with the search and filter function. We are actively monitoring performance.

3. 14 Mae 2026 da 19:42 UTCresolved

   The issue affecting the search and filter has been resolved, and the system is now operating normally.

1. 14 Mae 2026 da 07:31 UTCinvestigating

   There is an issue with one of our infrastructure providers that may be resulting in errors or delays in data propagation in Float. Based on our initial assessment, core functionalities should not be impacted. We're monitoring the issue and we will update when we know more.

2. 14 Mae 2026 da 09:26 UTCmonitoring

   The issue has been identified by the infrastructure provider and a fix has been applied. We will continue to monitor our services to make sure everything recovered properly.

3. 14 Mae 2026 da 09:26 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 14 Mae 2026 da 15:56 UTCresolved

   This incident has been resolved.

1. 13 Meurzh 2026 da 13:45 UTCinvestigating

   We are currently experiencing issues with the Search function. Our team is actively working on a fix.

2. 13 Meurzh 2026 da 15:06 UTCmonitoring

   We've implemented a fix for the issues reported with the Search function. We are actively monitoring performance to confirm the issue has been fully resolved.

3. 13 Meurzh 2026 da 15:28 UTCresolved

   The issue affecting Search has been resolved, and the system is now operating normally.

1. 6 Cʼhwevrer 2026 da 19:35 UTCinvestigating

   We're currently investigating issues with our search service. Newly changed items may not be visible in search.

2. 6 Cʼhwevrer 2026 da 19:55 UTCidentified

   We've identified the issue and we're working to resolve it.

3. 7 Cʼhwevrer 2026 da 00:44 UTCresolved

   The issue is resolved.

1. 5 Kerzu 2025 da 09:17 UTCinvestigating

   We are currently investigating reports of issues accessing Float.com due to an issue with an upstream provider. We are continuing to investigate and will share additional details as soon as they become available.

2. 5 Kerzu 2025 da 09:27 UTCmonitoring

   The issue with an upstream provider has been resolved and we're continuing to monitor Float.com.

3. 5 Kerzu 2025 da 09:41 UTCresolved

   The issue with the upstream provider has now been resolved.

1. 20 Here 2025 da 20:11 UTCinvestigating

   We've observed an issue with services causing the reports and search to fail. We're investigating the issue and will report here as soon as identified and resolved.

2. 20 Here 2025 da 22:46 UTCmonitoring

   The issue was identified to be related to global internet disruptions caused by an AWS outage. We've implemented a fix to resolve the problems affecting reports and search, as well as another issue identified with integrations. We're now monitoring the services to ensure there are no further disruptions.

3. 21 Here 2025 da 13:58 UTCresolved

   This incident has been resolved. Reports, search, and integrations are back to normal operation.

1. 18 Gouere 2025 da 16:04 UTCidentified

   There is an issue with Google Cloud our infrastructure provider that may be causing issues with; Logins with Google, slow responses in the float app, some requests may need to be retried. We're monitoring the issue and we will update when we know more.

2. 18 Gouere 2025 da 18:57 UTCresolved

   This incident has been resolved.

1. 1 Gouere 2025 da 01:08 UTCinvestigating

   We've observed an issue that teams are unable to add new Projects from the Allocations modal.

2. 1 Gouere 2025 da 02:25 UTCmonitoring

   We've deployed a fix for adding new Projects from the Allocations modal.

3. 1 Gouere 2025 da 03:50 UTCresolved

   This incident has been resolved.

1. 12 Mezheven 2025 da 19:04 UTCidentified

   We have identified an issue with our hosting provider Google Cloud which is affecting the Float Application. Issues for customers include slow loading times, or loading failures of the Float Application. We're working on the issue now and will continue to update.

2. 12 Mezheven 2025 da 21:56 UTCmonitoring

   While there are still issues with our underlying provider we've seen stabilisation for the Float Application. We'll continue to monitor and update.

3. 12 Mezheven 2025 da 23:10 UTCresolved

   Issue is resolved.

1. 27 Cʼhwevrer 2025 da 11:41 UTCidentified

   We've identified issues with response times for the Float Application while performing routine changes. We're actively working to implement a fix and will update as we progress.

2. 27 Cʼhwevrer 2025 da 12:42 UTCmonitoring

   We've implemented a fix and are now monitoring

3. 27 Cʼhwevrer 2025 da 12:59 UTCresolved

   This issue has been resolved.

1. 22 Genver 2025 da 09:12 UTCinvestigating

   We have some issues with requests to the Float application. While we've identified the issue there may still be problems with some requests made to Float while we identify a fix.

2. 22 Genver 2025 da 15:51 UTCresolved

   We've identified and released some changes to support previous issues. We'll continue to monitor going forward.

1. 9 Gouere 2024 da 21:07 UTCinvestigating

   The float.com site is inaccessible for some people, we're investigating the issue. The float app continues to work fine and workflows for teams using the resource management tool is not affected.

2. 10 Gouere 2024 da 09:22 UTCresolved

   A patch has been issued and we're monitoring.

1. 7 Meurzh 2024 da 21:03 UTCinvestigating

   We are investigating an issue with our cloud provider that is causing problems for customers viewing their schedules.

2. 7 Meurzh 2024 da 21:23 UTCidentified

   We've identified the issue and are working to resolve it.

3. 7 Meurzh 2024 da 21:33 UTCmonitoring

   We implemented a fix and can see the problem has stopped. We're monitoring now to check it doesn't re-occur.

4. 7 Meurzh 2024 da 22:00 UTCresolved

   This incident has been resolved.

1. 5 Meurzh 2024 da 16:08 UTCinvestigating

   We are experiencing degraded performance from our 3rd party identity provider, causing high latency for SSO authentication.

2. 5 Meurzh 2024 da 17:03 UTCresolved

   This incident has been resolved.

1. 30 Genver 2024 da 12:34 UTCidentified

   An issue with database connectivity has been identified while running a routine deployment. We're working to get Float back up and operational.

2. 30 Genver 2024 da 13:06 UTCmonitoring

   We've implemented a failover for our production database and we're seeing healthy requests and responses. We'll continue to monitor the situation.

3. 30 Genver 2024 da 13:48 UTCresolved

   The issue has been resolved.

1. 7 Gwengolo 2023 da 08:24 UTCinvestigating

   We're currently investigating issues with the Float App. We'll update as soon as we know more.

2. 7 Gwengolo 2023 da 09:15 UTCresolved

   A fix has been implemented and the service is back online.

1. 23 Eost 2023 da 20:03 UTCidentified

   We have identified a problem with an upstream provider that is causing requests to fail. We're working on a fix now.

2. 23 Eost 2023 da 20:30 UTCmonitoring

   We've released a fix Float App users will be receiving successful responses now. We will continue to monitor the situation.

3. 23 Eost 2023 da 21:45 UTCresolved

   The issue has been resolved.

1. 21 Eost 2023 da 07:01 UTCidentified

   An issue with an upstream provider is causing problems with Float. Some customers may experience longer loading times and some failed requests.

2. 21 Eost 2023 da 09:24 UTCmonitoring

   Our monitoring is indicating the problem is subsiding, we'll continue to monitor.

3. 21 Eost 2023 da 12:55 UTCresolved

   The issue is resolved.