FloQast Outage History

Started Dec 10, 2025, 11:40 PM UTC· resolved Dec 11, 2025, 12:56 AM UTC

1. investigating Dec 11, 2025, 12:18 AM UTC

   We are currently investigating reports of an issue attaching files to Checklist Items.

2. identified Dec 11, 2025, 12:32 AM UTC

   The cause of the issue attaching files to Checklist Items has been identified. We are currently applying a fix and will update this page as soon as we have confirmed the resolution.

3. resolved Dec 11, 2025, 12:56 AM UTC

   Dec 10, 16:56 PST Resolved - The fix for this issue has been released, and we have confirmed that linking documents to Checklist Items is working as expected. A Root Cause Analysis will be posted here when available. Dec 10, 16:32 PST Identified - The cause of the issue attaching files to Checklist Items has been identified. We are currently applying a fix and will update this page as soon as we have confirmed the resolution. Dec 10, 15:40 PST Investigating - We are currently investigating reports of an issue attaching files to Checklist Items.

4. resolved Dec 11, 2025, 12:56 AM UTC

   The fix for this issue has been released, and we have confirmed that linking documents to Checklist Items is working as expected. A Root Cause Analysis will be posted here when available.

5. postmortem Dec 18, 2025, 09:14 PM UTC

   **Summary:** Customers experienced an inability to upload and link files to Checklist Items within the Close Optimization product. **Root Cause:** The incident was caused by a code regression introduced during a scheduled release designed to optimize system performance. Specific changes intended to improve application responsiveness inadvertently disabled the trigger mechanism required to send files to the backend system. **Immediate Resolution:** The engineering team identified the problematic update and restored proper functionality by reverting the application to the previous stable version. The fix was validated across all production environments to ensure the file upload capability was fully operational. **Follow-up Actions:** To prevent recurrence, the team has implemented new automated end-to-end testing specifically for the file upload workflow to catch similar issues prior to deployment. Additionally, the performance optimization code has been removed from the main codebase for further review and correction before future re-release.

Read the full incident report →

Started Dec 10, 2025, 09:48 PM UTC· resolved Dec 10, 2025, 10:29 PM UTC

1. investigating Dec 10, 2025, 10:14 PM UTC

   We are investigating reports of errors in AI Transaction Matching for customers on our US Database. Errors are being seen when generating new Rules in Matching and when searching for specific transactions.

2. identified Dec 10, 2025, 10:15 PM UTC

   We believe we have identified the cause of these errors in AI Transaction Matching, and are currently working on a fix.

3. monitoring Dec 10, 2025, 10:29 PM UTC

   The fix for this issue has been released, and we have confirmed AI Transaction Matching is fully functional. A Root Cause Analysis will be posted here when available.

4. resolved Dec 10, 2025, 10:29 PM UTC

   Dec 10, 14:29 PST Resolved - This incident has been resolved. Dec 10, 14:29 PST Monitoring - The fix for this issue has been released, and we have confirmed AI Transaction Matching is fully functional. A Root Cause Analysis will be posted here when available. Dec 10, 14:15 PST Identified - We believe we have identified the cause of these errors in AI Transaction Matching, and are currently working on a fix. Dec 10, 13:48 PST Investigating - We are investigating reports of errors in AI Transaction Matching for customers on our US Database. Errors are being seen when generating new Rules in Matching and when searching for specific transactions.

5. resolved Dec 10, 2025, 10:29 PM UTC

   This incident has been resolved.

6. postmortem Dec 18, 2025, 09:12 PM UTC

   **Summary:** Customers using AI Transaction Matching on the US Database experienced issues where searching for transactions and rule generation were temporarily unavailable or failed to function as expected. **Root Cause:** A routine system update intended to improve the user interface resulted in a synchronization mismatch between background services and the application front-end. While the back-end service updates were successfully applied, the corresponding interface update was blocked by a transient network error during the installation of a related component, leaving an incompatible version of the interface active. **Immediate Resolution:** Engineering teams identified the failure and successfully reran the deployment process, ensuring all components were properly synchronized and restoring full functionality to the US region. **Follow-up Actions:** To prevent future occurrences, the team is implementing improvements to decouple service deployments so that a failure in one area does not block unrelated updates. Additionally, new automated monitoring and alerting for deployment failures are being established alongside improved dependency management protocols to ensure system consistency during releases.

