Is Google Artifact Registry Down? Google Artifact Registry Status, Outages, and Your CI

Your CI just went red and you suspect Google Artifact Registry. Here is how to confirm an outage in seconds - and how to stop a registry blip from failing your builds in the first place.

When Google Artifact Registry has a hiccup, every pipeline that depends on it can fail at once. The good news: these failures are transient, so the fix is to confirm the outage and make your CI resilient to it.

How to check if Google Artifact Registry is down

Check the official status page: status.cloud.google.com
Look for an active incident affecting image or package pulls in the affected region.
Cross-check community reports (Downdetector, the project status on social/X).
Confirm it is org-wide, not just your job: if every repo that depends on Google Artifact Registry fails at once, it is an outage, not your config.

What it looks like in CI

An outage usually surfaces as a transient network or 5xx error while talking to Google Artifact Registry:

Typical CI log

unexpected status from HEAD request to https://...-docker.pkg.dev/...: 503 Service Unavailable

Outage vs your own bug

Outage: many repos fail at once, errors are network/5xx/timeouts, no recent change on your side.
Your bug: one repo, a specific error, started right after a change you made.

How to keep CI green during a blip

Add retry-with-backoff around the step that hits Google Artifact Registry - most blips pass within a minute.
Check the specific region; mirror hot images to a second registry and retry transient pulls.
Cache dependencies and artifacts so a brief outage does not block jobs that could run from cache.
Avoid mass "re-run all" during an incident - it piles up when the service recovers.

Key takeaways

Check status.cloud.google.com first; org-wide failures = outage, not your config.
Google Artifact Registry blips are transient network/5xx errors.
Retries, caching, and a fallback keep CI green through a hiccup.

Frequently asked questions

Why does a Google Artifact Registry outage fail my whole pipeline?

Most CI steps hit Google Artifact Registry with a single attempt and no retry, so one failed request fails the job. Adding retries or self-healing runners turns a momentary blip into a non-event.