Windows for home
A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.
All microsoft hosted servers refuse to respond to requests coming from an IPV6 address on my ISP
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 16%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EH%3C/text%3E%3C/svg%3E)
hau5tastic
0
Reputation points
I've been having this issue for some time now, and its so goddamn annoying.
By default, any Microsoft related website refuses to load (vs, xbox, .net etc) on my ISP when my device is using IPV6. The only reason I am able to access it now is because I disabled IPV6 completely on my system. I have replicated this issue on both windows and linux as well as across different devices.
Azure just refuses to respond to any request that comes from ipv6 address.
I have wireless home internet from bell.
Windows for home
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous2025-10-07T20:28:11.0266667+00:00 Hello @hau5tastic,
Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.
I understand your question regarding problems accessing Microsoft sites like Visual Studio, Xbox, and .NET over IPv6 on your Bell Canada wireless home internet.
This is not an Azure issue; Microsoft services offer full support for IPv6. The issue stems from Bell Canada’s wireless home internet, which has limited or unreliable IPv6 routing. As a result, requests to Microsoft endpoints may be dropped or time out.
Available Quick Fix Options:
- Use IPv4 only__,__ disabling IPv6 (as you’ve done) is the simplest and most stable workaround for now.
- Configure specific sites to use IPv4, you can edit your hosts file or use a browser extension to force IPv4 only for Microsoft sites.
- Please contact Bell support to report "IPv6 routing issues to Microsoft endpoints" and include the traceroute results as evidence.
- Microsoft services do not block IPv6; this issue is caused by the ISP. Keeping IPv4 enabled will maintain stable access until Bell improves its IPv6 routing.
Overview of the IPV6: Internet Protocol version 6 (IPv6) overview - .NET | Microsoft Learn
Kindly let us know if the above helps or you need further assistance on this issue.
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 76%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERJ%3C/text%3E%3C/svg%3E)
Robert Johnston 0 Reputation points2025-11-18T21:21:05.31+00:00 This is not a problem with Bell. I also have this issue, and I am using a Hurricane Electric IPv6 tunnel directly, as my provider (SaskTel) does not support IPv6 for customers. Using said tunnel I can access any other service, including Google, Cloudflare and AWS, using IPv6, but all of MS's services, including Microsoft, XBox and Azure, fail to connect.
Attempting to traceroute to Azure hosted sites and CDNs all fail at the
2a01:111:222:2c::*range, from both my local connection and online IPv6 capable traceroute tools, but fortunately I can use my local DNS to override MS' DNS entries and remove their AAAA entries, making my network stack fall back to IPv4 and restoring functionality.
Sign in to comment
Sign in to answer