История сбоев Float

1. 21 октября 2026 г. в 19:35 UTCresolved

   21 октября 2026 года уязвимость безопасности была публично раскрыта в популярном программном компоненте с открытым исходным кодом, используемом в отрасли, в том числе в части нашей веб-инфраструктуры. После раскрытия информации наша команда инженеров быстро оценила потенциальное влияние на услуги Float, внедрила временные защитные меры и развернула выпущенные поставщиком обновления безопасности во всех затронутых системах. Все обновления были применены без перерыва в обслуживании. Наше расследование не обнаружило никаких доказательств того, что эта уязвимость была использована против Float или что какие-либо данные клиентов были затронуты. Мы продолжаем следить за окружающей средой в рамках нашей стандартной практики безопасности. Никаких действий от клиентов не требуется. Если у вас есть вопросы, пожалуйста, свяжитесь с нашей службой поддержки. Обновление — 22 октября 2026 года: Для справки, этот инцидент касался двух связанных уязвимостей во время выполнения PHP, CVE-2026-109618 и CVE-2026-109619, в совокупности известных как «PHP2Shell»

Автоматический перевод официального обновления инцидента.

1. 9 октября 2026 г. в 08:34 UTCresolved

   Между 14:30 и 15:00 8 октября 2026 года некоторые клиенты не смогли добраться до Float. Мы определили причину как обычное обновление конфигурации сети, которое привело к неожиданным, изолированным проблемам доступности. Проблема была решена, и мы работаем с нашим поставщиком, чтобы это не повторилось.

Автоматический перевод официального обновления инцидента.

1. 14 мая 2026 г. в 08:37 UTCinvestigating

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

2. 14 мая 2026 г. в 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 мая 2026 г. в 19:42 UTCresolved

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

1. 14 мая 2026 г. в 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 мая 2026 г. в 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 мая 2026 г. в 09:26 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 14 мая 2026 г. в 15:56 UTCresolved

   This incident has been resolved.

1. 13 марта 2026 г. в 13:45 UTCinvestigating

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

2. 13 марта 2026 г. в 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 марта 2026 г. в 15:28 UTCresolved

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

1. 6 февраля 2026 г. в 19:35 UTCinvestigating

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

2. 6 февраля 2026 г. в 19:55 UTCidentified

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

3. 7 февраля 2026 г. в 00:44 UTCresolved

   The issue is resolved.

1. 5 декабря 2025 г. в 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 декабря 2025 г. в 09:27 UTCmonitoring

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

3. 5 декабря 2025 г. в 09:41 UTCresolved

   The issue with the upstream provider has now been resolved.

1. 20 октября 2025 г. в 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 октября 2025 г. в 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 октября 2025 г. в 13:58 UTCresolved

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

1. 18 июля 2025 г. в 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 июля 2025 г. в 18:57 UTCresolved

   This incident has been resolved.

1. 1 июля 2025 г. в 01:08 UTCinvestigating

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

2. 1 июля 2025 г. в 02:25 UTCmonitoring

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

3. 1 июля 2025 г. в 03:50 UTCresolved

   This incident has been resolved.

1. 12 июня 2025 г. в 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 июня 2025 г. в 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 июня 2025 г. в 23:10 UTCresolved

   Issue is resolved.

1. 27 февраля 2025 г. в 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 февраля 2025 г. в 12:42 UTCmonitoring

   We've implemented a fix and are now monitoring

3. 27 февраля 2025 г. в 12:59 UTCresolved

   This issue has been resolved.

1. 22 января 2025 г. в 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 января 2025 г. в 15:51 UTCresolved

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

1. 9 июля 2024 г. в 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 июля 2024 г. в 09:22 UTCresolved

   A patch has been issued and we're monitoring.

1. 7 марта 2024 г. в 21:03 UTCinvestigating

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

2. 7 марта 2024 г. в 21:23 UTCidentified

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

3. 7 марта 2024 г. в 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 марта 2024 г. в 22:00 UTCresolved

   This incident has been resolved.

1. 5 марта 2024 г. в 16:08 UTCinvestigating

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

2. 5 марта 2024 г. в 17:03 UTCresolved

   This incident has been resolved.

1. 30 января 2024 г. в 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 января 2024 г. в 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 января 2024 г. в 13:48 UTCresolved

   The issue has been resolved.

1. 7 сентября 2023 г. в 08:24 UTCinvestigating

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

2. 7 сентября 2023 г. в 09:15 UTCresolved

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

1. 23 августа 2023 г. в 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 августа 2023 г. в 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 августа 2023 г. в 21:45 UTCresolved

   The issue has been resolved.

1. 21 августа 2023 г. в 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 августа 2023 г. в 09:24 UTCmonitoring

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

3. 21 августа 2023 г. в 12:55 UTCresolved

   The issue is resolved.