On Friday 27 February 2026 at 10:21 UTC, a GRE flood targeted a news publisher customer in Western Europe. The attack peaked at 8.0 Gbps and lasted 62 minutes. Traffic originated from 2889 autonomous systems in 117 countries, predominantly a rented booter service.
| Vector | GRE flood |
| Peak | 8.0 Gbps |
| Duration | 62 min |
| Time to mitigation | 0.659 s |
| Attack traffic reaching origin | 0.068% |
| Legitimate traffic challenged | 0.61% |
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 13 points of presence.
What the customer saw
The customer’s status page stayed green throughout; they learned about the attack from our notification.
Recommendations
- Enable log streaming to your SIEM for faster correlation.
- Lower challenge thresholds on authentication endpoints during high-risk events.
- Add a dedicated rate limit for the targeted route.
The billing model is what got our finance team on board, honestly.
Thanks! Yes — the risk score and its components are included in every log record.
Is the risk score exposed in the logs so we can build our own dashboards on it?
How does the proof-of-work challenge behave on older Android devices? Any numbers below Android 10?
Our auditors asked for exactly this kind of incident evidence under DORA.
Machine-readable ranges are at /ips.json and via the API.
Interesting that most attacks are under ten minutes. Our experience is similar.
Interesting that most attacks are under ten minutes. Our experience is similar.
The billing model is what got our finance team on board, honestly.
Our auditors asked for exactly this kind of incident evidence under DORA.