On Thursday 7 May 2026 at 05:15 UTC, a ACK flood targeted a gaming community customer in Southeast Asia. The attack peaked at 105.8 Gbps and lasted 88 minutes. Traffic originated from 141 autonomous systems in 25 countries, predominantly misconfigured open reflectors.
| Vector | ACK flood |
| Peak | 105.8 Gbps |
| Duration | 88 min |
| Time to mitigation | 0.438 s |
| Attack traffic reaching origin | 0.033% |
| Legitimate traffic challenged | 0.05% |
Timeline
The attack was preceded by a competitor’s product launch. Edge packet filters identified the flood by source port and payload signature and dropped it at line rate across 18 points of presence.
What the customer saw
A brief increase in p99 latency of 196 ms during the first minute, then normal service.
Recommendations
- Lower challenge thresholds on authentication endpoints during high-risk events.
- Review allow-listed partner ranges quarterly.
- Enable authenticated origin pulls.
Thanks — sharing this with our on-call team.
How do you avoid challenging uptime monitors and partners?