On Monday 3 August 2026 at 16:02 UTC, a search endpoint flood targeted a online casino customer in the Nordics. The attack peaked at 359.8 million requests per second and lasted 115 minutes. Traffic originated from 3486 autonomous systems in 17 countries, predominantly a Mirai-derived IoT botnet.
| Vector | search endpoint flood |
| Peak | 359.8 million requests per second |
| Duration | 115 min |
| Time to mitigation | 0.841 s |
| Attack traffic reaching origin | 0.067% |
| Legitimate traffic challenged | 0.30% |
Timeline
The attack was preceded by an extortion email received two days earlier. Request rates on the targeted routes exceeded their hourly baseline by a factor of 799 within 29 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
Checkout conversion was unchanged compared with the same hour of the previous week.
Recommendations
- Enable log streaming to your SIEM for faster correlation.
- Lower challenge thresholds on authentication endpoints during high-risk events.
- Review allow-listed partner ranges quarterly.
How does the proof-of-work challenge behave on older Android devices? Any numbers below Android 10?
Good question. We will cover that in a follow-up post.
Could you share the dataset behind the percentages?
Clear and practical, thanks.
We had the exact false-positive issue with CGNAT carriers. The weighting change makes sense.
Any plans to support per-tenant limits keyed on a JWT claim?
Good question. We will cover that in a follow-up post.
Thanks — sharing this with our on-call team.
Interesting that most attacks are under ten minutes. Our experience is similar.
We had the exact false-positive issue with CGNAT carriers. The weighting change makes sense.