Your connection, in IPv4 and IPv6.
Find out which protocols work, which one your browser uses by default, and how their response times compare.
Your public IP · default connection
Checking…
Waiting for the main server.
Preparing the test…
| Connection | IPv4 | IPv6 |
|---|---|---|
| Reachability | Waiting | Waiting |
| Public IP | — | — |
| Country | — | — |
| Network / ASN | — | — |
| Mean HTTP latency | — | — |
| Min / max | — | — |
| Standard deviation | — | — |
| Jitter | — | — |
| Samples / failed | 0 / 0 | 0 / 0 |
The latency difference appears when both protocols respond.
What is being measured?
Each protocol gets one warm-up request, followed by six measured requests. The test alternates which protocol goes first. Each request has a three-second timeout; failures are shown separately.
Times include an HTTPS request and its response body, as seen by this browser. This is HTTP latency, not ICMP ping. DNS, TLS, the browser and the server can affect it. Jitter is the mean absolute difference between successive successful samples; standard deviation describes their spread. Results describe this route to this server.
“Default” is the protocol used to create this test on the main site. It describes this browser connection, not a fixed preference for every site. A failed IPv6 request may also mean a firewall, browser extension or network policy blocked the check.