Fluid Attacks experienced a critical incident on September 26, 2025 affecting Platform and Agent, lasting 29m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Sep 26, 2025, 01:18 PM UTC
Some Fluid Attacks products are experiencing availability issues. Click for details: https://availability.fluidattacks.com
- resolved Sep 26, 2025, 01:20 PM UTC
The issue has been resolved, and all Fluid Attacks products are now fully available.
- postmortem Sep 26, 2025, 02:36 PM UTC
**Impact** An unknown number of users encountered the Fluid Attacks' official documentation, which was unavailable. The issue started on UTC-5 25-09-26 00:45 and was proactively discovered 5 minutes \(TTD\) later by one of our monitoring tools and staff members, indicating a disruption in this component. The problem was resolved in 1.2 hours \(TTF\), resulting in a total window of exposure of 1.2 hours \(WOE\) [\[1\]](https://gitlab.com/fluidattacks/universe/-/issues/18036). **Cause** A system update introduced a change that reduced the limit on certain network connections. This prevented part of our infrastructure from communicating properly, which led to the disruption [\[2\]](https://gitlab.com/fluidattacks/universe/-/merge_requests/85382). **Solution** We updated the configuration to allow the affected component to connect directly, restoring normal communication and service availability [\[3\]](https://gitlab.com/fluidattacks/universe/-/merge_requests/85392). **Conclusion** To reduce the risk of similar problems in the future, we will adopt a safer process when updating critical systems by gradually migrating services to a duplicate environment. While this makes updates slower, it helps prevent disruptions that may only appear hours after a change. We will also continue to explore additional preventive measures. **INFRASTRUCTURE\_ERROR < IMPOSSIBLE\_TO\_TEST**