| L3/L4 DDoS mitigation |
⚠ At 126 PoPs. Unpublished capacity limit. |
✓ All 330+ cities. 477 Tbps published capacity. |
| L7 DDoS inspection location |
✗ 20 compute regions only (extra hop) |
✓ All 330+ PoPs at ingress — no extra hop |
| Adaptive / ML-based detection |
✗ Not available |
✓ 7-day traffic profiling, geo/UA/ML scoring |
| Attack traffic billing |
✗ Billed until mitigation activates |
✓ Zero — no attack traffic tax ever |
| Site availability during attack |
✗ Risk of self-pause (503) if spend limit hit |
✓ 100% uptime SLA — never self-pauses |
| Post-attack recovery |
✗ Manual per-project unpausing |
✓ Automatic — no action required |
| Fortescue visibility |
✗ None — no logs, no dashboards |
✓ Security Events, Logpush to SIEM, real-time analytics |
| DDoS sensitivity tuning |
✗ Not configurable |
✓ Per-rule sensitivity + 10 custom expression overrides |
| Challenge granularity |
⚠ All-or-nothing (Attack Challenge Mode) |
✓ Managed Challenge scoped to suspicious traffic only |
| Vendor transparency |
✗ Black-box — no published ruleset or thresholds |
✓ Published managed ruleset + public changelog |
| DDoS uptime SLA |
✗ None published |
✓ 100% uptime SLA (Enterprise) |
| Government endorsement (AU) |
✗ None |
✓ ASD's ACSC co-published DDoS guidance with Cloudflare (Mar 2025) |
| SASE / Zero Trust expansion |
✗ Not available |
✓ 50 Interna seats included with Externa package |