Is Maven Central Repository down right now?

No. Our checks are finding no problems with Maven Central Repository right now. That verdict is live, and the banner at the top of this page carries it too. We re-check Maven Central Repository continuously using its official status feed, direct network probes and reports from visitors, stopping at the first check that gives a clear answer, and the page updates itself as soon as anything changes. A green verdict does not rule out a fault affecting only some users or regions.

The problems visitors report most often on this page are downloads failing, clone / push failing, builds / pipelines stuck, slow or laggy, can't connect, no response / timing out, API errors and 5xx error pages. Those are the options the report button offers for Maven Central Repository, chosen for how this service actually fails rather than a generic list, and the "user reports" chart above breaks down which ones people are picking right now.

Our checks run from one place on the internet, so a fault limited to your region or network can be real while our probes succeed. With Maven Central Repository specifically, Maven Central has regional mirrors and CDN nodes that can fail independently, and your local Maven cache may be stale or corrupted, causing lookups to fail even when the primary repository is reachable. That is why this page reports what it observed rather than declaring the service healthy, and why reports from other visitors count toward the verdict.

For Maven Central Repository, try downloading a small well-known artifact directly using curl against repo.maven.apache.org, such as `curl -I https://repo.maven.apache.org/maven2/junit/junit/4.13.2/junit-4.13.2.jar`. A problem that follows you across networks and devices is very unlikely to be yours.

If this page shows evidence of problems, the fault is most likely on Maven Central Repository's side. Specifically: do not repeatedly retry builds, as this floods the repository with requests and can trigger rate limiting or temporary blocks on your IP address, making recovery slower for everyone. Reporting it here helps other people see they are not alone.

Continuously, around the clock. Maven Central Repository does not publish a machine-readable status feed, so we cannot read a verdict from them. We probe repo.maven.apache.org directly over HTTP, fall back to an ICMP ping if that is inconclusive, and weigh reports from visitors. That means we can tell you the service is unreachable, but not what Maven Central Repository says about it. The verification tier box on this page names whichever check produced the verdict you are reading, so you can see how direct the evidence is.

Yes, at status.maven.org, and it is linked further up this page. That is Maven Central Repository's own account of their service and it is the place to look for their estimate of a fix. We read it where we can, but we publish our own observations beside it rather than only repeating theirs, because an operator's status page can lag a problem their users are already hitting.

No. status.buzz is an independent monitoring site operated by LuzLab LLC, with no connection to Maven Central Repository or repo.maven.apache.org. It reads publicly available endpoints and status feeds, and publishes what it observed. For account or billing problems you need Maven Central Repository's own support, not us.