FloQast Outage History

FloQast is up right now

FloQast had 50 outages in the last 2 years totaling 180h 4m of downtime — averaging 2.1 incidents per month.

There were 50 FloQast outages since August 13, 2024 totaling 180h 4m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.floqast.com

Major June 2, 2026

Egnyte Connection Errors

Detected by Pingoru
Jun 02, 2026, 03:46 PM UTC
Resolved
Jun 02, 2026, 05:48 PM UTC
Duration
2h 2m
Affected: Egnyte API
Timeline · 3 updates
  1. investigating Jun 02, 2026, 03:46 PM UTC

    We are currently investigating reports of errors when refreshing reconciliations and uploading files for customers using our Egnyte integration.

  2. identified Jun 02, 2026, 04:09 PM UTC

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

  3. resolved Jun 02, 2026, 05:48 PM UTC

    We have released a fix for this issue, and customers using Egnyte should no longer be experiencing these errors. We are continuing to monitor to ensure stability, and a Root Cause Analysis will be shared here when available.

Read the full incident report →

Minor May 7, 2026

Review Note notifications are not being received for US clients.

Detected by Pingoru
May 07, 2026, 11:20 PM UTC
Resolved
May 08, 2026, 12:58 AM UTC
Duration
1h 37m
Affected: Optimize the Close - US
Timeline · 2 updates
  1. investigating May 07, 2026, 11:20 PM UTC

    We are currently investigating reports of notifications tied to Review Notes not being received

  2. resolved May 08, 2026, 12:58 AM UTC

    The fix for this issue has been released. Users may experience a brief delay as the backlog of queued notifications is processed. We are continuing to monitor the situation and will share a Root Cause Analysis here when available.

Read the full incident report →

Minor May 1, 2026

Errors Navigating to Reconciliations from the Dashboard

Detected by Pingoru
May 01, 2026, 05:57 PM UTC
Resolved
May 01, 2026, 07:18 PM UTC
Duration
1h 21m
Affected: Optimize the Close - EMEAOptimize the Close - APACOptimize the Close - US
Timeline · 3 updates
  1. investigating May 01, 2026, 05:57 PM UTC

    We are investigating reports of an error when opening reconciliations from the Dashboard's Timeline view. In the meantime, reconciliations can be accessed directly via the Reconciliations and Folders tabs.

  2. identified May 01, 2026, 06:14 PM UTC

    We have identified the cause of the issue and are working on a fix.

  3. resolved May 01, 2026, 07:18 PM UTC

    A fix has been deployed, and reconciliations can now be opened from the Dashboard Timeline view without error. Thank you for your patience while our team investigated. A Root Cause Analysis will be shared here when available.

Read the full incident report →

Major February 23, 2026

Experiencing TB Folder 500 errors

Detected by Pingoru
Feb 23, 2026, 09:00 PM UTC
Resolved
Feb 24, 2026, 12:00 AM UTC
Duration
2h 59m
Affected: Optimize the Close - EMEAOptimize the Close - APACOptimize the Close - USAutomate the Close - EMEAAutomate the Close - APACAutomate the Close - US
Timeline · 2 updates
  1. investigating Mar 02, 2026, 04:58 AM UTC

    Summary: Recent deployment of a core service caused a cascading 500 error when users attempted to access TB (Trial Balance) upload folders. The error originated from a failed HTTP request with status code 500.

  2. resolved Mar 02, 2026, 05:00 AM UTC

    Resolution: Reverting the recent deployment fixed the issue.

Read the full incident report →

Minor February 23, 2026

500 error displays when AI generating a rule within Matching.

Detected by Pingoru
Feb 23, 2026, 03:06 PM UTC
Resolved
Feb 23, 2026, 03:42 PM UTC
Duration
36m
Affected: Automate the Close - EMEAAutomate the Close - APACAutomate the Close - US
Timeline · 2 updates
  1. investigating Feb 23, 2026, 03:06 PM UTC

    We are currently looking into an issue where a 500 error displays when using the AI creation method to generate a rule within the Matching product.

  2. resolved Feb 23, 2026, 04:09 PM UTC

    This issue has been resolved after a newly introduced configuration requirement was made between FloQast and OpenAI. New regional configurations are now in place, and our team has validated that matching rules can be created in all three FloQast regional databases again (US, EU, AU).

