FloQast Outage History

28 incidents recorded over the last 365 days, 28 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live FloQast status100.00% uptime history

Every Recorded FloQast Incident

FloQast incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 3, 2026Users unable to sign in with SSO on the APAC DatabaseThis incident has been resolved.35 minResolved
Oct 15, 2026Some customers unable to log in via SSO**Summary:** Between approximately 19:45 and 22:10 UTC on October 15, 2026, customers signing in through single sign-on \(SSO\) with certain identity providers were unable to log in to FloQast, with some sign-in…1h 28mResolved
Jun 2, 2026Egnyte Connection ErrorsWe 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…2h 2mResolved
May 19, 2026Something Went Wrong Errors**Summary:** On May 19, 2026, some customers on our US database experienced "Something Went Wrong" errors when attempting to access the FloQast platform. Affected customers were able to restore access by clearing their…23h 23mResolved
May 18, 2026FloQast Connect SFTP: Trial Balance Upload Failures (APAC)**Summary:** Between 10:23 AM PT on May 15, 2026, and 4:50 PM PT on May 18, 2026, customers on the APAC database were unable to upload Trial Balance and Chart of Accounts files via the FloQast Connect SFTP…51 minResolved
May 12, 2026Request Agent Dashboard and Evidence Request Load Failures**Summary:** On May 12, 2026, between 10:46 AM PT and approximately 1:15 PT, the Request Agent feature was unavailable. Functionality was restored for customers on our US database at approximately 1:15 PT, for customers…1h 45mResolved
May 11, 2026"Something Went Wrong" errors attempting to access FloQast**Summary:** On May 11, 2026, between 3:08 PM and 3:48 PM PT, all customers using the US production environment were unable to log in or access the application. Customers on the EU and APAC databases were not…59 minResolved
May 8, 2026AutoRec Matching: Transaction Import and NetSuite Sync Disruption**Summary:** Beginning at approximately 12:50 PM PT on May 7th, customers using the AutoRec Matching module were unable to upload transaction files or sync data from NetSuite. Uploads failed without clear error…5h 23mResolved
May 7, 2026Review Note notifications are not being received for US clients.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…1h 37mResolved
May 7, 2026Lambda Errors and Runtime Errors Experienced Throughout the Application**Summary:** On May 7, 2026, from approximately 07:15 AM to 05:21 PM PT, customers across all regions experienced failures in automated workflows and email notifications within FloQast, resulting in jobs failing to…8h 49mResolved
May 5, 2026Errors Navigating the Single Workflow Dashboard**Summary:** On May 5, 2026, customers navigating between tabs on the Single Workflow Dashboard encountered an error modal displaying "Something Went Wrong." While the underlying dashboard data continued to load…4h 10mResolved
Apr 20, 2026Issues Updating Reconciliations via the All Entities Reconciliation Template**Summary:** Customers using Reconciliations experienced an issue where changes made via the All Entities template were saved in settings but failed to apply to individual periods. This resulted in template updates not…72h 49mResolved
Apr 7, 2026We are receiving reports of file processing failures when files are provided via sFTP**Summary:** Clients experienced failures when attempting to push files through FloQast's SFTP integration. Automated file processing was interrupted across all production regions. **Root Cause:** A recent update to…18h 54mResolved
Apr 7, 2026Reports of "Something Went Wrong" errors being received in various parts of the application.**Summary:** Clients experienced “Something Went Wrong” errors throughout certain parts of the application. **Root Cause:** As part of ongoing security infrastructure improvements, FloQast migrated services to a more…9h 19mResolved
Apr 2, 2026403 Permissions Error Response on sending API Requests to Specific Endpoints**Summary:** Clients experienced authorization errors \(403s\) when attempting to push data through FloQast's external API integration pipeline. **Root Cause:** As part of ongoing security infrastructure improvements…3h 52mResolved
Mar 31, 2026Admin Settings pages not loading**Summary:** Clients experienced failures when attempting to load most Admin pages within the application. The Team page remained accessible, but all other Admin pages were unavailable during the incident window, which…21 minResolved
Feb 23, 2026Experiencing TB Folder 500 errorsResolution: Reverting the recent deployment fixed the issue.2h 59mResolved
Feb 23, 2026500 error displays when AI generating a rule within Matching.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…36 minResolved
Feb 20, 2026Possible duplication of Checklist itemsThis incident has been resolved.4h 36mResolved
Feb 12, 2026EMEA and APAC - Error message displays when clicking on a review note in the Checklist module.This incident has been resolved.1h 23mResolved
Feb 11, 2026Journal Entry Management Module 500 ErrorsA fix has been implemented, and the issue is confirmed resolved.28 minResolved
Feb 10, 2026Transform AI Agents Unavailable**Summary:** Clients experienced failures when attempting to load the Transform module, receiving an error indicating that their user identity or team membership could not be validated. The issue affected all users…36 minResolved
Jan 29, 2026Issues Accessing AutoRec and AI Matching via the Folders tab**Summary:** Clients experienced navigation failures and error messages when attempting to access AI Matching, AutoRec Matching, AutoRec Amortization, and AutoRec Depreciation through the Folders page. Impacted users…6h 3mResolved
Jan 16, 2026Quickbooks Online Integration Refreshes Failing To Complete**Summary:** Customers experienced an interruption in service where QuickBooks Online \(QBO\) entities failed to refresh, preventing accurate data synchronization and resulting in failure to retrieve balances…6h 22mResolved
Dec 19, 2025Audit Log Event Capture**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…0 minResolved
Dec 10, 2025Issues Linking Documents to Checklist Items**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…1h 15mResolved
Dec 10, 2025Errors in AI Transaction Matching**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…41 minResolved
Dec 3, 2025Trial Balance Upload Failures via sFTPA 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…0 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next FloQast incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This FloQast Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before FloQast acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single FloQast outage in this window ran 3d, against a mean recovery of 6h 28m. If you depend on FloQast in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.