This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(182.40000000000003, 48%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESP%3C/text%3E%3C/svg%3E)
Hello,
Since today, April 24th, I'm experiencing connectivity issues to most Microsoft services from my public fix IP address given by my hosting provider.
Specifically, with dotnet tools (dotnet add package, dotnet restore, or actually anything that relies on dotnet HttpClient) I am unable to access:
However:
These symptoms strongly suggest that the IP address is being blocked or filtered by Microsoft’s infrastructure (possibly via Azure Front Door or CDN).
Where can I get support for this?
![](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(211.20000000000002, 61%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
If the browser works from the same machine, then your private ipaddress is not blocked. It more likely proxy settings for the browser are different than HttpClient.
Read carefully my post. It happened all of a sudden, on every computer working on the same network. It works with no pb on different url. It works with no pb from the moment I switch on the wifi hotspot of my phone.
If the browser can connect, then the hosting server is not blocking by ipaddress. It sounds like proxy setting. You say curl works, check its proxy configuration.