On Saturday 24 January 2026 at 01:34 UTC, a HTTP POST flood targeted a B2B SaaS customer in Southeast Asia. The attack peaked at 810.8 million requests per second and lasted 36 minutes. Traffic originated from 186 autonomous systems in 50 countries, predominantly a rented booter service.
| Vector | HTTP POST flood |
| Peak | 810.8 million requests per second |
| Duration | 36 min |
| Time to mitigation | 0.336 s |
| Attack traffic reaching origin | 0.070% |
| Legitimate traffic challenged | 0.23% |
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 497 within 11 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
- Review allow-listed partner ranges quarterly.
- Keep origin IPs out of public DNS history.
- Enable authenticated origin pulls.
How does the proof-of-work challenge behave on older Android devices? Any numbers below Android 10?
This matches what we see in iGaming around big matches.
Verified good bots and allow-listed partners bypass challenges entirely.
The billing model is what got our finance team on board, honestly.
Machine-readable ranges are at /ips.json and via the API.
The billing model is what got our finance team on board, honestly.
Is the risk score exposed in the logs so we can build our own dashboards on it?