Read the full incident report →

Minor February 20, 2026

Possible duplication of Checklist items

Detected by Pingoru
Feb 20, 2026, 03:54 PM UTC
Resolved
Feb 20, 2026, 08:30 PM UTC
Duration
4h 36m
Affected: Optimize the Close - EMEAOptimize the Close - APACOptimize the Close - US
Timeline · 4 updates
  1. investigating Feb 20, 2026, 03:54 PM UTC

    We have identified an issue where Checklist items are erroneously assigned a new Template ID when imported via the Single-Entity or All-Entities template. When an impacted template is applied via the Admin Settings > Checklist page, the updated Template ID causes a brand-new version of the checklist item to be created in the relevant periods. For items that have been fully signed off in those periods, absolutely no sign-off data is lost on the original item, but it will appear that the item has "duplicated" since this net-new version has also been added.

  2. identified Feb 20, 2026, 07:04 PM UTC

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

  3. monitoring Feb 20, 2026, 07:30 PM UTC

    A fix for this issue has been implemented, preventing additional erroneous duplicate tasks from being created. Work is ongoing to correct the tasks that have already been created.

  4. resolved Feb 23, 2026, 04:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 12, 2026

EMEA and APAC - Error message displays when clicking on a review note in the Checklist module.

Detected by Pingoru
Feb 12, 2026, 01:57 PM UTC
Resolved
Feb 12, 2026, 03:20 PM UTC
Duration
1h 23m
Affected: Optimize the Close - EMEAOptimize the Close - APAC
Timeline · 4 updates
  1. investigating Feb 12, 2026, 01:57 PM UTC

    We are currently investigating an issue for our EMEA and APAC customers where an error message displays when clicking on a review note.

  2. identified Feb 12, 2026, 02:51 PM UTC

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

  3. monitoring Feb 12, 2026, 02:54 PM UTC

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

  4. resolved Feb 12, 2026, 03:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 11, 2026

Journal Entry Management Module 500 Errors

Detected by Pingoru
Feb 11, 2026, 09:38 PM UTC
Resolved
Feb 11, 2026, 10:07 PM UTC
Duration
28m
Affected: Automate the Close - EMEAAutomate the Close - APACAutomate the Close - US
Timeline · 2 updates
  1. identified Feb 11, 2026, 09:38 PM UTC

    We have received reports of intermittent 500 errors, specifically in the Journal Entry Management module. We have identified the issue and are actively working on releasing the fix.

  2. resolved Feb 11, 2026, 10:07 PM UTC

    A fix has been implemented, and the issue is confirmed resolved.

Read the full incident report →

Critical December 19, 2025

Audit Log Event Capture

Detected by Pingoru
Dec 19, 2025, 10:15 PM UTC
Resolved
Dec 19, 2025, 10:15 PM UTC
Duration
—
Timeline · 2 updates
  1. resolved Mar 30, 2026, 09:15 PM UTC

    Certain audit log events are not appearing within the audit log export during an impacted period.

  2. postmortem Mar 30, 2026, 09:16 PM UTC

    **Summary:** Certain audit log events were not visible within the platform during the impacted period. **Root Cause:** A code change intended to reduce duplicate backend log entries introduced a gap in event capture due to an unaddressed dependency in the release process. As a result, some audit log events were not properly recorded or displayed. **Immediate Resolution:**The code change was reverted to restore audit log functionality. Engineering identified the affected time window, recovered available audit log data, and restored visibility of impacted events. **Follow-up Actions:** The team reviewed and reinforced software development lifecycle \(SDLC\) processes, including validation of dependencies during testing and deployment. Additional controls have been implemented to ensure completeness and reliability of audit log capture going forward.

Read the full incident report →