Your browser times 10 real HTTPS round trips to Azure Front Door through your actual Wi-Fi, internet provider and any VPN or proxy, then shows the median, the first connection time and the jitter.
Sniff, sniff… where are we?
Finding your exit IP…
When the requests are done, you'll see how fast Azure Front Door is from here.
To compare, the home page tests Azure Front Door together with the other CDN providers services: Cloudflare, Akamai, Amazon CloudFront, Google Cloud CDN, Fastly. Azure Front Door is served through Azure Front Door's network, so the round trip ends at Azure Front Door's nearest data center, not at Azure Front Door's own servers.
It's the address websites see when you visit them. At home it usually belongs to your internet provider. On a VPN, proxy, work network or iCloud Private Relay, it belongs to whoever forwards your traffic, and that can be in another city or another country. Services pick which server to send you to based on this address, so it affects your speed too.
Because many proxies and VPNs use split routing: they choose the route by website, so some sites go direct and the rest through the proxy. One IP check only sees its own route. So we ask several at once: 1ms.dog itself, a site in mainland China, Cloudflare, ip.sb, ipinfo.io, IPv4-only and IPv6-only checks, and WebRTC (over UDP). We group what they see by network and mark each exit as direct or proxy. If services that are usually blocked in your country answer anyway, we tell you there's an 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 lookup, TCP and TLS handshakes); it's shown separately and not counted. Then the same connection is reused for a few timed requests, and we show the median. So you see one round trip from your device to the service's nearest server, through your Wi-Fi, provider and any proxy: the delay your apps actually feel.
Ping uses ICMP, which browsers can't send, and many networks treat ICMP differently from normal traffic, so a good ping doesn't always mean a fast app. HTTPS timing takes the same path as the apps you use. The numbers are usually a few milliseconds higher than ping, because the server has to answer a request.
Zoomies ≤ 30 ms: about the same city. Sprint ≤ 80 ms: same region. Trot ≤ 150 ms: fine for almost everything. Stroll ≤ 300 ms: you'll notice it in games and calls. Nap > 300 ms: far away, or a congested route. Not back: no connection within 5 seconds, so the service can't be reached from here. Under 2 ms unlocks the legendary 1ms dog.
Your results aren't sent to us. Latency requests go straight from your browser to the services being tested. To find your exit IP, your browser asks 1ms.dog and a few public IP lookup services, and they see your IP, because that's how an IP check works. Your last result stays in this browser so the dog can tell you if anything changed. A result leaves your browser only when you share it or report a problem. A shared link carries the country and timings, plus city and network only if you tick the box, and never IP addresses. On 1ms.dog the link is shortened and a picture of the result is stored for the link preview in chat apps. After a full test, your browser also exchanges a few tiny messages with 1ms.dog's server in Tokyo to time the round trip there; that server keeps no logs.
Runs entirely in your browser. No account, and we don't collect your results.
© 2026 1ms.dog