Skip to content

Outage tracker / Maven Central

Is Maven Central down?

I'm having a problem

Vendor reports no incidentWhat Maven Central reports

Maven Central reports no incident on its status page.

As of the last successful poll, 2026-11-05 15:01 UTC.

Maven Central's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Partially degradedchecked 6 minutes ago

Maven Central is answering our probes, but its web surface is running at least 1.3x its 7-day median from South America and Asia-Pacific and its API is running at least 3.7x its 7-day median from South America and Asia-Pacific. Everything else we check answered at its usual speed.

As of Nov 5, 2026, 3:08 PM UTC, RealUptime's checks of Maven Central passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 3:08 PM UTC
US-East640 msChecks passing
US-West544 msChecks passing
Europe332 msChecks passing
Asia-Pacific1143 msDegraded
US-Central666 msChecks passing
Canada144 msChecks passing
UK297 msChecks passing
Southeast Asia1173 msChecks passing
Australia2453 msChecks passing
South America874 msDegraded
their status pagetheir claim, not our reading

Maven Central reports: All systems operational (“All Systems Operational”)

from Maven Central's own status page, checked Nov 5, 2026, 2:27 PM UTC
Maven Central's own status page shows no incident, and our checks of Maven Central pass right now.

Maven Central's own component breakdown, as they publish it

  • CDN - repo1.maven.orgOperational
  • Portal - central.sonatype.comOperational
  • Portal - central.sonatype.com (SNAPSHOTs)Operational
  • Legacy Search - search.maven.orgOperational
  • Cloudflare CDN/CacheOperational

These are Maven Central's components, named and scored by Maven Central. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Maven Central's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Maven Central response time, by region

