Edge Node Declaration

729999

This endpoint is served from a hybrid edge — public cloud and self-hosted nodes — not from the origin server.

Last reviewed 31 October 2026

You are at the edge. Requests to this host are answered by the nearest healthy node — a public cloud PoP or one of our own nodes, whichever is closer. Cached content is delivered from there; anything else is fetched from origin on your behalf.

Both tiers share one cache policy, so it makes no difference to a request which one answers. Nothing here is authoritative: the origin remains the single source of truth.

Status

All systems operational Updated 30 Oct 2026 · 21:12 UTC

99.99%Uptime, 30 days

12.4MRequests, 24 hours

94.2%Cache hit ratio

41 msp95 time to first byte

Last 30 days 1 partial outage · 30 Oct 2026

Public cloud PoPsOperational

Self-hosted nodesOperational

Origin fetchOperational

Cache purgeOperational

Node

Network	Hybrid edge · public cloud + self-hosted
Public cloud tier	Cloudflare edge network · anycast
Self-hosted tier	729999 nodes · direct uplink, closer to origin
Serving node	Nearest healthy node in either tier
Tracing	`X-Edge-Node`, plus `CF-Ray` on the public tier
Caching	Shared policy across tiers, purge within 30 seconds
Protocols	HTTPS, HTTP/2 and HTTP/3
Origin	Never exposed directly

What this means

Traffic lands on the nearest healthy node, whether that is a public cloud PoP or a self-hosted node.
Both tiers serve the same objects under the same cache policy; a request does not care which one answers.
Cached objects are copies of origin files, kept for speed rather than durability.
Purges and cache expiry never delete anything at origin.
The serving node, and its tier, are reported in the x-edge-node response header.