50 Float incidents · Dezember 2018 — official updates, affected components, duration and resolution details.
We are currently experiencing issues with the search and filter function. Our team is actively working on a fix.
We've implemented a fix for the issues reported with the search and filter function. We are actively monitoring performance.
The issue affecting the search and filter has been resolved, and the system is now operating normally.
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.
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.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently experiencing issues with the Search function. Our team is actively working on a fix.
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.
The issue affecting Search has been resolved, and the system is now operating normally.
We're currently investigating issues with our search service. Newly changed items may not be visible in search.
We've identified the issue and we're working to resolve it.
The issue is resolved.
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.
The issue with an upstream provider has been resolved and we're continuing to monitor Float.com.
The issue with the upstream provider has now been resolved.
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.
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.
This incident has been resolved. Reports, search, and integrations are back to normal operation.
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.
This incident has been resolved.
We've observed an issue that teams are unable to add new Projects from the Allocations modal.
We've deployed a fix for adding new Projects from the Allocations modal.
This incident has been resolved.
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.
While there are still issues with our underlying provider we've seen stabilisation for the Float Application. We'll continue to monitor and update.
Issue is resolved.
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.
We've implemented a fix and are now monitoring
This issue has been resolved.
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.
We've identified and released some changes to support previous issues. We'll continue to monitor going forward.
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.
A patch has been issued and we're monitoring.
We are investigating an issue with our cloud provider that is causing problems for customers viewing their schedules.
We've identified the issue and are working to resolve it.
We implemented a fix and can see the problem has stopped. We're monitoring now to check it doesn't re-occur.
This incident has been resolved.
We are experiencing degraded performance from our 3rd party identity provider, causing high latency for SSO authentication.
This incident has been resolved.
An issue with database connectivity has been identified while running a routine deployment. We're working to get Float back up and operational.
We've implemented a failover for our production database and we're seeing healthy requests and responses. We'll continue to monitor the situation.
The issue has been resolved.
We're currently investigating issues with the Float App. We'll update as soon as we know more.
A fix has been implemented and the service is back online.
We have identified a problem with an upstream provider that is causing requests to fail. We're working on a fix now.
We've released a fix Float App users will be receiving successful responses now. We will continue to monitor the situation.
The issue has been resolved.
An issue with an upstream provider is causing problems with Float. Some customers may experience longer loading times and some failed requests.
Our monitoring is indicating the problem is subsiding, we'll continue to monitor.
The issue is resolved.
An issue with an upstream provider is causing problems with Float. Some customers may experience longer loading times and some failed requests.
We are continuing to work on a fix for this issue.
The upstream provider is showing the issue as fixed, we'll continue to monitor for a while until we're satisfied the issue doesn't occur again.
We're marking the issue as resolved. Thank you for your patience.
We're investigating an issue with Reports in the Float App which shows the Reports functionality unavailable right now.
A fix has been implemented and we’re monitoring.
This issue is resolved