Detailed IPv6 test, in real time

This test starts on its own and shows each check as soon as it finishes, along with latency and the hop-by-hop route to your connection. If you don't reach 10/10, you'll see exactly what's missing.

What this IPv6 test checks

First it looks up the AAAA record of a server that only has IPv6 and connects to it by name. Then it connects to an IPv6 address without DNS, to tell an IPv6 fault from a DNS one, and tries other IPv6-only sites. It also checks your address, downloads different sizes to see whether large packets get through, compares latency with IPv4 and traces the route to you.

How to read the route and MTU

The route shows each router between our server and your connection. It's normal for some, or the last one, not to respond, because many devices block it. MTU is the largest packet size on that path: 1500 is typical, and a lower one usually points to a tunnel or PPPoE.

What to do if IPv6 says "No service"

Not having IPv6 isn't a fault: almost all sites keep working over IPv4. To find where the break is, repeat the test on another network, like mobile data, and without a VPN. If it only fails at home, look for the IPv6 option on your router and ask your provider whether they offer it.

If it connects but large packets get lost

This is the most confusing case: IPv6 seems active, but some sites hang while loading. It is usually caused by a badly set MTU on the router, or a firewall blocking ICMPv6, which IPv6 needs to adjust packet size.