Float Outage History

Float is up right now

Float had 8 outages in the last 2 years totaling 50h 8m of downtime — averaging 0.3 incidents per month.

There were 8 Float outages since July 1, 2025 totaling 50h 8m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.float.com

Minor May 14, 2026

Search and filter issues

Detected by Pingoru
May 14, 2026, 08:37 AM UTC
Resolved
May 14, 2026, 07:42 PM UTC
Duration
11h 5m
Affected: Float App
Timeline · 3 updates
  1. investigating May 14, 2026, 08:37 AM UTC

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

  2. monitoring May 14, 2026, 08:48 AM UTC

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

  3. resolved May 14, 2026, 07:42 PM UTC

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

Read the full incident report →

Minor May 14, 2026

Infrastructure provider issues

Detected by Pingoru
May 14, 2026, 07:31 AM UTC
Resolved
May 14, 2026, 03:56 PM UTC
Duration
8h 24m
Affected: Float AppAPI - public
Timeline · 4 updates
  1. investigating May 14, 2026, 07:31 AM UTC

    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. monitoring May 14, 2026, 09:26 AM UTC

    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. monitoring May 14, 2026, 09:26 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved May 14, 2026, 03:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 13, 2026

Search function

Detected by Pingoru
Mar 13, 2026, 01:45 PM UTC
Resolved
Mar 13, 2026, 03:28 PM UTC
Duration
1h 42m
Affected: Float App
Timeline · 3 updates
  1. investigating Mar 13, 2026, 01:45 PM UTC

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

  2. monitoring Mar 13, 2026, 03:06 PM UTC

    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. resolved Mar 13, 2026, 03:28 PM UTC

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

Read the full incident report →

Notice February 6, 2026

Issues with search

Detected by Pingoru
Feb 06, 2026, 07:35 PM UTC
Resolved
Feb 07, 2026, 12:44 AM UTC
Duration
5h 8m
Affected: Float App
Timeline · 3 updates
  1. investigating Feb 06, 2026, 07:35 PM UTC

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

  2. identified Feb 06, 2026, 07:55 PM UTC

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

  3. resolved Feb 07, 2026, 12:44 AM UTC

    The issue is resolved.

Read the full incident report →

Notice December 5, 2025

Float.com site errors

Detected by Pingoru
Dec 05, 2025, 09:17 AM UTC
Resolved
Dec 05, 2025, 09:41 AM UTC
Duration
24m
Affected: www.float.com
Timeline · 3 updates
  1. investigating Dec 05, 2025, 09:17 AM UTC

    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. monitoring Dec 05, 2025, 09:27 AM UTC

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

  3. resolved Dec 05, 2025, 09:41 AM UTC

    The issue with the upstream provider has now been resolved.

Read the full incident report →

Notice October 20, 2025

Issue with Reports and Search

Detected by Pingoru
Oct 20, 2025, 08:11 PM UTC
Resolved
Oct 21, 2025, 01:58 PM UTC
Duration
17h 47m
Affected: Float App
Timeline · 3 updates
  1. investigating Oct 20, 2025, 08:11 PM UTC

    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. monitoring Oct 20, 2025, 10:46 PM UTC

    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. resolved Oct 21, 2025, 01:58 PM UTC

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

Read the full incident report →

Notice July 18, 2025

Issues with our infrastructure provider

Detected by Pingoru
Jul 18, 2025, 04:04 PM UTC
Resolved
Jul 18, 2025, 06:57 PM UTC
Duration
2h 53m
Affected: Float App
Timeline · 2 updates
  1. identified Jul 18, 2025, 04:04 PM UTC

    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. resolved Jul 18, 2025, 06:57 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 1, 2025

Error adding project from Allocations modal.

Detected by Pingoru
Jul 01, 2025, 01:08 AM UTC
Resolved
Jul 01, 2025, 03:50 AM UTC
Duration
2h 42m
Affected: Float App
Timeline · 3 updates
  1. investigating Jul 01, 2025, 01:08 AM UTC

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

  2. monitoring Jul 01, 2025, 02:25 AM UTC

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

  3. resolved Jul 01, 2025, 03:50 AM UTC

    This incident has been resolved.

Read the full incident report →