On Wednesday 8 April 2026 at 09:58 UTC, a Slowloris targeted a fashion retail customer in Latin America. The attack peaked at 480.9 million requests per second and lasted 41 minutes. Traffic originated from 627 autonomous systems in 46 countries, predominantly misconfigured open reflectors.
| Vector | Slowloris |
| Peak | 480.9 million requests per second |
| Duration | 41 min |
| Time to mitigation | 0.511 s |
| Attack traffic reaching origin | 0.008% |
| Legitimate traffic challenged | 0.71% |
Timeline
The attack was preceded by a hacktivist channel announcing the target. Request rates on the targeted routes exceeded their hourly baseline by a factor of 397 within 15 seconds. The risk score of participating clients crossed the challenge threshold automatically and proof-of-work difficulty rose with origin load.
What the customer saw
A brief increase in p99 latency of 93 ms during the first minute, then normal service.
Recommendations
- Enable log streaming to your SIEM for faster correlation.
- Add a dedicated rate limit for the targeted route.
- Keep origin IPs out of public DNS history.
Is the risk score exposed in the logs so we can build our own dashboards on it?
Our auditors asked for exactly this kind of incident evidence under DORA.
The billing model is what got our finance team on board, honestly.