On Sunday 24 August 2025 at 00:50 UTC, a ACK flood targeted a developer platform customer in Southeast Asia. The attack peaked at 192.0 Gbps and lasted 9 minutes. Traffic originated from 2930 autonomous systems in 74 countries, predominantly a Mirai-derived IoT botnet.
| Vector | ACK flood |
| Peak | 192.0 Gbps |
| Duration | 9 min |
| Time to mitigation | 0.929 s |
| Attack traffic reaching origin | 0.004% |
| Legitimate traffic challenged | 0.19% |
Timeline
The attack was preceded by a hacktivist channel announcing the target. Edge packet filters identified the flood by source port and payload signature and dropped it at line rate across 40 points of presence.
What the customer saw
No customer-visible impact. The on-call engineer was notified and acknowledged the incident from the dashboard.
Recommendations
- Enable authenticated origin pulls.
- Keep origin IPs out of public DNS history.
- Lower challenge thresholds on authentication endpoints during high-risk events.
Thanks — sharing this with our on-call team.
Could you share the dataset behind the percentages?
This matches what we see in iGaming around big matches.
Verified good bots and allow-listed partners bypass challenges entirely.
Could you share the dataset behind the percentages?
Carpet bombing is nasty. Good to see a clear explanation of it.
Could you share the dataset behind the percentages?