Test your connection for IPv6
This page checks whether your own connection can reach the internet over IPv4 (the older internet protocol) and IPv6 (the newer version). Your browser sends small requests to two probe servers, one reachable only over IPv4 and one reachable only over IPv6, and scores each protocol. The test usually finishes in a few seconds.
Running the connection test
The test sends 26 probes, 13 over each protocol. It measures latency (the time a reply takes to arrive), jitter (how much that time varies between probes) and stability (the share of probes that succeed).
- Passed Failed Warning
The test is temporarily unavailable
The site operators have been alerted automatically. Please try again later.
IPv4 score
out of 100
IPv6 score
out of 100
Overall score
out of 100
A score of 85 or more is Excellent, 70 to 84 is Good, 50 to 69 is Fair, 1 to 49 is Poor and 0 means the protocol was not detected. The overall score counts IPv6 at 70 per cent and IPv4 at 30 per cent.
What to do next
Follow the advice that matches your result, then use the buttons to keep a record or run the test again.
Your connection carries both IPv4 and IPv6, so nothing needs fixing. You can keep a copy of this result for your records and check any website for IPv6 readiness.
Your network reaches the internet over IPv6 only. Websites without an IPv6 address may be unreachable for you. Ask your internet service provider whether they offer NAT64 (a translation service that lets an IPv6-only network reach IPv4 websites).
Your IPv6 works, but it runs through a tunnel instead of your provider's own network. Ask your internet service provider when they will provide native IPv6 (IPv6 delivered directly by the provider, without a tunnel) and share this result with them.
Your network has no IPv6 route. Ask your internet service provider when they will enable IPv6 and share this result with them.
Your device attempts IPv6 connections but they time out, which delays every website you visit. Contact your internet service provider and share this result. This broken state is worse than having no IPv6 at all.
Neither protocol reached the probe servers. Check your internet connection, then run the test again.
- Run the test again after any change to your network or router. The button below repeats every probe and gives you a fresh result.
- Keep a record of this result. You can copy it as text, download it as JSON (a plain-text data format) or copy a share link. The share link lets other people see this result without your IP addresses.
IPv4 and IPv6 details
The address, the network that owns it and the timings recorded for each protocol. Latency is the time a reply takes to arrive, jitter is how much that time varies and stability is the share of probes that succeeded.
IPv4
Looking up the network that owns this address.
IPv6
Looking up the network that owns this address.
The network lines give the ASN (autonomous system number, the number that identifies the network that owns the address), the organisation, the country and the address block. The address type describes how the address is assigned, for example a public address or one behind carrier-grade NAT (a shared address used by many customers of a mobile or broadband provider).
IPv4
- Detected IPv4 address
- Median latency (the middle value of the samples)
- Jitter as MAD (median absolute deviation, the middle value of the distances from the median)
- Connection setup for the first request
- Connection stability (probes that succeeded out of three)
- Payload transfer of 10 kilobytes (tests the path MTU, the largest packet the route can carry)
- Latency samples (the first is a warm-up and is left out of the statistics)
IPv6
- Detected IPv6 address
- Median latency (the middle value of the samples)
- Jitter as MAD (median absolute deviation, the middle value of the distances from the median)
- Connection setup for the first request
- Connection stability (probes that succeeded out of three)
- Payload transfer of 10 kilobytes (tests the path MTU, the largest packet the route can carry)
- Latency samples (the first is a warm-up and is left out of the statistics)
In the connection setup, DNS is the name lookup, TCP is the connection handshake, TLS is the security handshake and TTFB is the time until the first byte of the reply arrives. All times are in milliseconds (ms, one thousandth of a second).
Every probe
Open the group to see each request the test sent, its result and its timing.
Full probe table
| Test | Protocol | Result | Latency | Notes |
|---|---|---|---|---|
Blacklist status
We check whether your detected addresses appear on public blacklists, which are lists of addresses reported for spam or abuse. These listings do not change the scores above.