On Tuesday 11 March 2025 at 11:07 UTC, a carpet-bombing UDP flood targeted a ticketing customer in Iberia. The attack peaked at 71.3 Gbps and lasted 135 minutes. Traffic originated from 2405 autonomous systems in 7 countries, predominantly mobile carrier ranges.
| Vector | carpet-bombing UDP flood |
| Peak | 71.3 Gbps |
| Duration | 135 min |
| Time to mitigation | 0.277 s |
| Attack traffic reaching origin | 0.059% |
| Legitimate traffic challenged | 0.41% |
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 authenticated origin pulls.
- Lower challenge thresholds on authentication endpoints during high-risk events.
- Review allow-listed partner ranges quarterly.
Our auditors asked for exactly this kind of incident evidence under DORA.
How does the proof-of-work challenge behave on older Android devices? Any numbers below Android 10?
We moved from a scrubbing provider to always-on last year; time to mitigation went from minutes to basically nothing.
How does the proof-of-work challenge behave on older Android devices? Any numbers below Android 10?
Could you share the dataset behind the percentages?