On Thursday 17 July 2025 at 09:13 UTC, a carpet-bombing UDP flood targeted a video streaming customer in the Middle East. The attack peaked at 194.1 Gbps and lasted 99 minutes. Traffic originated from 1050 autonomous systems in 6 countries, predominantly hijacked home routers.
| Vector | carpet-bombing UDP flood |
| Peak | 194.1 Gbps |
| Duration | 99 min |
| Time to mitigation | 0.381 s |
| Attack traffic reaching origin | 0.009% |
| Legitimate traffic challenged | 0.65% |
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 34 points of presence.
What the customer saw
The customer’s status page stayed green throughout; they learned about the attack from our notification.
Recommendations
- Enable log streaming to your SIEM for faster correlation.
- Lower challenge thresholds on authentication endpoints during high-risk events.
- Enable authenticated origin pulls.
How does the proof-of-work challenge behave on older Android devices? Any numbers below Android 10?
Thanks — sharing this with our on-call team.
This matches what we see in iGaming around big matches.
Thanks! Yes — the risk score and its components are included in every log record.