On Friday 2 July 2021 at 07:49 UTC, a CLDAP reflection targeted a education platform customer in Central Europe. The attack peaked at 188.8 Gbps and lasted 74 minutes. Traffic originated from 95 autonomous systems in 32 countries, predominantly hijacked home routers.
| Vector | CLDAP reflection |
| Peak | 188.8 Gbps |
| Duration | 74 min |
| Time to mitigation | 0.300 s |
| Attack traffic reaching origin | 0.015% |
| Legitimate traffic challenged | 0.04% |
Timeline
The attack was preceded by a competitor’s product launch. Edge packet filters identified the flood by source port and payload signature and dropped it at line rate across 20 points of presence.
What the customer saw
Checkout conversion was unchanged compared with the same hour of the previous week.
Recommendations
- Add a dedicated rate limit for the targeted route.
- Review allow-listed partner ranges quarterly.
- Enable authenticated origin pulls.
Is the risk score exposed in the logs so we can build our own dashboards on it?
Any plans to support per-tenant limits keyed on a JWT claim?
Could you share the dataset behind the percentages?
Machine-readable ranges are at /ips.json and via the API.
The billing model is what got our finance team on board, honestly.