-
Notifications
You must be signed in to change notification settings - Fork 4.9k
dotnet CDN tracking issue #9674
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I don't know exactly what is going on the last few days, but we have a very hard time in reaching https://dot.net/v1/dotnet-install.sh from our Bitbucket pipelines.
Could this be part of this issue? |
The .NET Website uses a different routing infrastructure before it gets to the new CDN urls - see dotnet/install-scripts#582 (comment) for more details. I though this was resolved already, but can investigate with the internal team that controls this infra for us again. |
My monitoring is alerting that the redirection service is still having issues. I contacted the team again. |
Yes please, thank you |
We have a backlog item to switch redirection services. We are planning on moving to Azure Front Door. |
Any updates? still have a lot of failures |
Uh oh!
There was an error while loading. Please reload this page.
We are making important changes to the dotnet CND, due to
azureedge.net
domains no longer being supported/available, per #9671.The following are the tasks we intend to take on with target timelines. All of this is expected to evolve as we learn more.
Phase 1 (January):
releases-index.json
#9669Phase 2 (February-March):
builds.dotnet.microsoft.com
notdownload.visualstudio.microsoft.com
#9675Phase 3 (April?):
Related:
The text was updated successfully, but these errors were encountered: