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.
Results you can see
Origin savings and setup time; origin requests and egress saved are shown live in the panel
fewer origin requests
In a test of 2,400 requests, origin requests fell from 544 to 300. More nodes per region and more repeated requests mean bigger savings.
to switch on
Each region gets 1–2 recommended L2 nodes. Confirm once and all existing sites are covered.
Two steps
No per-node setup, no 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.
Done
Failures are bypassed and recovered automatically. L2 hit ratio, origin requests and egress saved are shown right in the panel.
How it compares
Tiered caching, with the least setup and upkeep
| Features | GoEdge | Cloudflare | gocdn |
|---|---|---|---|
| How to enable | Set a level per node | One switch | One click, nodes recommended |
| Auto bypass and recovery | No | 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 | No | Yes, with templates |
| Global pause with timed resume | No | No | Yes |
| Origin request queueing (no 503) | No | No | Yes |
| Savings dashboard | No | Logs only | Shown in the panel |
Based on each product's public docs as of October 2026; Cloudflare refers to Tiered Cache. Figures come from a test environment and vary by workload.
Tiered caching comes with selected plans
The pricing page shows which plans include it. Switch it on in the panel once included.