-
Notifications
You must be signed in to change notification settings - Fork 4.9k
Notice: builds.dotnet.microsoft.com
is currently unreliable
#9799
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
Labels
area-setup
Issues related to installing .NET Core
Comments
Datapoint without a screenshot. I saw download errors yesterday when spinning up a devcontainer (when the C# DevKit activates it hits these endpoints). |
This was referenced Mar 14, 2025
5 tasks
jonathanpeppers
added a commit
to dotnet/android
that referenced
this issue
Mar 25, 2025
Context: dotnet/core#9799 The dot.net redirector has issues currently, using the CDN URL directly is more reliable. Co-authored-by: Jonathan Peppers <[email protected]>
JamieMagee
added a commit
to dependabot/dependabot-core
that referenced
this issue
Mar 25, 2025
Context: dotnet/core#9799 The dot.net redirector has issues currently, using the CDN URL directly is more reliable.
5 tasks
jonathanpeppers
added a commit
to dotnet/android
that referenced
this issue
Mar 26, 2025
Context: dotnet/core#9799 The dot.net redirector has issues currently, using the CDN URL directly is more reliable. Co-authored-by: Jonathan Peppers <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have been receiving reports of intermittent failures with
builds.dotnet.microsoft.com
. We are investigating it.We appreciate the reports we have been receiving. Please feel free to report them on this issue or link to this issue. We are primarily hearing from Azure DevOps and GitHub Actions users.
Please see #9797 for a good example of failure symptoms (and an excellent report).
We switched domains and CDNs in December 2024 due challenges covered in #9671. The old CDN was very reliable over the course of nearly ten years of our user. It is a surprise to us that we are having trouble.
The data we have access to suggests that these failures occur around Patch Tuesday. That isn't a surprise. The fact that it only occurs around this one day (obviously) doesn't limit its importance.
We have made an initial (significant) change to our CDN infra (on March 12th). Unfortunately, we will likely need to wait until next month to validate if it is effective. Failure reports mid-month will be of great interest to us. Please don't hesitate to share them.
We appreciate your patience. We will get this issue resolved.
The text was updated successfully, but these errors were encountered: