Your browser times 10 real HTTPS round trips to Fastly through your actual Wi-Fi, ISP and any VPN or proxy, and shows the median, the first connection and the jitter.
Sniff, sniff… where are we?
Sniffing out your exit…
When the samples are in, you'll see how fast Fastly is from here.
To compare, the home page tests Fastly together with the other CDN providers services: Cloudflare, Akamai, CloudFront. Fastly is answered by Fastly's network, so the round trip ends at Fastly's nearest location. Reddit, PyPI use the same network: if they are slow too, the problem is your route to Fastly, not Fastly.
It's the address websites see when you visit them. At home it usually belongs to your ISP. With a VPN, proxy, company network or iCloud Private Relay, it belongs to whoever forwards your traffic, and that can be in another city or country. The exit decides which server a service sends you to, so it decides your speed too.
Rule-based proxies and VPNs pick the route by destination: some sites go direct, the rest through the proxy, so one IP check only sees its own route. We ask several at once (a site in mainland China, Cloudflare, ip.sb, ipinfo.io, IPv4-only and IPv6-only checks, and WebRTC over UDP), group what they see by network, and mark each exit local or proxy. If services that are usually unreachable from your country answer anyway, we point out the exit none of the checks could see.
Your browser opens a real HTTPS connection to each service. The first request only sets up the connection (DNS, TCP, TLS) and isn't counted; then the same connection is reused for timed requests, and we show the median. That is one round trip from your device to the service's nearest server, through your Wi-Fi, ISP and any proxy: the delay your apps actually get.
Ping uses ICMP, which browsers can't send, and many networks treat it differently from normal traffic. HTTPS timing follows the same path as the apps you use. Numbers are usually a few milliseconds higher than ping, because the server has to answer the request.
Zoomies ≤ 30 ms: same city. Sprint ≤ 80 ms: same region. Trot ≤ 150 ms: fine for almost everything. Stroll ≤ 300 ms: noticeable in games and calls. Nap > 300 ms: far away or congested. Not back: no connection within 5 seconds, so the service is unreachable from here. Under 2 ms earns the legendary 1ms dog.
No. Every request goes straight from your browser to the service being tested. 1ms.dog only serves the static page and never receives your results. Your last result stays in this browser so the dog can tell you if things changed. Shared links carry cities, networks and timings, never IP addresses.