On Thursday 5 March 2026 at 13:04 UTC, a CLDAP reflection targeted a developer platform customer in the Benelux. The attack peaked at 158.6 Gbps and lasted 146 minutes. Traffic originated from 1738 autonomous systems in 40 countries, predominantly hijacked home routers.
| Vector | CLDAP reflection |
| Peak | 158.6 Gbps |
| Duration | 146 min |
| Time to mitigation | 0.129 s |
| Attack traffic reaching origin | 0.025% |
| Legitimate traffic challenged | 0.12% |
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 36 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.
- Lower challenge thresholds on authentication endpoints during high-risk events.
- Enable authenticated origin pulls.
We moved from a scrubbing provider to always-on last year; time to mitigation went from minutes to basically nothing.
How do you avoid challenging uptime monitors and partners?
Good question. We will cover that in a follow-up post.
How does the proof-of-work challenge behave on older Android devices? Any numbers below Android 10?
Solid runbook advice. The DNS-at-2am point hit home.
Do you publish the edge IP ranges in a machine-readable format?
Thanks! Yes — the risk score and its components are included in every log record.