Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

FloQast Outage History

Every past FloQast outage tracked by IsDown, with detection times, duration, and resolution details.

There were 89 FloQast outages since November 2016. The 24 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor April 23, 2026

April 2026: Issues Updating Reconciliations via the All Entities Reconciliation Template

Detected Apr 23, 2026 1:21 PM EDT · Resolved Apr 23, 2026 6:19 PM EDT · Duration about 5 hours

FloQast experienced a 5-hour issue where changes made through the All Entities Reconciliation Template were appearing in Admin Settings but failing to sync to the Reconciliations tab. The team deployed a fix that restored proper syncing functionality, and users can re-apply the template if recent changes are not visible.

Major April 7, 2026

April 2026: Reports of "Something Went Wrong" errors being received in various parts of the application.

Detected Apr 7, 2026 3:15 AM EDT · Resolved Apr 7, 2026 12:37 PM EDT · Duration about 9 hours

FloQast experienced a major incident where users encountered "Something Went Wrong" errors across various parts of the application, specifically affecting the Checklist and Reconciliations components. The issue was identified and a fix was implemented after 9.4 hours, with the incident fully resolved following a monitoring period.

Major April 2, 2026

April 2026: 403 Permissions Error Response on sending API Requests to Specific Endpoints

Detected Apr 2, 2026 9:54 AM EDT · Resolved Apr 2, 2026 1:49 PM EDT · Duration about 4 hours

FloQast experienced a major service incident where users received 403 permission errors when making API requests to specific endpoints, including Trial Balance and Chart of Accounts endpoints. The issue prevented users from accessing these critical API functionalities for nearly 4 hours. The incident was resolved after implementing and deploying a fix, with monitoring confirming the restoration of normal API access.

Major March 31, 2026

March 2026: Admin Settings pages not loading

Detected Mar 31, 2026 7:40 PM EDT · Resolved Mar 31, 2026 8:06 PM EDT · Duration 25 minutes

FloQast experienced a major incident where specific admin settings pages failed to load for users. The issue affected administrative functionality across the platform for 25 minutes. The problem was identified and resolved through a fix deployed to all regions, restoring full functionality.

Major March 1, 2026

March 2026: Experiencing TB Folder 500 errors

Detected Mar 1, 2026 11:58 PM EST · Resolved Mar 2, 2026 12:04 AM EST · Duration 6 minutes

A recent core service deployment caused 500 errors preventing users from accessing Trial Balance (TB) upload folders in FloQast. The incident affected the Checklist and Reconciliations components for 6 minutes. The issue was resolved by reverting the problematic deployment.

Minor February 23, 2026

February 2026: 500 error displays when AI generating a rule within Matching.

Detected Feb 23, 2026 10:06 AM EST · Resolved Feb 23, 2026 11:12 AM EST · Duration about 1 hour

FloQast's AI-powered rule generation feature in the Matching product experienced a 500 error that prevented users from creating matching rules across all regional databases (US, EU, AU). The issue was resolved after 1.1 hours by implementing new regional configurations between FloQast and OpenAI to meet updated requirements.

Minor February 20, 2026

February 2026: Possible duplication of Checklist items

Detected Feb 20, 2026 10:54 AM EST · Resolved Feb 23, 2026 11:12 AM EST · Duration 3 days

FloQast experienced an issue where checklist items were erroneously assigned new Template IDs during import via Single-Entity or All-Entities templates, causing duplicate checklist items to appear in relevant periods when templates were applied through Admin Settings. While no sign-off data was lost from original items, users saw apparent duplications as new versions of checklist items were created alongside existing ones. The issue was resolved after 72.3 hours with a fix implemented to prevent further duplicates and correction of already-created duplicate tasks.