FloQast incident

Navigation UI Missing

Critical Resolved View vendor source →

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

Started
Jul 07, 2025, 03:20 PM UTC
Resolved
Jul 07, 2025, 05:09 PM UTC
Duration
1h 48m
Detected by Pingoru
Jul 07, 2025, 03:20 PM UTC

Affected components

Platform - US

Update timeline

  1. investigating Jul 07, 2025, 03:20 PM UTC

    The navigation bar is missing within the FloQast application. FloQast is currently aware of this issue and has all available resources working on discovery and resolution.

  2. investigating Jul 07, 2025, 03:54 PM UTC

    FloQast is continuing to investigate this issue. Due to the navigation being missing, large portions of the application are currently inaccessible and cannot be used. This is the company's top priority to resolve.

  3. investigating Jul 07, 2025, 04:12 PM UTC

    We have implemented what we believe to be the resolution to this issue. We are actively monitoring app performance for any indications of remaining issues. Thank you very much for your patience as we looked into and released a fix for this issue.

  4. monitoring Jul 07, 2025, 04:12 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Jul 07, 2025, 05:09 PM UTC

    We have confirmed success from the implemented fix and are now confident in saying the issue is resolved. Thank you for your patience while we worked to remediate this issue.

  6. postmortem Jul 07, 2025, 09:44 PM UTC

    **Created**: 2025-07-07T15:11:03Z **Resolved**: 2025-07-07T16:51:53.125Z **Impact**: The navigation bar was not loading for customers in the US region, resulting in multiple parts of the FloQast application being inaccessible and unusable. **Root Cause** \(Preliminary\): The root cause was identified as a WAF \(Web Application Firewall\) DDOS protection mechanism blocking traffic due to exceeding a rate limit threshold within a designated time period. The IPs being blocked were from an internal API Gateway. **Mitigation**: The issue was mitigated by confirming the source of the IPs and the legitimacy of the traffic, then implementing an appropriate bypass.