On Monday 9 June 2025 at 10:08 UTC, a SYN flood targeted a ticketing customer in Western Europe. The attack peaked at 207.1 Gbps and lasted 141 minutes. Traffic originated from 819 autonomous systems in 21 countries, predominantly hijacked home routers.
| Vector | SYN flood |
| Peak | 207.1 Gbps |
| Duration | 141 min |
| Time to mitigation | 0.104 s |
| Attack traffic reaching origin | 0.041% |
| Legitimate traffic challenged | 0.24% |
Timeline
The attack was preceded by a breaking political story. Edge packet filters identified the flood by source port and payload signature and dropped it at line rate across 21 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.
- Review allow-listed partner ranges quarterly.
- Keep origin IPs out of public DNS history.
This matches what we see in iGaming around big matches.
Great write-up. We saw almost the same pattern on our login endpoint last month.
Machine-readable ranges are at /ips.json and via the API.
The billing model is what got our finance team on board, honestly.
Solid runbook advice. The DNS-at-2am point hit home.
Any plans to support per-tenant limits keyed on a JWT claim?