On Thursday 2 April 2026 at 15:17 UTC, a search endpoint flood targeted a online casino customer in the Benelux. The attack peaked at 952.4 million requests per second and lasted 82 minutes. Traffic originated from 2390 autonomous systems in 26 countries, predominantly hijacked home routers.
| Vector | search endpoint flood |
| Peak | 952.4 million requests per second |
| Duration | 82 min |
| Time to mitigation | 0.701 s |
| Attack traffic reaching origin | 0.046% |
| Legitimate traffic challenged | 0.75% |
Timeline
The attack was preceded by a publicly announced sales event. Request rates on the targeted routes exceeded their hourly baseline by a factor of 648 within 18 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
The customer’s status page stayed green throughout; they learned about the attack from our notification.
Recommendations
- Add a dedicated rate limit for the targeted route.
- Enable log streaming to your SIEM for faster correlation.
- Lower challenge thresholds on authentication endpoints during high-risk events.