On an edge miss,
ask a regional L2 node first.
When an edge node misses, it asks a regional L2 node first and goes to the origin only if L2 misses too. Origin requests and origin egress go down as a result.
Included in selected plans; see pricing
Origin fetches per file in a region: 3
Origin fetches per file in a region: 1
Measured results
and observability.
Origin-request reduction and setup time; origin requests and egress saved are reported live in the console
origin requests
Test conditions: 2 edge nodes, 2,400 requests; origin requests fell from 544 to 300. More edge nodes per region and a higher share of repeated requests increase the reduction.
to switch on
Each region gets 1–2 L2 nodes recommended by bandwidth, disk and uptime. Confirm once to enable it for all existing sites.
Measured: 2 edge nodes, 2,400 requests; origin fetches 544 → 300 (−45%)
Two steps to enable,
no per-node setup.
No per-node configuration or rules to write
Click “Enable”
We recommend 1–2 nodes per region by bandwidth, disk and uptime. Confirm once; setup takes about 2 minutes and covers existing sites.
Automated operation and observability
A failing L2 node is bypassed automatically and reinstated on recovery. L2 hit ratio, origin requests and egress saved are reported in the console.
How it compares,
enablement and operations.
Tiered origin: enablement and operations compared
| Features | GoEdge | Cloudflare | gocdn |
|---|---|---|---|
| How to enable | Set a level per node | One switch | One click, nodes recommended |
| Auto bypass and recovery | Bypass supported; switch-back not stated | Yes | Yes, with in-panel notices |
| Origin allows only L2 | Cluster-wide only | Not supported | Per-site switch + IP allowlist + pending protection |
| Conditional routing | No | Yes, via Cache Rules bypassing the upper tier | Yes, with templates |
| Global pause with timed resume | No | No | Yes |
| Origin request queueing (no 503) | No | No | Yes |
| Savings reporting | No | Logs only | Reported in the console |
Based on each product's public docs as of October 2026; Cloudflare refers to Tiered Cache. Performance figures come from a test environment and vary with traffic characteristics.