Float Outage History
15 incidents recorded over the last 365 days, 7 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Float Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 21, 2026 | Security Maintenance – Infrastructure Component UpdateOn October 21, 2026, a security vulnerability was publicly disclosed in a popular open-source software component used across the industry, including in parts of our web infrastructure. Upon disclosure, our engineering… | 0 min | Resolved |
| Oct 8, 2026 | Float App inaccessible for some peopleBetween approximately 14:30 and 15:00 UTC on 8 October 2026, some customers were unable to reach Float. We have identified the cause as a routine network configuration update, which resulted in unexpected, isolated… | 0 min | Resolved |
| May 30, 2026 | Routine Database MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| May 14, 2026 | Search and filter issuesThe issue affecting the search and filter has been resolved, and the system is now operating normally. | 11h 5m | Resolved |
| May 14, 2026 | Infrastructure provider issuesThis incident has been resolved. | 8h 24m | Resolved |
| Mar 28, 2026 | Scheduled Database MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Mar 22, 2026 | Scheduled Database MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Mar 13, 2026 | Search functionThe issue affecting Search has been resolved, and the system is now operating normally. | 1h 42m | Resolved |
| Feb 25, 2026 | Infrastructure maintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Feb 6, 2026 | Issues with searchThe issue is resolved. | 5h 8m | Resolved |
| Jan 24, 2026 | Database MaintenanceThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Jan 19, 2026 | Infrastructure maintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Dec 5, 2025 | Float.com site errorsThe issue with the upstream provider has now been resolved. | 24 min | Resolved |
| Nov 15, 2025 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Nov 8, 2025 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Float incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Float Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Float acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Float outage in this window ran 11h 5m, against a mean recovery of 2h 39m. If you depend on Float in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.