What "served from the edge" actually means
A look at what Cloudflare's asset layer does with a static build, and what the numbers in the health endpoint are telling you.
The phrase gets used loosely enough to stop meaning much. Here is the specific version, for a static Astro build uploaded as Worker assets.
What upload actually does
When Wrangler deploys, it hashes every file in dist/ and uploads only the ones
Cloudflare has not seen before. Those files are stored across the network rather
than in one origin location. There is no origin server to miss.
A request for /blog/why-mdx/ is matched against that manifest at whichever
data centre took the connection. On a hit, the file is returned there.
Reading the health endpoint
The /api/health route on this site returns the cf object Cloudflare attaches
to each request:
{
"status": "ok",
"edge": { "colo": "SYD", "country": "AU", "city": "Sydney" },
"connection": { "protocol": "HTTP/3", "tls": "TLSv1.3" }
}
colo is the three-letter code for the data centre that handled the request —
airport codes, mostly. If yours says SYD and the site was deployed from a
laptop in the same city, that tells you very little. The interesting test is
asking someone on another continent what theirs says.
Where the latency actually goes
For a static page the round trip decomposes roughly into:
| Stage | Typical cost | Controlled by |
|---|---|---|
| DNS | 0–20 ms | Resolver, cached after first visit |
| TCP + TLS | 1 round trip | TLS 1.3, resumed on repeat visits |
| Asset lookup | Single-digit | Cloudflare |
| Transfer | Size-bound | You |
Only the last row is yours. This page is a few kilobytes of HTML and one stylesheet, with no JavaScript bundle, so the transfer is close to free — which is the main argument for building the site this way.
Where it stops helping
Static assets at the edge solve distribution. They do not solve:
- Personalisation. Every visitor gets the same bytes. Anything per-user has to run in the Worker.
- Freshness. Content updates on deploy. If your data changes every minute, a static build is the wrong shape.
- Large media. A 40 MB video does not become fast because it is nearby.
For a site that is mostly words, none of those apply, which is why the simple setup holds up.