EDGE  /  a page that knows where it came from reading the trace

One of these
answered you.

This page sits in every city below at the same time. Your browser asked for it once, and Cloudflare's network handed the request to whichever one could answer fastest. Here is the one that did.

Checking which datacenter picked up.

Datacenter
Protocol
Encryption
Your region
Round trip

How this page got here

Four commands, run once. Nothing was built, bundled, or compiled — Cloudflare serves the file you wrote.

Step oneWrite the page

public/index.html — the file you are reading right now.

Anything inside public/ gets published as-is. One HTML file is a complete website.

Step twoPoint Cloudflare at it

wrangler.jsonc

{
  "name": "siewusen02",
  "compatibility_date": "2026-07-31",
  "pages_build_output_dir": "./public"
}

This is the whole configuration. name becomes the subdomain — siewusen02.pages.dev — and pages_build_output_dir says which folder to publish.

Step threeSign in

npx wrangler login

Opens your browser once and stores a token on this machine. You won't need it again on this computer.

Step fourShip it

npx wrangler pages deploy public

Uploads the folder and returns a live URL. The page is on every Cloudflare datacenter within seconds — including the one currently talking to you.

Change something

The loop from here is short. Edit, look, publish.

Where the live numbers come from

Every Cloudflare-served hostname answers at /cdn-cgi/trace with a few lines of plain text describing the request that just happened — datacenter, protocol, TLS version, region. No API key, no setup. This page fetches that file, times the request, and prints what came back.