Outage in FloQast

"Connection was force closed" error upon page load

Resolved Minor
February 07, 2025 - Started about 1 month ago - Lasted about 1 hour
Official incident page

Need to monitor FloQast outages?
Stay on top of outages with IsDown. Monitor the official status pages of all your vendors, SaaS, and tools, including FloQast, and never miss an outage again.
Start Free Trial

Outage Details

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.
Latest Updates ( sorted recent to last )
RESOLVED about 1 month ago - at 02/07/2025 11:58PM

The issue previously causing the "500: Connection was force closed" error has been remediated, and all pages should load properly at this time.

IDENTIFIED about 1 month ago - at 02/07/2025 11:25PM

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.

Don't be the last to know when your dependencies go down

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 3845 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook