On Friday 1 May 2026 at 21:30 UTC, a CLDAP reflection targeted a online casino customer in the Middle East. The attack peaked at 257.5 Gbps and lasted 179 minutes. Traffic originated from 3954 autonomous systems in 108 countries, predominantly a rented booter service.
| Vector | CLDAP reflection |
| Peak | 257.5 Gbps |
| Duration | 179 min |
| Time to mitigation | 0.261 s |
| Attack traffic reaching origin | 0.047% |
| Legitimate traffic challenged | 0.23% |
Timeline
The attack was preceded by an extortion email received two days earlier. 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
A brief increase in p99 latency of 193 ms during the first minute, then normal service.
Recommendations
- Lower challenge thresholds on authentication endpoints during high-risk events.
- Enable log streaming to your SIEM for faster correlation.
- Keep origin IPs out of public DNS history.
Would love a follow-up on how you handle HTTP/3 fingerprinting.
Solid runbook advice. The DNS-at-2am point hit home.
Any plans to support per-tenant limits keyed on a JWT claim?