On Monday 11 August 2025 at 07:54 UTC, a UDP reflection (NTP) targeted a education platform customer in the Nordics. The attack peaked at 354.4 Gbps and lasted 189 minutes. Traffic originated from 2711 autonomous systems in 105 countries, predominantly residential proxy networks.
| Vector | UDP reflection (NTP) |
| Peak | 354.4 Gbps |
| Duration | 189 min |
| Time to mitigation | 0.553 s |
| Attack traffic reaching origin | 0.015% |
| Legitimate traffic challenged | 0.74% |
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 23 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 authenticated origin pulls.
- Enable log streaming to your SIEM for faster correlation.
Interesting that most attacks are under ten minutes. Our experience is similar.
The point about origin IPs leaking through certificate transparency logs is underrated.
Great to hear, thanks for sharing your experience.
Is the risk score exposed in the logs so we can build our own dashboards on it?
Interesting that most attacks are under ten minutes. Our experience is similar.
Do you publish the edge IP ranges in a machine-readable format?
The point about origin IPs leaking through certificate transparency logs is underrated.
We moved from a scrubbing provider to always-on last year; time to mitigation went from minutes to basically nothing.
Thanks! Yes — the risk score and its components are included in every log record.
We moved from a scrubbing provider to always-on last year; time to mitigation went from minutes to basically nothing.
Could you share the dataset behind the percentages?