On Tuesday 22 April 2025 at 09:42 UTC, a GRE flood targeted a crypto exchange customer in the Benelux. The attack peaked at 293.1 Gbps and lasted 42 minutes. Traffic originated from 1545 autonomous systems in 80 countries, predominantly residential proxy networks.
| Vector | GRE flood |
| Peak | 293.1 Gbps |
| Duration | 42 min |
| Time to mitigation | 0.275 s |
| Attack traffic reaching origin | 0.046% |
| Legitimate traffic challenged | 0.05% |
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 37 points of presence.
What the customer saw
The customer’s status page stayed green throughout; they learned about the attack from our notification.
Recommendations
- Lower challenge thresholds on authentication endpoints during high-risk events.
- Review allow-listed partner ranges quarterly.
- Enable log streaming to your SIEM for faster correlation.
Any plans to support per-tenant limits keyed on a JWT claim?
Great to hear, thanks for sharing your experience.
We had the exact false-positive issue with CGNAT carriers. The weighting change makes sense.
Good question. We will cover that in a follow-up post.
We had the exact false-positive issue with CGNAT carriers. The weighting change makes sense.
The billing model is what got our finance team on board, honestly.
Machine-readable ranges are at /ips.json and via the API.
Could you share the dataset behind the percentages?
Do you publish the edge IP ranges in a machine-readable format?