P.S.A. CDN Issues

Question

P.S.A. CDN Issues

Closed this issue 8 days ago · 21 comments

denelon commented 11 days ago

We've received reports of users not being able to update their cache.

This appears to be an upstream CDN issue.

We have engineers engaged to investigate.

Answer 1 · 2025-10-28T03:45:24.000Z

The following issues might be duplicates:

#5834
#5366

AI-generated content by genai-issue-dedup may be incorrect.

Answer 2 · 2025-10-28T12:44:09.000Z

upgrade, install, nothing is working

I get

An unexpected error occurred while executing the command:
InternetOpenUrl() failed.
0x80072ee2 : unknown error

Answer 3 · 2025-10-28T17:42:49.000Z

This has also been ongoing on my end for about 16 hours now...
Asia-Pacific region.

Time out on cdn.winget.microsoft.com, but storeedgefd.dsx.mp.microsoft.com seems to be responsive.

Answer 4 · 2025-10-28T19:45:35.000Z

It's now working on my end, Asia-Pacific region. 👍

Answer 5 · 2025-10-28T19:53:37.000Z

Thanks for letting us know about the Asia-Pacific region @jorgereymartinez! We've been looking at the automated testing we do across regions, and didn't see the error there, so it must have been resolved. My guess is this could still crop up again as we haven't gotten a root cause with our upstream provider yet.

Answer 6 · 2025-10-29T16:10:23.000Z

In Europe the CDN still unreachable.

prompt -> winget upgrade
Failed in attempting to update the source: winget

ComputerName : cdn.winget.microsoft.com
RemoteAddress : 13.107.246.44
RemotePort : 443
PingSucceeded : False
PingReplyDetails (RTT) : 0 ms
TcpTestSucceeded : False

Answer 7 · 2025-10-29T16:17:08.000Z

In Europe the CDN still unreachable.

Indeed.

In fact all 4 IP addresses returned by DNS are unresponsive.

* Host cdn.winget.microsoft.com:443 was resolved.
* IPv6: 2620:1ec:bdf::44, 2620:1ec:46::44
* IPv4: 13.107.213.44, 13.107.246.44

Answer 8 · 2025-10-29T16:28:29.000Z

Worked like a few mins ago after installing ~5 packages, and then it stopped working out of nowhere.

Answer 9 · 2025-10-29T16:48:34.000Z

PS C:\> nslookup cdn.winget.microsoft.com
Server:  UnKnown
Address:  192.168.1.1

*** UnKnown can't find cdn.winget.microsoft.com: Server failed
PS C:\> nslookup winget.microsoft.com
Server:  UnKnown
Address:  192.168.1.1

Name:    winget.microsoft.com

PS C:\> nslookup microsoft.com
Server:  UnKnown
Address:  192.168.1.1

Non-authoritative answer:
Name:    microsoft.com
Addresses:  2603:1020:201:10::10f
          2603:1010:3:3::5b
          2603:1030:b:3::152
          2603:1030:20e:3::23c
          2603:1030:c02:8::14
          13.107.213.51
          13.107.246.51

Something seems to be wrong with DNS.

Answer 10 · 2025-10-29T16:50:59.000Z

Not working for me as well.

Answer 11 · 2025-10-29T16:53:24.000Z

Can at least one Microsoft server work without interruptions a whole day?

Answer 12 · 2025-10-29T17:28:31.000Z

Sadly, it looks like there is now a broader issue:
https://azure.status.microsoft/status

Answer 13 · 2025-10-29T17:55:00.000Z

the entire Azure CDN seems down/unreachable worldwide at the moment...

https://azure.status.microsoft
most likely because of this:

Answer 14 · 2025-10-29T18:00:07.000Z

Even support.microsoft.com is unreachable in Southeast Asia.

>ping cdn.winget.microsoft.com

Pinging part-0031.t-0009.t-msedge.net [2620:1ec:bdf::59] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 2620:1ec:bdf::59:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

>ping support.microsoft.com

Pinging part-0031.t-0009.t-msedge.net [2620:1ec:bdf::59] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 2620:1ec:bdf::59:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Now even DNS is gone.

>nslookup cdn.winget.microsoft.com
Server:  UnKnown
Address:  2001:e68:****:****::****

DNS request timed out.
    timeout was 2 seconds.
*** UnKnown can't find cdn.winget.microsoft.com: Server failed

>nslookup support.microsoft.com
Server:  UnKnown
Address:  2001:e68:****:****::****

DNS request timed out.
    timeout was 2 seconds.
*** UnKnown can't find support.microsoft.com: Server failed

Answer 15 · 2025-10-29T18:49:47.000Z

seems to be coming back...

Answer 16 · 2025-10-29T19:54:02.000Z

DNS records for cdn.winget.microsoft.com are cyclically appearing then disappearing, linked to that "Azure Front Door - Connectivity issue", but the latest update, https://azure.status.microsoft/en-us/status, indicates it should be recovering. Clearly it is not!

update: appears to have resolved now

PS C:\> nslookup -type=a cdn.winget.microsoft.com. ns4
...
Non-authoritative answer:
Name:    mel01r9a.msedge.net
Address:  104.212.68.176
Aliases:  cdn.winget.microsoft.com
          winget-cache-pme-cxfsgwfxarb8hwg0.z01.azurefd.net
          mr-z01.tm-azurefd.net
          shed.dual-low.part-0010.t-0009.t-msedge.net
          azurefd-t-fb-prod.trafficmanager.net
          dual.part-0003.t-0009.fb-t-msedge.net
          global-entry-fb-afdthirdparty-unicast.trafficmanager.net

PS C:\> winget source update --verbose
Updating all sources...
Updating source: msstore...
Done
Updating source: winget...
Done
Updating source: winget-font...
Done

Answer 17 · 2025-10-30T01:44:40.000Z

Working as of right now from SEA. Lets hope it doesn't goes down when I'm installing packages from winget.

Answer 18 · 2025-10-30T04:28:57.000Z

worked all the time for me in Germany

Answer 19 · 2025-10-30T17:28:33.000Z

Hey everyone, it seems this issue has been resolved.

The CDN issue impacting cdn.winget.microsoft.com is still being investigated internally, and the Azure Front Door issue also seems to be resolved.

I'm going to go ahead and close this issue.

Answer 20 · 2025-10-30T17:50:28.000Z

@denelon, for me, winget is still stuck when using winget upgrade and using curl to check connectivity results in a failure:

PS C:\Windows\System32> curl.exe -v -s https://cdn.winget.microsoft.com/cache/source2.msix -o NUL
* Host cdn.winget.microsoft.com:443 was resolved.
* IPv6: 2620:1ec:bdf::48, 2620:1ec:46::48
* IPv4: 13.107.246.68, 13.107.213.68
*   Trying [2620:1ec:bdf::48]:443...
* schannel: disabled automatic use of client certificate
* ALPN: curl offers http/1.1
* Recv failure: Connection was reset
* schannel: failed to receive handshake, SSL/TLS connection failed
* closing connection #0

Answer 21 · 2025-10-31T10:27:09.000Z

I don't think that this is the correct place to report this, but I don't know of a better place.

In addition to winget, even websites like support.microsoft.com and status.cloud.microsoft are not opening at all on any of my computers/ mobile devices in India. The browser shows ERR_TIMED_OUT when trying to connect to them. So, it looks the CDN issue hasn't been resolved yet.

Not all microsoft websites are down, though. For example, azure.status.microsoft and copilot.microsoft.com are working fine.