Repository navigation
Intermittent HTTP 404 from v2 FindPackagesById for an existing package (2026-10-26) #356
Description
Summary
Repeated GET requests to the same PowerShell Gallery v2 discovery URL intermittently returned HTTP 404 for the existing powershell-yaml module on October 26, 2026. Other requests to the identical URL returned HTTP 200 with a matching Atom entry.
This report describes observations from one Linux machine. It does not establish a service-wide outage or identify whether the origin, CDN, or an intermediary caused the responses.
Endpoint
https://www.powershellgallery.com/api/v2/FindPackagesById()?id=%27powershell-yaml%27&$top=1
The package page was accessible and listed version 0.4.12:
https://www.powershellgallery.com/packages/powershell-yaml
Observed results
During an initial sequence of 12 discovery requests, approximately five seconds apart (with a package-download check between discovery requests):
- 9 returned HTTP 200 with a matching
powershell-yamlentry. - 3 returned HTTP 404.
- The 404 responses occurred at these UTC request-start timestamps:
- 2026-10-26T23:25:21Z
- 2026-10-26T23:25:42Z
- 2026-10-26T23:25:53Z
- Successful discovery responses contained 3,990 bytes.
All 12 interleaved GET requests to the following package-download URL succeeded, and the downloaded ZIP archives passed integrity checks:
https://www.powershellgallery.com/api/v2/package/VMware.Sdk.Runtime/1.0.2099.24145081
A follow-up check around 23:26:30–23:26:50 UTC made 10 discovery requests using Python urllib and 10 using curl; all 20 returned HTTP 200. This suggests intermittent behavior rather than a persistently missing package.
The initial failed requests used Python urllib with User-Agent: GalleryConnectivityDiagnostic/1.0. Response bodies and request-reference headers were not retained for those three failures. A subsequent attempt to capture those details did not reproduce a failure.
Reproduction / diagnostic command
Run repeated GET requests against the same URL. This is intermittent, so a sequence may return only successful responses. The command below also prints response headers to help capture a request reference if it happens again:
for i in 1 2 3 4 5 6 7 8 9 10 11 12; do
date -u '+%Y-%m-%dT%H:%M:%SZ'
curl --silent --show-error --max-time 15 \
--user-agent 'GalleryConnectivityDiagnostic/1.0' \
--dump-header - --output /dev/null \
--write-out 'HTTP %{http_code}; remote %{remote_ip}; seconds %{time_total}\n' \
'https://www.powershellgallery.com/api/v2/FindPackagesById()?id=%27powershell-yaml%27&$top=1'
sleep 5
doneExpected behavior
Discovery for an existing package should consistently return HTTP 200 with the matching package entry, rather than intermittently returning HTTP 404.
Request
Could the team check for discovery/backend/CDN issues around the UTC timestamps above? No incident for October 26 was listed in psgallery_status.md when checked. Please let us know which additional diagnostics would be most useful if the behavior recurs.
Activity
GABRIELNGBTUC commentedon Oct 27, 2026
We are seeing similar issues on other packages. For the last hour, we have been unable to install any singular module that depends on several submodules (like Microsoft.Graph, Az, ...) without retrying several times. Sometimes for up to more than 10 attempts.
Any pipeline that installs several of these modules is also unable to reach completion as the chances of all these installs succeed are extremely low.
The behaviour seen are many "Source location 'xxx' is not valid" and the powershell gallery page of affected packages intermittently returning 404.
Example log:
With a retry mechanism:
[ubicloud] Retry PowerShell Gallery module installs
CharlPels commentedon Oct 27, 2026
issue is also visible in azure devops pipelines.
can be any file in sample Az.AnalysisServices but next run its another file with same problem.
Az version 16.4.0 not avaiable locally on the agent. Downloading dynamically.
WARNING: Source Location 'https://www.powershellgallery.com/api/v2/package/Az.AnalysisServices/1.3.0' is not valid.
WARNING: Package 'Az.AnalysisServices' failed to download.
WARNING: Dependent Package 'Az.AnalysisServices' failed to install.
WARNING: Package 'Az' failed to install.
Wrap PowerShell Gallery calls in an explicit retry
tompatta commentedon Oct 27, 2026
Seeing the same issue in Azure DevOps Microsoft-hosted agents. Sometimes no packages can be found at all and other times specific packages cannot be downloaded. Different runs with exactly the same code produce different results each time. No 100% successful runs so far.
Retry NuGet provider / PowerShellGet installation on transient PowerS…
rlfink commentedon Oct 27, 2026
I have been experiencing this same issue while trying to install Az modules. I have attempted using Powershell 5.1 and 7. I have attempted across 2 separate machines on completely separate public IPs, from outside the Azure cloud and from within the Azure cloud. It occurs randomly across different modules. For example,
WARNING: Source Location 'https://www.powershellgallery.com/api/v2/package/Az.ResourceGraph/1.3.0' is not valid.
PackageManagement\Install-Package : Package 'Az.ResourceGraph' failed to download.
ekdegerman commentedon Oct 27, 2026
Seeing the same issue when installing Microsoft.Graph or Az both locally and in Azure DevOps Microsoft-hosted agents. Different submodules fail for different runs. The files are available when trying to download them manually with a separate request. Version does not seem to matter.
alerickson commentedon Oct 27, 2026
Thank you for letting us know! We're going to failover to our last known good deployment shortly. I'll update when that's complete to see if these issues improve.
rehkech commentedon Oct 27, 2026
We are receiving this on almost every run for the last 5 hours which is causing a failure:
"WARNING: Source Location 'https://www.powershellgallery.com/api/v2/package/Microsoft.Xrm.Data.Powershell/2.8.21' is not valid."
tompatta commentedon Oct 27, 2026
I am now getting successful downloads in my automations!
alerickson commentedon Oct 27, 2026
Tom Schoen (@tompatta) good to hear! Changes completed roughly 1 hour ago and we've seen stability on our end. I'm going to close this issue but feel free to comment here and I'll re-open if it persists.
[ubicloud] Retry PowerShell Gallery module installs
szabolcsleitner-tresorit commentedon Nov 6, 2026
I think the same thing is happening again...
tompatta commentedon Nov 6, 2026
alerickson
Can confirm, seeing the same happening again in my pipelines. Some seem to try to locate the repository on port 8080...
alerickson commentedon Nov 6, 2026
szabolcsleitner-tresorit Tom Schoen (@tompatta) thanks for the updates, could you share the request calls you're making?
szabolcsleitner-tresorit commentedon Nov 6, 2026
I'm getting this warning in a Azure powershell task
Source Location 'http://www.powershellgallery.com:8080/api/v2/package/Az.CognitiveServices/1.16.0' is not valid.It is completely random which dependency it gets stuck on.
Then the Az install fails:
##[error]Unable to save the module 'Az'.alerickson commentedon Nov 6, 2026
Thank you! This should be mitigated as of roughly 20 minutes ago, though it may take a full hour for changes to fully propagate through.
szabolcsleitner-tresorit commentedon Nov 6, 2026
It's working again, thank you!