On Wednesday 6 November 2024 at 05:39 UTC, a SYN flood targeted a online casino customer in the Benelux. The attack peaked at 175.0 Gbps and lasted 151 minutes. Traffic originated from 3950 autonomous systems in 77 countries, predominantly a Mirai-derived IoT botnet.
| Vector | SYN flood |
| Peak | 175.0 Gbps |
| Duration | 151 min |
| Time to mitigation | 0.313 s |
| Attack traffic reaching origin | 0.002% |
| Legitimate traffic challenged | 0.18% |
Timeline
The attack was preceded by a ransom note demanding payment in Monero. Edge packet filters identified the flood by source port and payload signature and dropped it at line rate across 20 points of presence.
What the customer saw
The customer’s status page stayed green throughout; they learned about the attack from our notification.
Recommendations
- Enable log streaming to your SIEM for faster correlation.
- Keep origin IPs out of public DNS history.
- Enable authenticated origin pulls.
Would love a follow-up on how you handle HTTP/3 fingerprinting.
How do you avoid challenging uptime monitors and partners?