Read the full incident report →

Started Dec 03, 2025, 03:45 PM UTC· resolved Dec 04, 2025, 03:45 PM UTC

1. resolved Dec 03, 2025, 04:38 PM UTC

   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.

Read the full incident report →

Started Oct 28, 2025, 01:23 PM UTC· resolved Oct 28, 2025, 07:45 PM UTC

1. investigating Oct 28, 2025, 01:23 PM UTC

   We are investigating issues capturing balances in the per-GL column for entities connected to QBO.

2. monitoring Oct 28, 2025, 03:57 PM UTC

   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.

3. resolved Oct 28, 2025, 07:45 PM UTC

   This incident has been resolved.

4. postmortem Oct 30, 2025, 12:03 AM UTC

   **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.

Read the full incident report →

Started Sep 29, 2025, 07:46 PM UTC· resolved Sep 29, 2025, 08:58 PM UTC

1. investigating Sep 29, 2025, 08:04 PM UTC

   We are currently investigating reports of unexpected errors throughout the app.

2. monitoring Sep 29, 2025, 08:10 PM UTC

   We are now seeing pages load successfully, and are continuing to monitor to ensure continued successful performance.

3. resolved Sep 29, 2025, 08:58 PM UTC

   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.

4. postmortem Oct 13, 2025, 11:32 PM UTC

   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.

Read the full incident report →

Started Sep 15, 2025, 03:46 PM UTC· resolved Sep 15, 2025, 04:20 PM UTC

1. investigating Sep 15, 2025, 04:04 PM UTC

   Customers are currently receiving "We're sorry—something went wrong" error messages when loading the Reconciliations and Folders pages, making those pages unavailable.

2. identified Sep 15, 2025, 04:14 PM UTC

   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.

3. resolved Sep 15, 2025, 04:20 PM UTC

   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.

4. postmortem Oct 15, 2025, 05:00 PM UTC

   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.

Read the full incident report →

Started Sep 12, 2025, 06:46 PM UTC· resolved Sep 12, 2025, 07:03 PM UTC

1. identified Sep 12, 2025, 07:16 PM UTC

   Users are observing "Failed to load UI" error messages and/or experiencing issues loading pages that contain checklist items (Folders tab, Checklist tab)

2. resolved Sep 12, 2025, 07:18 PM UTC

   A breaking change has been reverted, so all pages containing Checklist items should load fully and successfully at this time.

3. postmortem Oct 13, 2025, 11:18 PM UTC

   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.

Read the full incident report →

Started Sep 02, 2025, 11:10 PM UTC· resolved Sep 03, 2025, 12:14 AM UTC

1. investigating Sep 02, 2025, 11:42 PM UTC

   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.

2. identified Sep 02, 2025, 11:46 PM UTC

   We have identified the cause of the issue and are now developing a fix to be deployed shortly.

3. resolved Sep 03, 2025, 12:14 AM UTC

   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.

4. postmortem Sep 05, 2025, 09:49 PM UTC

   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.

Read the full incident report →

Started Aug 26, 2025, 06:04 PM UTC· resolved Aug 26, 2025, 07:44 PM UTC

1. investigating Aug 26, 2025, 06:16 PM UTC

   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.

2. identified Aug 26, 2025, 06:24 PM UTC

   The issue has been identified, and a fix is currently being implemented.

3. monitoring Aug 26, 2025, 06:40 PM UTC

   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.

4. resolved Aug 26, 2025, 07:44 PM UTC

   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.

5. postmortem Aug 27, 2025, 11:15 PM UTC

   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.

Read the full incident report →

Started Aug 12, 2025, 02:29 PM UTC· resolved Aug 12, 2025, 03:15 PM UTC

