On Friday 21 February 2025 at 16:41 UTC, a CLDAP reflection targeted a education platform customer in Southeast Asia. The attack peaked at 20.8 Gbps and lasted 144 minutes. Traffic originated from 918 autonomous systems in 81 countries, predominantly a rented booter service.
| Vector | CLDAP reflection |
| Peak | 20.8 Gbps |
| Duration | 144 min |
| Time to mitigation | 0.655 s |
| Attack traffic reaching origin | 0.025% |
| Legitimate traffic challenged | 0.60% |
Timeline
The attack was preceded by a breaking political story. Edge packet filters identified the flood by source port and payload signature and dropped it at line rate across 13 points of presence.
What the customer saw
Checkout conversion was unchanged compared with the same hour of the previous week.
Recommendations
- Enable log streaming to your SIEM for faster correlation.
- Keep origin IPs out of public DNS history.
- Review allow-listed partner ranges quarterly.
Would love a follow-up on how you handle HTTP/3 fingerprinting.
The billing model is what got our finance team on board, honestly.
Any plans to support per-tenant limits keyed on a JWT claim?
Verified good bots and allow-listed partners bypass challenges entirely.
Solid runbook advice. The DNS-at-2am point hit home.
Great write-up. We saw almost the same pattern on our login endpoint last month.
Do you publish the edge IP ranges in a machine-readable format?
We had the exact false-positive issue with CGNAT carriers. The weighting change makes sense.
Any plans to support per-tenant limits keyed on a JWT claim?
Is the risk score exposed in the logs so we can build our own dashboards on it?