On Friday 17 April 2026 at 00:40 UTC, a login endpoint flood targeted a online casino customer in Central Europe. The attack peaked at 826.7 million requests per second and lasted 168 minutes. Traffic originated from 2756 autonomous systems in 31 countries, predominantly a headless-browser farm.
| Vector | login endpoint flood |
| Peak | 826.7 million requests per second |
| Duration | 168 min |
| Time to mitigation | 0.197 s |
| Attack traffic reaching origin | 0.008% |
| Legitimate traffic challenged | 0.14% |
Timeline
The attack was preceded by no stated motive. Request rates on the targeted routes exceeded their hourly baseline by a factor of 464 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
- Lower challenge thresholds on authentication endpoints during high-risk events.
- Enable authenticated origin pulls.
- Enable log streaming to your SIEM for faster correlation.
The billing model is what got our finance team on board, honestly.
Thanks! Yes — the risk score and its components are included in every log record.
How does the proof-of-work challenge behave on older Android devices? Any numbers below Android 10?
The billing model is what got our finance team on board, honestly.
Great write-up. We saw almost the same pattern on our login endpoint last month.
This matches what we see in iGaming around big matches.
We had the exact false-positive issue with CGNAT carriers. The weighting change makes sense.
The billing model is what got our finance team on board, honestly.
Thanks! Yes — the risk score and its components are included in every log record.
Clear and practical, thanks.