dot.net/v1/dotnet-install.sh times out or drops connections since 2026-11-12, builds.dotnet.microsoft.com works #751

What happens

Since 2026-11-12, requests to https://dot.net/v1/dotnet-install.sh and https://dot.net/v1/dotnet-install.ps1 often time out or drop the connection. The same scripts download fine from https://builds.dotnet.microsoft.com/dotnet/scripts/v1/, where dot.net redirects.

Evidence

• From a developer machine (Windows, curl --max-time 15), 2026-11-13 03:48–03:50 UTC:
  • https://dot.net/v1/dotnet-install.sh: 4 times 301 in 1.3 to 1.6 seconds, then 6 timeouts in a row with 0 bytes received.
  • https://builds.dotnet.microsoft.com/dotnet/scripts/v1/dotnet-install.sh: 10 times 200 in 0.3 to 0.4 seconds.
  • A few minutes earlier, https://dot.net/v1/dotnet-install.ps1 failed with schannel: server closed abruptly (missing close_notify).
• GitHub-hosted runners (Windows, Ubuntu and macOS), in the CI of unoplatform/uno.check, which downloads the script from dot.net:
  • The first failure was at 19:49 UTC on 2026-11-12. From about 00:45 UTC on 2026-11-13, most runs fail.
  • The errors are timeouts, connections that stall without a response, and The SSL connection could not be established ... Received an unexpected EOF or 0 bytes from the transport stream.
  • In the same jobs, seconds earlier, actions/setup-dotnet downloaded the SDK from builds.dotnet.microsoft.com without problems.
  • Example jobs: Ubuntu, 4 stalled attempts, 03:12–03:15 UTC, Windows, SSL EOF, 22:26 UTC, macOS, 02:32 UTC.
• No notice in dotnet/announcements or on githubstatus.com.

Expected

dot.net/v1/dotnet-install.* redirects quickly and reliably, as it did before 2026-11-12.

Question

Is https://builds.dotnet.microsoft.com/dotnet/scripts/v1/dotnet-install.{sh,ps1} a stable URL that tools can use directly, with dot.net/v1 as a fallback?