On Wednesday 1 May 2024 at 22:44 UTC, a SYN flood targeted a developer platform customer in Iberia. The attack peaked at 340.3 Gbps and lasted 77 minutes. Traffic originated from 1967 autonomous systems in 114 countries, predominantly a rented booter service.
| Vector | SYN flood |
| Peak | 340.3 Gbps |
| Duration | 77 min |
| Time to mitigation | 0.082 s |
| Attack traffic reaching origin | 0.015% |
| Legitimate traffic challenged | 0.34% |
Timeline
The attack was preceded by no stated motive. Edge packet filters identified the flood by source port and payload signature and dropped it at line rate across 27 points of presence.
What the customer saw
No customer-visible impact. The on-call engineer was notified and acknowledged the incident from the dashboard.
Recommendations
- Add a dedicated rate limit for the targeted route.
- Enable log streaming to your SIEM for faster correlation.
- Enable authenticated origin pulls.
We moved from a scrubbing provider to always-on last year; time to mitigation went from minutes to basically nothing.
We moved from a scrubbing provider to always-on last year; time to mitigation went from minutes to basically nothing.
How does the proof-of-work challenge behave on older Android devices? Any numbers below Android 10?
How does the proof-of-work challenge behave on older Android devices? Any numbers below Android 10?
This matches what we see in iGaming around big matches.
Do you publish the edge IP ranges in a machine-readable format?
Nice to read a vendor blog that admits what went wrong.