On Friday 15 May 2026 at 13:58 UTC, a GRE flood targeted a gaming community customer in Central Europe. The attack peaked at 332.4 Gbps and lasted 189 minutes. Traffic originated from 3986 autonomous systems in 22 countries, predominantly hijacked home routers.
| Vector | GRE flood |
| Peak | 332.4 Gbps |
| Duration | 189 min |
| Time to mitigation | 0.716 s |
| Attack traffic reaching origin | 0.072% |
| Legitimate traffic challenged | 0.21% |
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 12 points of presence.
What the customer saw
Checkout conversion was unchanged compared with the same hour of the previous week.
Recommendations
- Lower challenge thresholds on authentication endpoints during high-risk events.
- Enable log streaming to your SIEM for faster correlation.
- Review allow-listed partner ranges quarterly.
The point about origin IPs leaking through certificate transparency logs is underrated.
Is the risk score exposed in the logs so we can build our own dashboards on it?
Thanks! Yes — the risk score and its components are included in every log record.
This matches what we see in iGaming around big matches.
How does the proof-of-work challenge behave on older Android devices? Any numbers below Android 10?