On Wednesday 8 July 2026 at 17:15 UTC, a SYN flood targeted a online casino customer in Southeast Asia. The attack peaked at 75.9 Gbps and lasted 54 minutes. Traffic originated from 3054 autonomous systems in 85 countries, predominantly hijacked home routers.
| Vector | SYN flood |
| Peak | 75.9 Gbps |
| Duration | 54 min |
| Time to mitigation | 0.533 s |
| Attack traffic reaching origin | 0.038% |
| Legitimate traffic challenged | 0.68% |
Timeline
The attack was preceded by an extortion email received two days earlier. Edge packet filters identified the flood by source port and payload signature and dropped it at line rate across 25 points of presence.
What the customer saw
Checkout conversion was unchanged compared with the same hour of the previous week.
Recommendations
- Lower challenge thresholds on authentication endpoints during high-risk events.
- Enable log streaming to your SIEM for faster correlation.
- Review allow-listed partner ranges quarterly.
This matches what we see in iGaming around big matches.
Thanks — sharing this with our on-call team.
Is the risk score exposed in the logs so we can build our own dashboards on it?
Machine-readable ranges are at /ips.json and via the API.
Carpet bombing is nasty. Good to see a clear explanation of it.
Great to hear, thanks for sharing your experience.
Interesting that most attacks are under ten minutes. Our experience is similar.
Thanks! Yes — the risk score and its components are included in every log record.