1. identified Aug 12, 2025, 03:49 PM UTC

   Customers reported issues loading Variance Analysis, receiving errors including "UnexpectedError" or "504 Gateway Time-out" responses, rendering the Variance service temporarily unavailable.

2. resolved Aug 12, 2025, 03:50 PM UTC

   This issue was resolved as of 11:15 EST, and we are continuing to monitor performance.

Read the full incident report →

Started Jul 11, 2025, 10:11 PM UTC· resolved Jul 11, 2025, 11:40 PM UTC

1. investigating Jul 11, 2025, 10:11 PM UTC

   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.

2. monitoring Jul 11, 2025, 10:49 PM UTC

   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.

3. monitoring Jul 11, 2025, 10:49 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Jul 11, 2025, 11:40 PM UTC

   This incident has been resolved. An RCA (Root Cause Analysis) will be made available as well.

5. postmortem Jul 11, 2025, 11:40 PM UTC

   **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.

Read the full incident report →

Started Jul 07, 2025, 03:20 PM UTC· resolved Jul 07, 2025, 05:09 PM UTC

1. investigating Jul 07, 2025, 03:20 PM UTC

   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.

2. investigating Jul 07, 2025, 03:54 PM UTC

   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.

3. investigating Jul 07, 2025, 04:12 PM UTC

   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.

4. monitoring Jul 07, 2025, 04:12 PM UTC

   A fix has been implemented and we are monitoring the results.

5. resolved Jul 07, 2025, 05:09 PM UTC

   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.

6. postmortem Jul 07, 2025, 09:44 PM UTC

   **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.

Read the full incident report →

Started Jun 20, 2025, 06:00 PM UTC· resolved Jun 20, 2025, 06:00 PM UTC

1. resolved Jun 20, 2025, 06:20 PM UTC

   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.

Read the full incident report →

Started Jun 20, 2025, 04:00 PM UTC· resolved Jun 20, 2025, 04:00 PM UTC

1. resolved Jun 20, 2025, 04:16 PM UTC

   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.

Read the full incident report →

Started Apr 08, 2025, 05:07 PM UTC· resolved Apr 08, 2025, 07:41 PM UTC

1. identified Apr 08, 2025, 05:37 PM UTC

   Customers are reporting errors with their automated trial balance deliveries via sFTP. The issue is caused by an updated server hostkey. The hostkey for sftp-v2.floqast.app has not been changed, but an additional hostkey has been added. If your automated upload process recognizes the new hostkey, your connection may fail until the new hostkey has been cached.

2. resolved Apr 09, 2025, 04:38 AM UTC

   Clients utilizing FloQast's SFTP capabilities have been advised to cache the updated hostkey, and there are no further changes anticipated for the production servers across all regions. Once the new hostkey is cached, all connections should succeed as expected and deliveries can be made successfully. If any errors persist with either connectivity or data transfer, please contact [email protected] for further troubleshooting!

Read the full incident report →

Started Mar 20, 2025, 06:15 PM UTC· resolved Mar 20, 2025, 07:21 PM UTC

1. investigating Mar 20, 2025, 06:25 PM UTC

   We are currently investigating reports of users receiving an error immediately upon logging in, then being redirected back to the login page. Engineering is triaging at the highest priority level, and further updates will be posted as soon as they are available.

2. identified Mar 20, 2025, 06:48 PM UTC

   The issue has been identified and impacts only the US region at this time. A fix is currently being deployed to resolve the issue of incorrect URLs rendering for customers and causing immediate logouts. Another update will be posted as soon as the fix is successfully deployed and validated.

3. resolved Mar 20, 2025, 07:21 PM UTC

   The fix has been deployed to Production and US users have validated successful logins and regular navigation throughout the application. If any further errors persist, please reach out to [email protected] for continued assistance!

Read the full incident report →

Started Mar 20, 2025, 04:40 PM UTC· resolved Mar 20, 2025, 05:37 PM UTC

