Hi everyone,
We’re seeing intermittent dependency-resolution failures in CI when downloading through an Artifact Registry virtual Maven repository. It combines a standard repository for private artifacts with a remote repository backed by Maven Central.
The virtual repository occasionally returns “not found” for public POMs already cached in the remote repository. Rerunning the build can succeed without source or configuration changes.
For example, org.apache.commons:commons-parent:pom:{version} returned NOT_FOUND despite valid authentication and download permissions. The POM had been cached for months, and the same file was served successfully 45 seconds later, with unchanged cache metadata.
We ran 45 controlled cold-cache dependency-resolution comparisons covering Maven 3.9.16, Maven 3.8.8, native/Wagon transport, and authentication/retry settings. All passed. Paired virtual/direct-proxy checks also succeeded during that test window, so the underlying cause remains unconfirmed.
Has anyone encountered this behaviour? Which diagnostics would help distinguish virtual-repository routing from remote-cache lookup failures, and is there a recommended workaround?
Thanks for any guidance.
Hi, we faced the same issue 11 times between 1st Oct - 7th Oct 2026.
Want to know what went wrong on GAR side, as it affected our customers.
Hi, we’re experiencing the same issue, with multiple builds impacted across various packages.
We’re seeing the same behaviour, and we have numbers that may help narrow it down.
Setup (created 6 Oct 2026, europe-west1):
- standard Maven repo (empty for now, priority 100)
- remote repo →
MAVEN_CENTRAL (priority 10)
- virtual repo in front of both; clients (Maven 3.9 with the artifactregistry wagon, Gradle 9.7 with the artifactregistry plugin) resolve only through the virtual repo
Symptom. Intermittent from day one. Random artifacts come back 404 (POM, .module, jar, klib), never the same one twice, and they all exist on Maven Central and resolve fine on a rerun. Examples: kotlin-reflect-2.3.21.pom, jackson-databind-2.18.1.jar, ktor-client-winhttp-3.6.0.pom, netty-handler-4.1.137.Final.jar. Our Kotlin Multiplatform builds (~1,600 requests each) fail several times a day; plain Maven builds less often.
Stress test. We replayed the ~1,600 Artifact Registry URLs of a successful build (all already cached in the remote repo), 32 requests in parallel, 25 rounds per repository, alternating the order between the two:
| target |
requests |
unexpected 404 |
| virtual repo |
39,800 |
7 (0.018%) |
| remote repo, direct |
39,800 |
0 |
For now we’ll probably point our clients straight at the remote repository and skip the virtual one until this is sorted out.