To keep Float in great working condition, the engineering team performs regular maintenance that may result in brief periods of downtime.
From time to time, we need to perform maintenance on the various systems and services behind the Float application. These pieces of work tend to be transparent and do not impact customer operations.
Occasionally, customer workflows might be interrupted or affected, which is why we utilize scheduled maintenance. During a scheduled maintenance window, Float will be briefly unavailable.
Notifications
We aim to provide notifications to customers at least 7 days in advance of a maintenance window. The notifications will include a description of the work and a timeframe for when the maintenance will be carried out.
You can visit our status page to see Float’s current status and announcements of upcoming and in-progress maintenance work. You can also subscribe to receive updates on Float's status.
📝Note: If you ever experience trouble accessing/using Float and there is no active incident reported on the status page, please let us know.
Impact on integrations
Integrations are usually unaffected by these types of changes. We plan far ahead for maintenance, and if we do find that integrations might be impacted, we will deliver plans to remediate any problems during maintenance.
It’s unlikely that you will see any impact after the maintenance has been completed.
Maintenance windows
The windows we aim to perform maintenance are as follows:
Service | Period | Day | Time |
Float Application, API, and other services | Quarterly | First Saturday | 6:00 a.m. - 7:00 a.m. (UTC) |
Float Databases | N/A | Saturdays and Sundays | 5:00 a.m. - 6:00 a.m. (UTC) |