Skip to content

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

Open
richlander opened this issue Dec 31, 2024 · 6 comments
Open

dotnet CDN tracking issue #9674

richlander opened this issue Dec 31, 2024 · 6 comments

Comments

@richlander
Copy link
Member

richlander commented Dec 31, 2024

@allschu
Copy link

allschu commented Mar 25, 2025

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.

+ curl -sSL https://dot.net/v1/dotnet-install.sh --output dotnet-install.sh

curl: (56) Recv failure: Connection timed out

Could this be part of this issue?

@baronfel
Copy link
Member

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.

@mairaw
Copy link
Contributor

mairaw commented Mar 25, 2025

My monitoring is alerting that the redirection service is still having issues. I contacted the team again.

@allschu
Copy link

allschu commented Mar 26, 2025

Yes please, thank you

@richlander
Copy link
Member Author

We have a backlog item to switch redirection services. We are planning on moving to Azure Front Door.

@allschu
Copy link

allschu commented Apr 7, 2025

Any updates? still have a lot of failures

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants