Connection troubleshooting
IPv6 no internet access: what to check.
“IPv6 no internet access” is a result to investigate, not a diagnosis. If IPv4 still works, you may be able to browse normally. Start by identifying where you see the message: Windows network status, a router or a website's test.
Start with the result you actually have
| Result | Next step |
|---|---|
| IPv4 detected, IPv6 not detected | Check whether your provider, router and any VPN support IPv6 on this connection. |
| Neither detected | Try normal browsing and check for a network sign-in page. Our endpoints or filtering may also be responsible. |
| Both detected, one website fails | Investigate that destination, its DNS or its route. Our test only confirms our endpoints. |
| Timed out | The request exceeded 4.5 seconds. Repeat the test, then compare another device or network. |
| Not configured | The service has no endpoint configured for that family. No conclusion about your connection follows. |
| Test unavailable | The test could not use its endpoint or response. Check again later before changing network settings. |
Use the IPv6 connection test to collect these results. A failed request means that we did not receive a successful response; it does not identify which part of the path failed.
Narrow it down one change at a time
- Establish the scope. Does normal browsing work? Is one app affected or the whole device? Record when the problem started.
- Compare another device on the same network. If only one device fails, focus on its network settings, software and browser. If several fail, investigate the shared network and provider.
- Compare another permitted network. A working result on another network helps isolate the conditions, but does not identify a specific faulty component.
- Check the router and provider. Confirm that IPv6 is included in your service and that the router has received the expected IPv6 configuration. Use the provider's setup instructions rather than guessing a prefix or gateway.
- Account for VPNs and filtering. Ask whether the VPN supports or intentionally blocks IPv6. On managed devices, involve support before changing network controls.
- Repeat and record. Keep the browser, network and test endpoint consistent when comparing results. Include timestamps and whether IPv4 worked.
A local IPv6 address is not enough
An address beginning with fe80: is link-local. It can exist even when there is no IPv6 route to the internet. A global address, DNS resolution and a usable route all contribute to connectivity; a firewall or remote endpoint can still block a particular request. Read IPv4 vs IPv6 for address types and test limits.
Windows status and website tests can disagree
Windows uses its own connectivity checks. A proxy or network policy can interfere with those checks even when some browsing works. Our result comes from different requests, so the two are not interchangeable. Microsoft explains this in its Network Connectivity Status Indicator overview.
Do not disable IPv6 as a blanket fix. Microsoft warns that disabling it or unbinding it from an interface can affect Windows components. Follow the network operator's diagnosis and Microsoft's IPv6 guidance before making advanced changes.
What to give support
Provide the affected device and network, approximate start time, IPv4/IPv6 test outcomes, VPN state and whether another device works. The connection report on our home page can help collect the current observations. Preview it before copying, then share it through your support channel. It cannot replace router diagnostics or a provider's investigation.