On Sunday 4 September 2022 at 19:27 UTC, a HTTP/2 rapid reset targeted a ticketing customer in the Benelux. The attack peaked at 541.2 million requests per second and lasted 12 minutes. Traffic originated from 2193 autonomous systems in 105 countries, predominantly misconfigured open reflectors.
| Vector | HTTP/2 rapid reset |
| Peak | 541.2 million requests per second |
| Duration | 12 min |
| Time to mitigation | 0.902 s |
| Attack traffic reaching origin | 0.048% |
| Legitimate traffic challenged | 0.43% |
Timeline
The attack was preceded by no stated motive. Request rates on the targeted routes exceeded their hourly baseline by a factor of 792 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
A brief increase in p99 latency of 129 ms during the first minute, then normal service.
Recommendations
- Keep origin IPs out of public DNS history.
- Enable authenticated origin pulls.
- Review allow-listed partner ranges quarterly.
We moved from a scrubbing provider to always-on last year; time to mitigation went from minutes to basically nothing.
Solid runbook advice. The DNS-at-2am point hit home.
Any plans to support per-tenant limits keyed on a JWT claim?