Is Maven Central Down? How to Check and Keep Your CI Green

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

When Maven Central has a hiccup, every pipeline that pulls from 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 Maven Central is down

1. Check the official status page: status.maven.org
2. Look for an active incident affecting artifact downloads.
3. Cross-check community reports (Downdetector, the project's status on social/X).
4. Confirm it is org-wide, not just your job: if every repo pulling from Maven Central 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 fetching from Maven Central:

Could not transfer artifact ... Connection timed out
[ERROR] Failed to execute goal ... Could not resolve dependencies

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 Maven Central - most blips pass within a minute.
• Use a repository manager (Nexus/Artifactory) as a caching proxy in front of Central.
• Cache dependencies so a brief outage does not block jobs that could install from cache.
• Avoid mass "re-run all" during an incident - it piles up when the service recovers.

Key takeaways

• Check status.maven.org first; org-wide failures = outage, not your config.
• Maven Central blips are transient network/5xx errors.
• Retries, caching, and a mirror keep CI green through a hiccup.

Frequently asked questions

Related guides