On Thursday 6 November 2025 at 14:48 UTC, a carpet-bombing UDP flood targeted a airline booking customer in the Benelux. The attack peaked at 332.6 Gbps and lasted 68 minutes. Traffic originated from 1617 autonomous systems in 59 countries, predominantly residential proxy networks.
| Vector | carpet-bombing UDP flood |
| Peak | 332.6 Gbps |
| Duration | 68 min |
| Time to mitigation | 0.801 s |
| Attack traffic reaching origin | 0.021% |
| Legitimate traffic challenged | 0.25% |
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 24 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 log streaming to your SIEM for faster correlation.
- Enable authenticated origin pulls.
- Review allow-listed partner ranges quarterly.
Could you share the dataset behind the percentages?
Nice to read a vendor blog that admits what went wrong.
Any plans to support per-tenant limits keyed on a JWT claim?
How do you avoid challenging uptime monitors and partners?
Thanks — sharing this with our on-call team.
Verified good bots and allow-listed partners bypass challenges entirely.
Nice to read a vendor blog that admits what went wrong.
We moved from a scrubbing provider to always-on last year; time to mitigation went from minutes to basically nothing.