On Monday 8 September 2025 at 00:46 UTC, a carpet-bombing UDP flood targeted a online casino customer in the UK. The attack peaked at 76.3 Gbps and lasted 58 minutes. Traffic originated from 986 autonomous systems in 68 countries, predominantly a headless-browser farm.
| Vector | carpet-bombing UDP flood |
| Peak | 76.3 Gbps |
| Duration | 58 min |
| Time to mitigation | 0.439 s |
| Attack traffic reaching origin | 0.028% |
| Legitimate traffic challenged | 0.33% |
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 36 points of presence.
What the customer saw
The customer’s status page stayed green throughout; they learned about the attack from our notification.
Recommendations
- Keep origin IPs out of public DNS history.
- Enable log streaming to your SIEM for faster correlation.
- Enable authenticated origin pulls.
Thanks — sharing this with our on-call team.
Machine-readable ranges are at /ips.json and via the API.
Any plans to support per-tenant limits keyed on a JWT claim?
Carpet bombing is nasty. Good to see a clear explanation of it.
Would love a follow-up on how you handle HTTP/3 fingerprinting.