Fluid Attacks experienced a notice incident on January 30, 2026 affecting Platform, lasting 2d 9h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jan 30, 2026, 09:32 PM UTC
Users are experiencing high response times when accessing https://app.fluidattacks.com.
- resolved Feb 03, 2026, 03:32 PM UTC
The incident has been resolved, and platform response times have returned to normal, ensuring a smooth and consistent experience.
- postmortem Feb 03, 2026, 07:22 PM UTC
**Impact** At least one user experienced issues while using the platform, as several tables were slow to load or did not display information correctly, sometimes showing errors. The issue started on UTC-5 26-01-29 21:53 and was proactively discovered 17.7 hours \(TTD\) later by a staff member who reported through our internal channels about unusual delays and failures when accessing different sections of the platform. Although no direct customer reports were received, the issue affected multiple users. The problem was resolved in 2.8 days \(TTF\), resulting in a total window of exposure of 3.5 days \(WOE\) [\[1\]](https://gitlab.com/fluidattacks/universe/-/issues/20342). **Cause** A recently introduced filter was enabled by default and triggered a request that required more resources than expected. This caused the system responsible for retrieving data to become overloaded, which resulted in slow response times and errors across the platform [\[2\]](https://gitlab.com/fluidattacks/universe/-/merge_requests/93622). **Solution** The query used to retrieve location data was updated to be more efficient, reducing the load on the system and restoring normal platform behavior [\[3\]](https://gitlab.com/fluidattacks/universe/-/merge_requests/93739). **Conclusion** The incident has been resolved, and the platform is now operating normally. To prevent similar situations in the future, internal tools have been improved to help detect performance issues earlier, and additional improvements to this part of the system are planned to make it easier to maintain and enhance over time. **PERFORMANCE\_DEGRADATION < INCOMPLETE\_PERSPECTIVE**