FloQast logo

Is FloQast Down?

SaaSLive status, outages, and incident history

No. FloQast is up right now.

Every monitored FloQast system is operational as of August 11, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 43m agoLive, rechecked every 60s
How we know: the official FloQast status page, PulsAPI's own check every 60 seconds, and outage reports from engineers. How PulsAPI monitoring works

FloQast Component Status

The main FloQast systems on this page. All 20 are operational right now.

20operational
APAC » Automate the Close - APAC
Operational
APAC » Connected Compliance - APAC
Operational
APAC » Integrated Record-to-Report - APAC
Operational

17 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking APAC » Optimize the Close - APAC, APAC » Platform - APAC, APAC » Transform AI Agents - APAC, EMEA » Automate the Close - EMEA, EMEA » Connected Compliance - EMEA, EMEA » Integrated Record-to-Report - EMEA, EMEA » Optimize the Close - EMEA, EMEA » Platform - EMEA, EMEA » Transform AI Agents - EMEA, Integrations » Box API, Integrations » Business Central API, Integrations » Dropbox API, and 5 more.

Create a free account

Component statuses may change independently during partial outages.

Recent FloQast Outages & Incidents

Incident history from the official FloQast status page, including resolution updates.

Uptime history4 days observed
Aug 8100.00% averageAug 11
Egnyte Connection ErrorsResolved Jun 2, 2026 · 2h 2mResolved

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. --- [2026-06-02T09:09:25.463-07:00] (identified) The issue has been identified and a fix is being implemented. --- [2026-06-02T08:48:51.140-07:00] (investigating) We are currently investigating reports of errors when refreshing reconciliations and uploading files for customers using our Egnyte integration.

Something Went Wrong ErrorsResolved May 19, 2026 · 23h 23mResolved

**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 browser cache. The issue was fully resolved on May 20. **Root Cause:** A recent update to how the platform routes login and authentication requests introduced a misconfiguration in the network path. Under the new routing, certain browser security checks received an unexpected redirect response, which browsers are required to reject per web standards. Once a browser encountered this error, it cached the failure, meaning subsequent requests by the same user continued to fail until the browser cache was cleared. **Immediate Resolution:** The network routing configuration was corrected so that authentication requests reach the intended destination without triggering the redirect. The fix prevents recurrence of the caching problem going forward. **Follow-up Actions:** Additional controls are being put in place to allow the team to respond more quickly to issues with future rollouts, limiting customer impact while investigations are underway. The production deployment pipeline is also being strengthened with additional safeguards to ensure rollback procedures work as expected when needed. --- [2026-05-20T12:42:20.881-07:00] (resolved) A fix has been released for this issue, and customers should no longer receive these "Something Went Wrong" errors. If you continue to receive the error, refreshing your browser will resolve it. We will continue to monitor, and a Root Cause Analysis will be posted here once available. --- [2026-05-19T13:31:58.293-07:00] (identified) We have identified the cause of the issue and are working on a fix. --- [2026-05-19T13:18:26.425-07:00] (investigating) We are currently investigating reports of "Something Went Wrong" errors when loading pages in the application. For any affected customers, clearing your web browser's cache should allow you to access the application while our engineers address the underlying issue.

FloQast Connect SFTP: Trial Balance Upload Failures (APAC)Resolved May 18, 2026 · 51 minResolved

**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 server. **Root Cause:** A software update to an internal file-processing component introduced a new configuration requirement that had not been applied to the APAC database environment. As a result, the service was unable to construct the correct address for its internal file handling system, causing all upload attempts to fail. **Immediate Resolution:** The missing configuration was identified and applied to the affected environment, restoring normal upload functionality. Successful file transfers were confirmed shortly thereafter. **Follow-up Actions:** The team is conducting a broader audit to ensure configuration standards are consistently applied across all service environments and databases. Additional safeguards are being added to the deployment process so that configuration requirements introduced by software updates are validated across all affected services before they reach production. --- [2026-05-18T16:47:07.617-07:00] (resolved) We have released a fix for this issue, and Trial Balances uploaded via the FloQast Connect SFTP server are now being successfully processed again. We will continue to monitor and will share a Root Cause Analysis here when it is available. --- [2026-05-18T15:56:01.356-07:00] (investigating) We are currently investigating reports of Trial Balance files not being successfully processed after being sent via the FloQast Connect SFTP server for customers on our APAC database.

Live FloQast Outage Reports

Problems reported by engineers using FloQast. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No FloQast problems reported yet.

Something wrong with FloQast on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About FloQast

FloQast publishes a public status page at status.floqast.com covering 37 components, including FloQast Connect: SFTP Server, Optimize the Close - EMEA and Optimize the Close - APAC. PulsAPI tracks FloQast outages, degraded performance and incident history in real time, alongside the rest of your SaaS stack.

Over the past 30 days, PulsAPI has measured FloQast uptime at 100.00%. Response times, incident history, and SLA tracking for FloQast are available on the PulsAPI dashboard.

FloQast Status FAQ

Is FloQast down right now?

PulsAPI checks FloQast every 60 seconds. The verdict at the top of this page comes from the latest poll of the official FloQast status feed and refreshes automatically, so you are not looking at a stale cached answer.

What should I do if FloQast is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until FloQast recovers.

How do I check FloQast uptime history?

PulsAPI tracks FloQast uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. A free PulsAPI account unlocks the full 90-day SLA history and incident timeline for FloQast.

How fast does PulsAPI detect FloQast outages?

PulsAPI polls the official FloQast status page every 60 seconds and usually delivers alerts to Slack, Discord, Microsoft Teams, PagerDuty, or email in under 4 seconds after detection. That is often faster than someone on your team notices on their own.

Does PulsAPI track individual FloQast components?

Yes. PulsAPI monitors 20 individual FloQast components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when FloQast goes down?

Yes. Create a PulsAPI account and subscribe to FloQast. Email alerts are included on the free Starter plan. Paid plans add Slack, Discord, Microsoft Teams, PagerDuty, and webhooks whenever FloQast status changes.

How do I report an issue with FloQast to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot FloQast problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor FloQast?

Yes. PulsAPI's Starter plan includes up to 10 monitored services with email alerts, and the 30-day free trial requires no credit card. You can monitor FloQast alongside up to 9 other services at pulsapi.com/signup.

Track FloQast with the rest of your stack

Monitor 2461+ cloud services from one dashboard and get alerts when FloQast status changes.

Start free trial