CDN Node CheckThe edge node your browser actually hits on Cloudflare, Akamai, Fastly, CloudFront, ByteDance and other CDNs, with its city, cache status and latency

CDNs route each visitor to a nearby edge node based on their network, so the check has to run in your own browser. This page requests one public resource per CDN and reads the node from it. Most are CDNPerf test files hosted on each CDN, which expose response headers carrying node info to web pages; Cloudflare and GCP are read from what their endpoints return, and Netlify and Wikimedia from Server-Timing via the browser’s Resource Timing API.

Node codes are mostly nearby airport codes (e.g. LAX for Los Angeles, NRT for Tokyo), which this site converts to cities. Latency is the median of 3 requests after the first one and covers the full HTTPS round trip.

With a proxy on, the result reflects nodes near the proxy exit. Different customers of the same CDN may also use different node groups, so results only describe the resources tested here.

Akamai and NetEase only give the node IP, so this site looks up where that IP is; CDN77, Medianova, Melbicom and ByteDance overseas nodes only reveal the country. Vercel, Gcore, Alibaba Cloud, Tencent EdgeOne and others have no public resource exposing node info yet, so they are not included.