1. investigating Mar 20, 2025, 05:58 PM UTC

   We have been investigating issues capturing balances in the per-GL column for certain ERPs, and Engineering has issued a fix that should resolve the issue for all systems. If any further balance discrepancies are observed after clicking the Refresh button, please contact [email protected] and we'll continue investigating!

2. resolved Mar 20, 2025, 05:58 PM UTC

   The fix has been validated for affected customers, and all Refreshes should be running successfully at this time.

Read the full incident report →

Started Feb 19, 2025, 01:14 AM UTC· resolved Feb 19, 2025, 01:53 AM UTC

1. identified Feb 19, 2025, 01:14 AM UTC

   Some users are currently observing a blank page upon loading various pages within the FloQast application. Engineering is actively working to resolve this issue.

2. resolved Feb 19, 2025, 01:53 AM UTC

   A series of fixes has been deployed and all pages should load fully once again for affected customers.

Read the full incident report →

Started Feb 07, 2025, 11:25 PM UTC· resolved Feb 07, 2025, 11:58 PM UTC

1. identified Feb 07, 2025, 11:25 PM UTC

   Users are currently observing an error immediately upon loading pages within FloQast. The error can be closed out, and all underlying functionality should remain operational! Engineering is actively working to fully resolve the front-end error.

2. resolved Feb 07, 2025, 11:58 PM UTC

   The issue previously causing the "500: Connection was force closed" error has been remediated, and all pages should load properly at this time.

Read the full incident report →

Started Nov 05, 2024, 03:39 PM UTC· resolved Nov 05, 2024, 08:33 PM UTC

1. investigating Nov 05, 2024, 05:48 PM UTC

   Google Drive customers are reporting a reoccurrence of the Google Drive API outage previously observed in late September and early October. Downstream functionality within FloQast is impacted, including the ability to upload/attach documents within FloQast since these actions leverage the Google Drive API and are currently being rejected. The FloQast Engineering team has engaged contacts at Google and is awaiting further updates. As Google works on restoring full API functionality, available workarounds include uploading documents directly within Google Drive folders and then clicking the Refresh button in corresponding FloQast folders, thereby bypassing the "upload" function of the Google Drive API. Only customers leveraging Google MyDrive and Google Share Drive are impacted at this time; customers leveraging other Storage Providers should observe regular functionality.

2. resolved Nov 06, 2024, 07:15 AM UTC

   Google Drive customers are observing successful uploads at this time, and logs indicate that full functionality via the Google Drive API is restored at this time.

Read the full incident report →

Started Nov 01, 2024, 04:46 PM UTC· resolved Nov 01, 2024, 04:56 PM UTC

1. identified Nov 01, 2024, 04:46 PM UTC

   Clients utilizing AutoRec (Matching, AI Matching, Amortization, Depreciation, etc.) may receive an error when clicking on an AutoRec link specifically from the Folders tab. Accessing the same link from the Reconciliations tab should load all AutoRec functionality as expected! FloQast engineering's team is actively working to restore the click-through of the links from the Folders tab.

2. resolved Nov 01, 2024, 04:56 PM UTC

   The issue preventing AutoRec links from loading has been resolved for the Folders tab. At this time, all hyperlinks should properly launch the respective AutoRec modules!

Read the full incident report →

Started Nov 01, 2024, 04:40 PM UTC· resolved Nov 01, 2024, 05:00 PM UTC

1. identified Nov 01, 2024, 04:40 PM UTC

   The "Percent Updated" and "Last Update at..." components are not loading for some Users after clicking the Refresh button on the Folders tab > Reconciliations section. This UI issue is intermittent and only occurs on the Folders tab — the Reconciliations tab should be unaffected at this time. On the Folders tab, only the UI is impacted and data is being successfully refreshed! However, a page reload (i.e. refreshing the browser itself) is necessary to display the refreshed data since the front-end automation is not updating.

2. resolved Nov 01, 2024, 05:00 PM UTC

   The UI issue on the Folders tab has been resolved for users clicking the Refresh button. At this time, components like the "Percent Updated" gif and the "Last Updated" timestamp should be loading as expected!

Read the full incident report →