All Systems Operational
FloQast Application Accessibility Operational
Login Operational
Page Load Operational
FloQast Products Operational
Checklist Operational
Reconciliations Operational
Flux Analysis Operational
AutoRec Matching Operational
AutoRec Amortization Operational
ReMind Operational
Dashboard Operational
Analytics Operational
Folders & Replication Operational
Review Notes Operational
Admin Settings Operational
Notifications: Email, Slack, Teams Operational
Integrations Operational
FloQast Connect: SFTP Server Operational
Netsuite API Operational
Intacct API Operational
QBO API Operational
Business Central API Operational
OneDrive API Operational
Google Drive API Operational
Box API Operational
Dropbox API Operational
Egnyte API Operational
Workiva API Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Feb 19, 2025

No incidents reported today.

Feb 18, 2025
Resolved - A series of fixes has been deployed and all pages should load fully once again for affected customers.
Feb 18, 17:53 PST
Identified - Some users are currently observing a blank page upon loading various pages within the FloQast application. Engineering is actively working to resolve this issue.
Feb 18, 17:14 PST
Feb 17, 2025

No incidents reported.

Feb 16, 2025

No incidents reported.

Feb 15, 2025

No incidents reported.

Feb 14, 2025

No incidents reported.

Feb 13, 2025

No incidents reported.

Feb 12, 2025

No incidents reported.

Feb 11, 2025

No incidents reported.

Feb 10, 2025

No incidents reported.

Feb 9, 2025

No incidents reported.

Feb 8, 2025

No incidents reported.

Feb 7, 2025
Resolved - The issue previously causing the "500: Connection was force closed" error has been remediated, and all pages should load properly at this time.
Feb 7, 15:58 PST
Identified - 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.

Feb 7, 15:25 PST
Feb 6, 2025

No incidents reported.

Feb 5, 2025

No incidents reported.