On Monday 22 June 2026 at 05:54 UTC, a SYN flood targeted a news publisher customer in Iberia. The attack peaked at 221.9 Gbps and lasted 166 minutes. Traffic originated from 3358 autonomous systems in 17 countries, predominantly mobile carrier ranges.
| Vector | SYN flood |
| Peak | 221.9 Gbps |
| Duration | 166 min |
| Time to mitigation | 0.226 s |
| Attack traffic reaching origin | 0.005% |
| Legitimate traffic challenged | 0.74% |
Timeline
The attack was preceded by a competitor’s product launch. Edge packet filters identified the flood by source port and payload signature and dropped it at line rate across 26 points of presence.
What the customer saw
A brief increase in p99 latency of 62 ms during the first minute, then normal service.
Recommendations
- Add a dedicated rate limit for the targeted route.
- Enable authenticated origin pulls.
- Review allow-listed partner ranges quarterly.
We moved from a scrubbing provider to always-on last year; time to mitigation went from minutes to basically nothing.
Do you publish the edge IP ranges in a machine-readable format?
Could you share the dataset behind the percentages?
Nice to read a vendor blog that admits what went wrong.
How does the proof-of-work challenge behave on older Android devices? Any numbers below Android 10?
Verified good bots and allow-listed partners bypass challenges entirely.
Our auditors asked for exactly this kind of incident evidence under DORA.
Solid runbook advice. The DNS-at-2am point hit home.
Is the risk score exposed in the logs so we can build our own dashboards on it?