On Thursday 4 June 2026 at 04:13 UTC, a login endpoint flood targeted a electronics retail customer in Latin America. The attack peaked at 420.0 million requests per second and lasted 29 minutes. Traffic originated from 3480 autonomous systems in 56 countries, predominantly hijacked home routers.
| Vector | login endpoint flood |
| Peak | 420.0 million requests per second |
| Duration | 29 min |
| Time to mitigation | 0.825 s |
| Attack traffic reaching origin | 0.058% |
| Legitimate traffic challenged | 0.63% |
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 368 within 8 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
No customer-visible impact. The on-call engineer was notified and acknowledged the incident from the dashboard.
Recommendations
- Keep origin IPs out of public DNS history.
- Enable log streaming to your SIEM for faster correlation.
- Enable authenticated origin pulls.
Great write-up. We saw almost the same pattern on our login endpoint last month.
The point about origin IPs leaking through certificate transparency logs is underrated.