Resolved after under a minute, affecting Platform and Agent, on October 23, 2025.
**Impact** An unknown number of internal users found the Fluid Attacks Platform unavailable. The issue started on UTC-5 25-10-21 12:51 and was immediately discovered by one of our monitoring tools, indicating the outage of these components. The problem was resolved in 14.4 minutes \(TTF\), resulting in a total window of exposure of 14.4 minutes \(WOE\). **Cause** A large volume of simultaneous internal processes triggered an unexpected overload in one of our core services, which temporarily degraded its performance and caused a platform outage. The root cause was the number of concurrent requests exceeding the system’s ability to scale quickly. **Solution** We optimized the internal scripts responsible for launching these processes to limit the number of concurrent requests and reduce system load. These changes have already been applied, and further improvements are planned to prevent similar issues in the future. **Conclusion** This incident revealed a scalability limitation in one of our core services. We are working on improvements to make the system more resilient and capable of handling high-demand scenarios without affecting availability. **INFRASTRUCTURE\_ERROR < PERFORMANCE\_DEGRADATION**
Affected components
Update timeline
- identified Oct 23, 2025, 07:16 PM UTC
Some Fluid Attacks products are experiencing availability issues. Click for details: https://availability.fluidattacks.com
- resolved Oct 23, 2025, 07:17 PM UTC
The incident has been resolved, and all affected services are now fully operational.
- postmortem Oct 23, 2025, 09:19 PM UTC
**Impact** An unknown number of internal users found the Fluid Attacks Platform unavailable. The issue started on UTC-5 25-10-21 12:51 and was immediately discovered by one of our monitoring tools, indicating the outage of these components. The problem was resolved in 14.4 minutes \(TTF\), resulting in a total window of exposure of 14.4 minutes \(WOE\). **Cause** A large volume of simultaneous internal processes triggered an unexpected overload in one of our core services, which temporarily degraded its performance and caused a platform outage. The root cause was the number of concurrent requests exceeding the system’s ability to scale quickly. **Solution** We optimized the internal scripts responsible for launching these processes to limit the number of concurrent requests and reduce system load. These changes have already been applied, and further improvements are planned to prevent similar issues in the future. **Conclusion** This incident revealed a scalability limitation in one of our core services. We are working on improvements to make the system more resilient and capable of handling high-demand scenarios without affecting availability. **INFRASTRUCTURE\_ERROR < PERFORMANCE\_DEGRADATION**
Your product runs on more than Fluid Attacks
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services