On Monday 3 February 2025 at 16:28 UTC, a login endpoint flood targeted a municipal services customer in Southeast Asia. The attack peaked at 765.5 million requests per second and lasted 77 minutes. Traffic originated from 2173 autonomous systems in 115 countries, predominantly residential proxy networks.
| Vector | login endpoint flood |
| Peak | 765.5 million requests per second |
| Duration | 77 min |
| Time to mitigation | 0.452 s |
| Attack traffic reaching origin | 0.059% |
| Legitimate traffic challenged | 0.32% |
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 689 within 21 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
Checkout conversion was unchanged compared with the same hour of the previous week.
Recommendations
- Lower challenge thresholds on authentication endpoints during high-risk events.
- Keep origin IPs out of public DNS history.
- Review allow-listed partner ranges quarterly.
How do you avoid challenging uptime monitors and partners?
How does the proof-of-work challenge behave on older Android devices? Any numbers below Android 10?
We had the exact false-positive issue with CGNAT carriers. The weighting change makes sense.
Do you publish the edge IP ranges in a machine-readable format?
Clear and practical, thanks.
This matches what we see in iGaming around big matches.
Great to hear, thanks for sharing your experience.
Do you publish the edge IP ranges in a machine-readable format?
We moved from a scrubbing provider to always-on last year; time to mitigation went from minutes to basically nothing.