US-East
1.3sp95 · latest
5s2.5s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 617ms2026-10-08 UTC: p95 532ms2026-10-09 UTC: p95 574ms2026-10-10 UTC: p95 575ms2026-10-11 UTC: p95 624ms2026-10-12 UTC: p95 562ms2026-10-13 UTC: p95 649ms2026-10-14 UTC: p95 548ms2026-10-15 UTC: p95 527ms2026-10-16 UTC: p95 638ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 563ms2026-10-23 UTC: p95 634ms2026-10-24 UTC: p95 629ms2026-10-25 UTC: p95 632ms2026-10-26 UTC: p95 2.8s2026-10-27 UTC: p95 1.0s2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 1.1s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 2.1s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5
US-West
1.2sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 409ms2026-10-08 UTC: p95 495ms2026-10-09 UTC: p95 464ms2026-10-10 UTC: p95 494ms2026-10-11 UTC: p95 431ms2026-10-12 UTC: p95 464ms2026-10-13 UTC: p95 657ms2026-10-14 UTC: p95 495ms2026-10-15 UTC: p95 484ms2026-10-16 UTC: p95 516ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 4.5s2026-10-23 UTC: p95 627ms2026-10-24 UTC: p95 755ms2026-10-25 UTC: p95 750ms2026-10-26 UTC: p95 633ms2026-10-27 UTC: p95 331ms2026-10-28 UTC: p95 978ms2026-10-29 UTC: p95 486ms2026-10-30 UTC: p95 684ms2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 1.3s2026-11-02 UTC: p95 2.0s2026-11-03 UTC: p95 2.4s2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
Europe
1.4sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 613ms2026-10-08 UTC: p95 475ms2026-10-09 UTC: p95 502ms2026-10-10 UTC: p95 465ms2026-10-11 UTC: p95 380ms2026-10-12 UTC: p95 466ms2026-10-13 UTC: p95 363ms2026-10-14 UTC: p95 314ms2026-10-15 UTC: p95 375ms2026-10-16 UTC: p95 346ms2026-10-17 UTC: p95 531ms2026-10-18 UTC: p95 666ms2026-10-19 UTC: p95 901ms2026-10-20 UTC: p95 742ms2026-10-21 UTC: p95 707ms2026-10-22 UTC: p95 281ms2026-10-23 UTC: p95 398ms2026-10-24 UTC: p95 402ms2026-10-25 UTC: p95 430ms2026-10-26 UTC: p95 471ms2026-10-27 UTC: p95 405ms2026-10-28 UTC: p95 342ms2026-10-29 UTC: p95 342ms2026-10-30 UTC: p95 526ms2026-10-31 UTC: p95 464ms2026-11-01 UTC: p95 521ms2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 939ms2026-11-04 UTC: p95 1.7s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
Asia-Pacific
2.1sp95 · latest
10s5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 850ms2026-10-08 UTC: p95 804ms2026-10-09 UTC: p95 762ms2026-10-10 UTC: p95 884ms2026-10-11 UTC: p95 791ms2026-10-12 UTC: p95 783ms2026-10-13 UTC: p95 711ms2026-10-14 UTC: p95 792ms2026-10-15 UTC: p95 726ms2026-10-16 UTC: p95 830ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.8s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.6s2026-10-23 UTC: p95 2.0s2026-10-24 UTC: p95 1.9s2026-10-25 UTC: p95 1.8s2026-10-26 UTC: p95 1.9s2026-10-27 UTC: p95 5.6s2026-10-28 UTC: p95 741ms2026-10-29 UTC: p95 547ms2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 600ms2026-11-01 UTC: p95 452ms2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.7s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5
US-Central
1.2sp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 334ms2026-10-08 UTC: p95 270ms2026-10-09 UTC: p95 320ms2026-10-10 UTC: p95 365ms2026-10-11 UTC: p95 313ms2026-10-12 UTC: p95 248ms2026-10-13 UTC: p95 268ms2026-10-14 UTC: p95 328ms2026-10-15 UTC: p95 308ms2026-10-16 UTC: p95 412ms2026-10-17 UTC: p95 325ms2026-10-18 UTC: p95 288ms2026-10-19 UTC: p95 350ms2026-10-20 UTC: p95 248ms2026-10-21 UTC: p95 338ms2026-10-22 UTC: p95 667ms2026-10-23 UTC: p95 777ms2026-10-24 UTC: p95 609ms2026-10-25 UTC: p95 774ms2026-10-26 UTC: p95 671ms2026-10-27 UTC: p95 349ms2026-10-28 UTC: p95 854ms2026-10-29 UTC: p95 726ms2026-10-30 UTC: p95 588ms2026-10-31 UTC: p95 960ms2026-11-01 UTC: p95 930ms2026-11-02 UTC: p95 776ms2026-11-03 UTC: p95 922ms2026-11-04 UTC: p95 988ms2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
Canada
430msp95 · latest
2.5s1.3s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 371ms2026-10-08 UTC: p95 574ms2026-10-09 UTC: p95 443ms2026-10-10 UTC: p95 448ms2026-10-11 UTC: p95 486ms2026-10-12 UTC: p95 509ms2026-10-13 UTC: p95 443ms2026-10-14 UTC: p95 479ms2026-10-15 UTC: p95 546ms2026-10-16 UTC: p95 386ms2026-10-17 UTC: p95 402ms2026-10-18 UTC: p95 565ms2026-10-19 UTC: p95 538ms2026-10-20 UTC: p95 639ms2026-10-21 UTC: p95 673ms2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 739ms2026-10-24 UTC: p95 715ms2026-10-25 UTC: p95 766ms2026-10-26 UTC: p95 671ms2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 2.0s2026-10-29 UTC: p95 487ms2026-10-30 UTC: p95 531ms2026-10-31 UTC: p95 550ms2026-11-01 UTC: p95 602ms2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 430ms
Oct 7Oct 21Nov 5
UK
516msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 118ms2026-10-08 UTC: p95 151ms2026-10-09 UTC: p95 161ms2026-10-10 UTC: p95 123ms2026-10-11 UTC: p95 137ms2026-10-12 UTC: p95 185ms2026-10-13 UTC: p95 175ms2026-10-14 UTC: p95 164ms2026-10-15 UTC: p95 175ms2026-10-16 UTC: p95 224ms2026-10-17 UTC: p95 164ms2026-10-18 UTC: p95 141ms2026-10-19 UTC: p95 168ms2026-10-20 UTC: p95 303ms2026-10-21 UTC: p95 586ms2026-10-22 UTC: p95 738ms2026-10-23 UTC: p95 276ms2026-10-24 UTC: p95 292ms2026-10-25 UTC: p95 279ms2026-10-26 UTC: p95 291ms2026-10-27 UTC: p95 461ms2026-10-28 UTC: p95 860ms2026-10-29 UTC: p95 132ms2026-10-30 UTC: p95 469ms2026-10-31 UTC: p95 553ms2026-11-01 UTC: p95 314ms2026-11-02 UTC: p95 915ms2026-11-03 UTC: p95 887ms2026-11-04 UTC: p95 813ms2026-11-05 UTC: p95 516ms
Oct 7Oct 21Nov 5
Southeast Asia
1.9sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 736ms2026-10-08 UTC: p95 829ms2026-10-09 UTC: p95 843ms2026-10-10 UTC: p95 945ms2026-10-11 UTC: p95 880ms2026-10-12 UTC: p95 1.0s2026-10-13 UTC: p95 896ms2026-10-14 UTC: p95 961ms2026-10-15 UTC: p95 958ms2026-10-16 UTC: p95 946ms2026-10-17 UTC: p95 879ms2026-10-18 UTC: p95 733ms2026-10-19 UTC: p95 858ms2026-10-20 UTC: p95 716ms2026-10-21 UTC: p95 732ms2026-10-22 UTC: p95 882ms2026-10-23 UTC: p95 889ms2026-10-24 UTC: p95 1.6s2026-10-25 UTC: p95 870ms2026-10-26 UTC: p95 1.5s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 555ms2026-10-30 UTC: p95 981ms2026-10-31 UTC: p95 1.9s2026-11-01 UTC: p95 1.3s2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 1.9s
Oct 7Oct 21Nov 5
Australia
1.7sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 786ms2026-10-08 UTC: p95 669ms2026-10-09 UTC: p95 884ms2026-10-10 UTC: p95 731ms2026-10-11 UTC: p95 913ms2026-10-12 UTC: p95 922ms2026-10-13 UTC: p95 746ms2026-10-14 UTC: p95 769ms2026-10-15 UTC: p95 659ms2026-10-16 UTC: p95 846ms2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 517ms2026-10-23 UTC: p95 425ms2026-10-24 UTC: p95 1.2s2026-10-25 UTC: p95 330ms2026-10-26 UTC: p95 489ms2026-10-27 UTC: p95 350ms2026-10-28 UTC: p95 367ms2026-10-29 UTC: p95 1.8s2026-10-30 UTC: p95 2.2s2026-10-31 UTC: p95 2.3s2026-11-01 UTC: p95 789ms2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 1.7s
Oct 7Oct 21Nov 5
South America
1.4sp95 · latest
20s10s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 20s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 465ms2026-10-08 UTC: p95 330ms2026-10-09 UTC: p95 324ms2026-10-10 UTC: p95 600ms2026-10-11 UTC: p95 647ms2026-10-12 UTC: p95 777ms2026-10-13 UTC: p95 632ms2026-10-14 UTC: p95 739ms2026-10-15 UTC: p95 758ms2026-10-16 UTC: p95 908ms2026-10-17 UTC: p95 798ms2026-10-18 UTC: p95 697ms2026-10-19 UTC: p95 643ms2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 496ms2026-10-23 UTC: p95 10.9s2026-10-24 UTC: p95 305ms2026-10-25 UTC: p95 448ms2026-10-26 UTC: p95 449ms2026-10-27 UTC: p95 725ms2026-10-28 UTC: p95 529ms2026-10-29 UTC: p95 2.5s2026-10-30 UTC: p95 477ms2026-10-31 UTC: p95 361ms2026-11-01 UTC: p95 2.8s2026-11-02 UTC: p95 2.1s2026-11-03 UTC: p95 387ms2026-11-04 UTC: p95 1.6s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5

