FloQast incident

Errors throughout the Application

Critical Resolved View vendor source →

FloQast experienced a critical incident on August 26, 2025 affecting Platform - US, lasting 1h 39m. The incident has been resolved; the full update timeline is below.

Started
Aug 26, 2025, 06:04 PM UTC
Resolved
Aug 26, 2025, 07:44 PM UTC
Duration
1h 39m
Detected by Pingoru
Aug 26, 2025, 06:04 PM UTC

Affected components

Platform - US

Update timeline

  1. investigating Aug 26, 2025, 06:16 PM UTC

    Users are experiencing a Bad Gateway Error when loading pages in the application, making these pages unavailable. Engineering is investigating this with our highest priority.

  2. identified Aug 26, 2025, 06:24 PM UTC

    The issue has been identified, and a fix is currently being implemented.

  3. monitoring Aug 26, 2025, 06:40 PM UTC

    The fix has been released, and pages are now loading successfully again. We are continuing to monitor to ensure successful performance and will post a Root Cause Analysis here when it is available.

  4. resolved Aug 26, 2025, 07:44 PM UTC

    We are continuing to see successful page loads throughout the application, and are now considering this incident resolved. A Root Cause Analysis will be shared here when available.

  5. postmortem Aug 27, 2025, 11:15 PM UTC

    The incident was caused by a software update that introduced a version mismatch, leading to an incompatibility with our production environment. This issue prevented a core part of our application from running correctly, resulting in the "Bad Gateway" errors and making the affected pages unavailable. Our engineering team was able to quickly identify and resolve the problem by reverting the incompatible software changes. To prevent a similar occurrence in the future, we have implemented additional automated alerts and expanded our testing procedures to catch such errors before they can impact our services.