CheckUpstream does not yet run an independent probe against Maven Central, so no availability figure is published for it — only Maven Central's own disclosure record below. 41 incidents were recorded in the past 12 months; the most recent resolved 11 days ago after 3 hours. Status signals are polled from Maven Central's official Atlassian Statuspage status page, alongside independent probes and community reports.
Independent measurement how this is computed
Not measured
We run no independent probe against Maven Central yet, so we publish no availability figure for it. What follows is Maven Central's own disclosure record, which is a different thing.
Vendor disclosed: 38 incidents · 173 of 180 days with none posted · 8h 12m of declared impact
Fewer incidents in the last 30 days than 45% of 232 tracked services.
Share of each window with no impact declared by Maven Central
7d
100.000%
30d
99.527%
90d
99.792%
180d
99.810%
1y
99.906%
Downtime like this can be refundable
If you're a paying Maven Central customer, outages in these windows may count against Maven Central's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Maven Central entitlement →Does Maven Central actually matter to you?
A Maven Central outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →From 38 incidents Maven Central published and resolved in the last 180 days, measured between their own start and resolution times. It describes how long Maven Central takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Live Maven Central status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/maven-central)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Maven Central is currently Operational. CheckUpstream tracks Maven Central in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Looking for the live "is Maven Central down" view? See the Maven Central Live status page.
Jul 21, 10:36 UTC · resolved in 5h 3m · Resolved
Jun 22, 13:52 UTC · resolved in 1h 17m · Resolved
Jun 22, 12:05 UTC · resolved in 1h 4m · Resolved
Jun 22, 11:23 UTC · resolved in 47m · Resolved
Jun 22, 09:40 UTC · resolved in 1h 49m · Resolved
Jun 22, 05:54 UTC · resolved in 1h 6m · Resolved
Jun 22, 01:10 UTC · resolved in 49m · Resolved
Jun 21, 22:24 UTC · resolved in 40m · Resolved
Jun 19, 15:30 UTC · resolved in 10m · Resolved
Jun 19, 10:38 UTC · resolved in 1h 11m · Resolved
Jun 19, 08:38 UTC · resolved in 2h 2m · Resolved
Maven Central's last resolved incident started 11 days ago and lasted 3h 24m (a complete outage).
We don't publish one. CheckUpstream runs no independent probe against Maven Central yet, and the only other figure available would be derived from Maven Central's own incident posts — which measures how much a vendor discloses rather than how available it was. Vendors that post often score worse than vendors that stay quiet, so the number would be backwards.
Sign up to CheckUpstream and add Maven Central to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Maven Central's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.