On Monday 18 May 2026 at 01:16 UTC, a HTTP GET flood targeted a gaming community customer in North America. The attack peaked at 566.1 million requests per second and lasted 124 minutes. Traffic originated from 1695 autonomous systems in 91 countries, predominantly mobile carrier ranges.
| Vector | HTTP GET flood |
| Peak | 566.1 million requests per second |
| Duration | 124 min |
| Time to mitigation | 0.098 s |
| Attack traffic reaching origin | 0.032% |
| Legitimate traffic challenged | 0.56% |
Timeline
The attack was preceded by a competitor’s product launch. Request rates on the targeted routes exceeded their hourly baseline by a factor of 145 within 20 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
- Enable log streaming to your SIEM for faster correlation.
- Lower challenge thresholds on authentication endpoints during high-risk events.
- Review allow-listed partner ranges quarterly.
How does the proof-of-work challenge behave on older Android devices? Any numbers below Android 10?
The point about origin IPs leaking through certificate transparency logs is underrated.