On Saturday 14 May 2022 at 11:39 UTC, a HTTP POST flood targeted a B2B SaaS customer in Southeast Asia. The attack peaked at 205.1 million requests per second and lasted 92 minutes. Traffic originated from 1545 autonomous systems in 18 countries, predominantly mobile carrier ranges.
| Vector | HTTP POST flood |
| Peak | 205.1 million requests per second |
| Duration | 92 min |
| Time to mitigation | 0.754 s |
| Attack traffic reaching origin | 0.082% |
| Legitimate traffic challenged | 0.43% |
Timeline
The attack was preceded by a hacktivist channel announcing the target. Request rates on the targeted routes exceeded their hourly baseline by a factor of 581 within 26 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 authenticated origin pulls.
- Keep origin IPs out of public DNS history.
- Review allow-listed partner ranges quarterly.
How does the proof-of-work challenge behave on older Android devices? Any numbers below Android 10?
Solid runbook advice. The DNS-at-2am point hit home.
Nice to read a vendor blog that admits what went wrong.