1ms.dog
English · 简体中文
Where does your internet really exit, and how far is the world from there? 1ms.dog finds every exit your traffic uses (your local line and any proxy or VPN), then a shiba plays fetch with 40 services worldwide plus a local pack, right from your browser. Each service is a ball thrown as far as its latency.
Live: https://1ms.dog
More from 1ms.dog, all free and open source (hover a name to see what it answers)
IP & privacy: EgressLens · IP Quality Test · Who Are You · ASN Lookup · Streaming & AI Unlock Check
Speed & connectivity: Network X-Ray · Speed Test · DNS Test · Domain X-Ray · IPv6 Test · CDN Radar · Reach Check · Network Diagnosis · Route Trace · Global Ping
Cloud & costs: Me2Cloud · Lightsail Cost Saver · Cloud Cost Planner
Command line: httpslatency · vps2cloud · dnstest
What it does
- Every exit, local and proxy. A rule-based proxy picks the route by destination, so a single "what is my IP" check only sees its own route. The page asks checks in different places at once: a site in mainland China, Cloudflare, ip.sb, ipinfo.io, IPv4-only and IPv6-only hosts, and WebRTC over UDP. It groups their answers by network and marks each exit as local or proxy. When services that are usually unreachable from your country answer anyway, it points out the exit none of the checks could see.
- Latency to 40 services, measured at their edge. Covers AI, everyday web, video and music, social, developer tools, gaming and CDNs, plus a local pack picked by exit country (mainland China, Japan, Korea, Russia, Europe, Latin America…).
- A verdict, not just a median. Local favorites and global services are judged separately, so the page tells you where it's slow: international routes or the proxy server, your own line, or everything going through a proxy. It also translates the numbers into everyday uses: gaming, video calls, streaming, AI tools and dev tools.
- Share a result as an image drawn in your browser, or as a link that carries the result itself. Links hold the country and timings, plus city and network only if you tick the box; never IP addresses.
- 10 languages, all pre-rendered, plus landing pages chosen per language for the services people search latency for there (
/chatgpt/, /zh-cn/dockerhub/, /ru/discord/…).
- Private by design: every request goes straight from your browser to the service being tested. The site is static files; it never receives your results. A shared link carries its result in the path (
/r/…), and a small Worker reads it to put the result in the link preview.
- The same test from a terminal. On a VPS, a Linux box or a router, httpslatency times the same services over real HTTPS, gives the same verdict, and prints a result link that opens here:
curl -fsSL https://1ms.dog/i | sh. It reads the list from /services.json, which the build writes from src/services.mjs; the Worker passes its installers and release files on from GitHub (/i, /i.ps1, /v, /dl/…).
How latency is measured
Your browser opens a real HTTPS connection to each service. The first request only sets the connection up (DNS, TCP, TLS) and isn't counted. Timed requests then reuse that connection, and the page shows the median. The result is one round trip from your device to the service's nearest server, through your Wi-Fi, ISP and any proxy.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
