Feature

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

Measured

Measured results
and observability.

Origin-request reduction and setup time; origin requests and egress saved are reported live in the console

−45%

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.

~ 2 min

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.

Scaled to measured ratios
VisitorVisitorVisitorEdge node AEdge node BL2 nodeOrigin
Edge hits1,856
Caught by L2244
Origin fetches300Share of requests: 12.5%

Measured: 2 edge nodes, 2,400 requests; origin fetches 544 → 300 (−45%)

Two steps

Two steps to enable,
no per-node setup.

No per-node configuration or rules to write

1

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.

2

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.

Enable · recommended L2 nodesDemo
East Chinaedge-sh-031.2 Gbps · 1.8 TBEnabled
South Chinaedge-gz-01940 Mbps · 2.0 TBEnabled
North Americaedge-la-021.0 Gbps · 1.2 TBEnabled
edge-sh-03 heartbeat OK · L2 hit ratio 44.9%
Comparison

How it compares,
enablement and operations.

Tiered origin: enablement and operations compared

FeaturesGoEdgeCloudflaregocdn
How to enableSet a level per nodeOne switchOne click, nodes recommended
Auto bypass and recoveryBypass supported; switch-back not statedYesYes, with in-panel notices
Origin allows only L2Cluster-wide onlyNot supportedPer-site switch + IP allowlist + pending protection
Conditional routingNoYes, via Cache Rules bypassing the upper tierYes, with templates
Global pause with timed resumeNoNoYes
Origin request queueing (no 503)NoNoYes
Savings reportingNoLogs onlyReported 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.

Get started

Try the live demo

Open the live demo, or contact us for a quote and the install command