"Something Went Wrong" errors attempting to access FloQast

Update timeline

1. investigating May 11, 2026, 10:27 PM UTC

   We are aware of an issue causing an "Something Went Wrong" error for users attempting to access FloQast. Users may be unable to load the application or see an unexpected error on login. Our engineering team has been alerted and is actively investigating.

2. investigating May 11, 2026, 10:31 PM UTC

   We are continuing to investigate this issue.

3. monitoring May 11, 2026, 10:52 PM UTC

   A fix has been deployed for the issue affecting US customers. We are actively monitoring to confirm full stability.

4. monitoring May 11, 2026, 11:09 PM UTC

   We are continuing to monitor for any further issues.

5. resolved May 11, 2026, 11:27 PM UTC

   This incident has been fully resolved. US customers can access FloQast as normal. A Root Cause Analysis will be published on this page shortly. We apologize for the disruption and thank you for your patience.

6. postmortem May 14, 2026, 09:46 PM UTC

   **Summary:** On May 11, 2026, between 3:08 PM and 3:48 PM PT, all customers using the US production environment were unable to log in or access the application. Customers on the EU and APAC databases were not affected. **Root Cause:** A recent deployment introduced a change to how the application constructs the web addresses used to communicate with its backend services. Due to a difference in how those addresses are formatted in the US environment compared to other regions, requests were being sent to an incorrect path, which prevented authentication and page access from completing successfully. **Immediate Resolution:** The address construction logic was corrected, and the fix was deployed, restoring full access for all affected customers shortly thereafter. **Follow-up Actions:** We are broadening automated test coverage to exercise environment-specific configuration more thoroughly, so this class of issue can be caught before reaching production. Additional monitoring and alerting are being added to detect access failures earlier. We are also working toward greater consistency in how service addresses are defined across our production environments to reduce the risk of environment-specific regressions going forward.