-
Notifications
You must be signed in to change notification settings - Fork 5k
.NET web site is down #104230
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
Tagging subscribers to this area: @dotnet/runtime-infrastructure |
CI is also failing:
(maybe we can catch >500 and avoid printing the response HTML in logs 😅 ) |
For the sake of others reading this, a workaround (courtesy of @martincostello) is to use the following urls while the dotnet subdomain is down (specifically for those requiring the install scripts): |
Apologies for the inconvenience. The team is currently investigating the issue. |
Hello, team. Looks like the site just came back up again. In the future, is there a status page for this site that we can follow to get any updates? Something similar to: |
Yes, site is back up again. Thanks for your suggestion @lucaspimentel. I'll discuss that with the team, but we probably would have the same issue with that site today 😢 it makes sense for the other sites that have multiple teams and services under. |
I downloaded from master branch, thank you for the tip. |
FWIW a short post-mortem would be nice. I appreciate that this also triggered the process of moving the dotnet-install scripts from marketing website into a blob storage. |
Related: dotnet/install-scripts#490 |
I'm curious about what happened, are there any disclosure about what happened? |
The website still down. |
Thanks for pointing that out. I routed that to the right folks internally. |
@GeeSuth can you confirm if that URL is working for you now? We're double checking all our services now. |
Works for me (accessing from Europe). |
Since you requested @filipnavara - here's a post-mortem of what happened today: We moved the website to a new infrastructure and did not have a complete checklist of tasks for the migration. We have updated the checklist, reconfigured the missing resources on the new setup, and are evaluating moving the storage of the .NET scripts out of the dot.net website. We're double checking all services are reconfigured appropriately as systems come back online. |
@mairaw Yes, its working now, |
Thanks for pointing out the additional service we missed on the first round. |
Not sure who to ping...
The text was updated successfully, but these errors were encountered: