On Friday 27 June 2025 at 13:06 UTC, a login endpoint flood targeted a ticketing customer in Southeast Asia. The attack peaked at 244.8 million requests per second and lasted 20 minutes. Traffic originated from 2191 autonomous systems in 37 countries, predominantly a rented booter service.
| Vector | login endpoint flood |
| Peak | 244.8 million requests per second |
| Duration | 20 min |
| Time to mitigation | 0.086 s |
| Attack traffic reaching origin | 0.022% |
| Legitimate traffic challenged | 0.72% |
Timeline
The attack was preceded by no stated motive. Request rates on the targeted routes exceeded their hourly baseline by a factor of 236 within 17 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.
- Lower challenge thresholds on authentication endpoints during high-risk events.
- Enable log streaming to your SIEM for faster correlation.
Great write-up. We saw almost the same pattern on our login endpoint last month.