Field guide
A guide to the data, the network and what your connection can tell you.
IP geolocation is approximate. Some internet providers share precise location data; others provide little or none. Cloudflare and its partners may be estimating a location using incomplete or outdated information. Different providers can show very different results for the same IP.
For example, a Cloudflare IP may be registered in San Francisco while the server actually handling traffic is elsewhere. The map shows approximate city locations, not physical server addresses.
Geographical distance is different from the path taken by internet traffic. Your ISP, Cloudflare and the networks between them choose routes based on peering agreements, congestion, faults, DDoS attacks, regulatory constraints and other factors. A farther location may offer a better network route.
The distance in the test tool is an approximate great-circle distance between geolocation coordinates. It does not measure cable length or the actual route.
In service and discontinued describe whether a location or machine has been observed as part of the network. These observations do not guarantee availability or indicate a current outage.
For service incidents, always use the official Cloudflare Status page.
A point of presence (PoP) is a network location, usually identified by a three-letter airport code. A colo is an individual datacenter associated with a PoP.
Cloudflare adds request metadata when a request passes through its network. Local development cannot provide all of those values. Some custom values, including datacenter IDs, server IDs and bot signals, require existing zone rules or specific Cloudflare features. Missing data is shown as “Not provided”; no substitute location is invented.
Bot score indicates Cloudflare's assessment of whether traffic is automated. It is not a probability that the visitor is human. Fingerprints are request signals, not guaranteed device identities.
Cloudflare reports TCP round-trip time for HTTP/1 and HTTP/2, and QUIC round-trip time for HTTP/3 when available. A missing QUIC value is not shown as a zero TCP latency. The browser test measures five requests to this site's diagnostic endpoint and reports their median. It includes browser, network and server processing time, so it is not a speed test or a direct measure of bandwidth.
The speed test uses Cloudflare's measurement engine and generated data. It starts only when you press Start speed test, and you can stop it at any time. Quick tests use about 40 MB; extended tests can use about 180 MB and give fast connections larger samples. Retries may use more data. Each run stops at its time limit.
Results estimate speed to Cloudflare, rather than every destination on the internet. Other transfers, Wi-Fi and browser limits affect the result. Tests do not upload your files. The site's integration disables the engine's optional results logging. Download, upload, idle latency and jitter are included in copied or downloaded diagnostic reports.
Saved places and theme preferences are stored only in your browser. CSV exports contain the currently displayed page of filtered results. Connection reports exclude cookies and authentication tokens. Identifiers are visible by default. Use Hide identifiers to mask them; downloaded and copied reports respect that setting.
Your language choice is remembered in a cookie for one year. Interactive maps use OpenFreeMap vector tiles, with data from OpenStreetMap. Sign-in uses the existing PocketBase service. Private pages and diagnostics are marked as non-cacheable.
No. This is a community project maintained by Matteo Manfredi and is not affiliated with Cloudflare. Observations may be incomplete or outdated. Report errors or suggest improvements through the contact page.