On Tuesday 8 October 2024 at 12:42 UTC, a memcached amplification targeted a online casino customer in Southeast Asia. The attack peaked at 242.3 Gbps and lasted 104 minutes. Traffic originated from 424 autonomous systems in 66 countries, predominantly mobile carrier ranges.
| Vector | memcached amplification |
| Peak | 242.3 Gbps |
| Duration | 104 min |
| Time to mitigation | 0.792 s |
| Attack traffic reaching origin | 0.055% |
| Legitimate traffic challenged | 0.51% |
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 33 points of presence.
What the customer saw
A brief increase in p99 latency of 198 ms during the first minute, then normal service.
Recommendations
- Enable log streaming to your SIEM for faster correlation.
- Add a dedicated rate limit for the targeted route.
- Review allow-listed partner ranges quarterly.
Our auditors asked for exactly this kind of incident evidence under DORA.
How does the proof-of-work challenge behave on older Android devices? Any numbers below Android 10?