On Tuesday 29 July 2025 at 22:38 UTC, a carpet-bombing UDP flood targeted a healthcare portal customer in the Nordics. The attack peaked at 88.4 Gbps and lasted 48 minutes. Traffic originated from 818 autonomous systems in 16 countries, predominantly misconfigured open reflectors.
| Vector | carpet-bombing UDP flood |
| Peak | 88.4 Gbps |
| Duration | 48 min |
| Time to mitigation | 0.308 s |
| Attack traffic reaching origin | 0.074% |
| Legitimate traffic challenged | 0.51% |
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 32 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.
- Keep origin IPs out of public DNS history.
Nice to read a vendor blog that admits what went wrong.
The point about origin IPs leaking through certificate transparency logs is underrated.
Thanks! Yes — the risk score and its components are included in every log record.
Any plans to support per-tenant limits keyed on a JWT claim?
Verified good bots and allow-listed partners bypass challenges entirely.
Nice to read a vendor blog that admits what went wrong.
Machine-readable ranges are at /ips.json and via the API.
This matches what we see in iGaming around big matches.
Thanks! Yes — the risk score and its components are included in every log record.