Check your own site while you wait on Maven Central

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Maven Central. It cannot diagnose Maven Central's own systems.

What we measured, function by function

Maven Central answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Degraded Answering, but 2x slower than its 7-day median.US-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Degraded Answering, but 1.3x slower than its 7-day median.
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Degraded Answering, but 3.7x slower than its 7-day median.US-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Degraded Answering, but 4.2x slower than its 7-day median.
  • Artifact downloadUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Central portalUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Publishing APIUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Maven Central reports an incident on its status page, and again when it reports it resolved.

Get an email when Maven Central reports an incident

Email me when Maven Central reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is Maven Central's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 640msstatus code: 200checked: Nov 5, 2026, 2:49 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Maven Central normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 544msstatus code: 200checked: Nov 5, 2026, 2:42 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Maven Central normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 666msstatus code: 200checked: Nov 5, 2026, 2:45 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Maven Central normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 144msstatus code: 200checked: Nov 5, 2026, 2:39 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Maven Central normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Degradedlatency: 874msstatus code: 200checked: Nov 5, 2026, 2:41 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Maven Central normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 332msstatus code: 200checked: Nov 5, 2026, 2:46 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Maven Central normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 297msstatus code: 200checked: Nov 5, 2026, 2:35 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Maven Central normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    DegradedAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Degradedlatency: 1143msstatus code: 200checked: Nov 5, 2026, 3:08 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Maven Central normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1173msstatus code: 200checked: Nov 5, 2026, 3:00 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Maven Central normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 2453msstatus code: 200checked: Nov 5, 2026, 2:51 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Maven Central normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Maven Central, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Maven Central yet, which is not evidence that nothing is wrong.

