FloQast had 37 outages in the last 2 years totaling 15h 12m of downtime — averaging 1.5 incidents per month.
There were 37 FloQast outages since June 20, 2025 totaling 15h 12m of downtime. Each is summarised below — incident details, duration, and resolution information.
A release to improve security was deployed, which had the unintended consequence of overrestricting the ability to write Trial Balance files to cloud storage folders. As a result of this, trial balances sent via sFTP for environments with specific configurations failed to upload successfully between 7:30pm EST 12/2, and 10:45am EST 12/3.
We are investigating issues capturing balances in the per-GL column for entities connected to QBO.
The source of the GL balances from Quickbooks Online failing to pull in has been identified and resolved. We are actively monitoring to ensure that the issue is fully mitigated.
This incident has been resolved.
**Summary:** Customers who have integrated their QuickBooks Online instance with FloQast began to see their Per GL balances in the Close module fail to correctly reflect balances from QuickBooks Online, and instead showed a zero balance. **Root Cause:** A monthly limitation of available API request credits was exceeded, and this resulted in all requests made to QuickBooks Online being rejected. The rejected requests caused a failure to obtain correct balance data, ultimately ending in the zero balance being displayed for reconciliations. **Immediate Resolution:** Proper functionality was restored by working to increase the available API request credits allocated from QuickBooks Online, allowing for the requests to return accurate data once again. **Follow-up Actions:** Additional monitoring will be put in place to more specifically measure third-party request quota limitations and usage, alerting FloQast in advanced of any potential conflicts.
We are currently investigating reports of unexpected errors throughout the app.
We are now seeing pages load successfully, and are continuing to monitor to ensure continued successful performance.
Service has been fully restored. Our engineering team is now conducting a full root cause analysis to prevent a recurrence of this issue. We will post the RCA here once it is complete.
This issue was caused by a brief delay in our traffic auto-scaling system, which led to temporary errors for some users. The underlying settings were quickly refined, resulting in an immediate restoration of services and ensuring resources are properly deployed without disrupting any additional services.
Customers are currently receiving "We're sorry—something went wrong" error messages when loading the Reconciliations and Folders pages, making those pages unavailable.
The cause of the errors has been identified, and we are working on a fix. We can also confirm that this outage is only impacting customers on our US Database; the EU and APAC databases are not affected.
We have released the fix for this issue, and the Folders and Reconciliations pages are now loading successfully. We are continuing to monitor to ensure successful performance, and a root cause analysis will be posted here once it is available.
The disruption was caused by a version incompatibility between a few different components of the application. Certain parts of the application were upgraded to a newer framework version before other related parts of the application, and this resulted in the separate parts of the application not communicating correctly with each other, manifesting in the errors experienced in the application front end. This was resolved by creating version parity again and introducing additional guardrails to the version release process to prevent this from occurring again in the future.
Users are observing "Failed to load UI" error messages and/or experiencing issues loading pages that contain checklist items (Folders tab, Checklist tab)
A breaking change has been reverted, so all pages containing Checklist items should load fully and successfully at this time.
The errors received when loading the checklist pages were caused by a delayed code release, resulting in a software incompatibility between two portions of the application. This versioning incompatibility caused the page load errors to display when interacting with the Checklist page.
We are currently investigating an issue causing error messages when attempting to access the Reconciliations page within the Admin Settings. As a temporary workaround, reconciliations can be edited via Inline Editing.
We have identified the cause of the issue and are now developing a fix to be deployed shortly.
We have released a fix for this issue, and the Reconciliations Settings page is now loading again. We are continuing to monitor for any further issues and will post a root cause analysis here once it becomes available.
A recent release was deployed to improve performance on the Reconciliation Settings page by deprecating legacy routes. However, this release inadvertently introduced an error caused by an undeclared variable, which prevented the page from loading. Our engineers reverted the change to immediately restore functionality. The underlying issue has been addressed, and the intended improvements will be redeployed following a complete testing cycle.
Users are experiencing a Bad Gateway Error when loading pages in the application, making these pages unavailable. Engineering is investigating this with our highest priority.
The issue has been identified, and a fix is currently being implemented.
The fix has been released, and pages are now loading successfully again. We are continuing to monitor to ensure successful performance and will post a Root Cause Analysis here when it is available.
We are continuing to see successful page loads throughout the application, and are now considering this incident resolved. A Root Cause Analysis will be shared here when available.
The incident was caused by a software update that introduced a version mismatch, leading to an incompatibility with our production environment. This issue prevented a core part of our application from running correctly, resulting in the "Bad Gateway" errors and making the affected pages unavailable. Our engineering team was able to quickly identify and resolve the problem by reverting the incompatible software changes. To prevent a similar occurrence in the future, we have implemented additional automated alerts and expanded our testing procedures to catch such errors before they can impact our services.
Customers reported issues loading Variance Analysis, receiving errors including "UnexpectedError" or "504 Gateway Time-out" responses, rendering the Variance service temporarily unavailable.
This issue was resolved as of 11:15 EST, and we are continuing to monitor performance.
We are currently investigating an issue causing the Folders page to fail to load. This is being given highest priority and updates will be shared as soon as we have them. Thank you for your patience while we're working on getting this resolved.
The issue has been identified, and the fix has been implemented. We are actively monitoring for any unexpected behavior, but we expect the application to be functioning properly again. Thank you again for your patience while we investigated and resolved this issue.
We are continuing to monitor for any further issues.
This incident has been resolved. An RCA (Root Cause Analysis) will be made available as well.
**Created**: 2025-07-11 3:30 PM PST **Resolved**: 2025-07-11 3:51 PM PST **Impact**: FloQast users were unable to access the Folders tab of the application due to receiving an error message upon page load after selecting the Folders tab **Root Cause** **\(Preliminary\)**: The root cause was identified to be an implementation of a new infrastructure upgrade that was not successfully completed, causing a missing property to be passed with a Folders payload. **Mitigation**: The issue was mitigated by reversing the attempted infrastructure upgrade and restoring the previous version.
The navigation bar is missing within the FloQast application. FloQast is currently aware of this issue and has all available resources working on discovery and resolution.
FloQast is continuing to investigate this issue. Due to the navigation being missing, large portions of the application are currently inaccessible and cannot be used. This is the company's top priority to resolve.
We have implemented what we believe to be the resolution to this issue. We are actively monitoring app performance for any indications of remaining issues. Thank you very much for your patience as we looked into and released a fix for this issue.
A fix has been implemented and we are monitoring the results.
We have confirmed success from the implemented fix and are now confident in saying the issue is resolved. Thank you for your patience while we worked to remediate this issue.
**Created**: 2025-07-07T15:11:03Z **Resolved**: 2025-07-07T16:51:53.125Z **Impact**: The navigation bar was not loading for customers in the US region, resulting in multiple parts of the FloQast application being inaccessible and unusable. **Root Cause** \(Preliminary\): The root cause was identified as a WAF \(Web Application Firewall\) DDOS protection mechanism blocking traffic due to exceeding a rate limit threshold within a designated time period. The IPs being blocked were from an internal API Gateway. **Mitigation**: The issue was mitigated by confirming the source of the IPs and the legitimacy of the traffic, then implementing an appropriate bypass.
We experienced an issue with email notifications not sending correctly. Notifications affected included One-Time Verification Code, Password Resets, and Invite Links. This has now been resolved. Customers may observe multiple notifications at once as a backlog of notifications is processed.
Various parts of the FloQast application experienced degraded performance today. Known impacted products included: - AI Matching - Variance Analysis This issue has since been resolved, and the application should be performing as expected now.