Recent probe events

Scheduled Maintenance - SNAPSHOT Publishing Infrastructure Upgrade, 44mdeclared on their status page2026-11-05
repo1.maven.org is down, 3h 21mdeclared on their status page2026-08-21
repo1.maven.org is down, 4mdeclared on their status page2026-07-24
repo1.maven.org is down, 7mdeclared on their status page2026-07-24
repo1.maven.org is down, 1mdeclared on their status page2026-07-24
Delayed publishing to Maven Central, 4h 55mdeclared on their status page2026-07-21
search.maven.org is down, 1h 53mdeclared on their status page2026-07-16
search.maven.org is down, 2mdeclared on their status page2026-07-15

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Maven Central since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Maven Central covering any window you pick, with our check readings and Maven Central's own claim at the time, side by side.

Full check history for Maven Central: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Maven Central uptime by RealUptime's checksLive, from this page's own readings.
[![Maven Central uptime by RealUptime's checks](https://realuptime.io/outages/maven-central/badge.svg?days=30)](https://realuptime.io/outages/maven-central)
<a href="https://realuptime.io/outages/maven-central"><img src="https://realuptime.io/outages/maven-central/badge.svg?days=30" alt="Maven Central uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Maven Central down?", https://realuptime.io/outages/maven-central. The readings change with every check, so give the date you read them.

What we check

primaryfunctional: live API
https://repo1.maven.org/maven2/
secondary
https://repo1.maven.org/maven2/junit/junit/4.13.2/junit-4.13.2.pom
secondary
https://central.sonatype.com/
secondary
https://central.sonatype.com/api/v1/publisher/status

What our check can and cannot see

A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.

Host checked: repo1.maven.org

RealUptime is not affiliated with Maven Central; the name identifies what we checked, and nothing here speaks for Maven Central's own team. We send a single web request to Maven Central from 10 regions on our own schedule and time the response. We do not see inside Maven Central's systems, do not use an account or real transaction, and are not the same signal Maven Central's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Maven Central is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.