Outage in Gradle

JCenter no longer serves files but redirects to Maven Central instead

Resolved Major
June 23, 2023 - Started over 2 years ago - Lasted about 12 hours
Official incident page

Incident Report

Without any prior announcement, it looks like JCenter is now redirecting to Maven Central instead of serving artifacts. Builds that have build logic that relies on artifacts available only on JCenter and not Maven Central will fail. We are investigating what we can do to mitigate the issue. We also contacted JFrog to understand this change.

Need to monitor Gradle outages?

One place to monitor all your cloud vendors.
Get instant alerts when an outage is detected.

Latest Updates ( sorted recent to last )
RESOLVED over 2 years ago - at 06/23/2023 08:51PM

This incident has been resolved.

MONITORING over 2 years ago - at 06/23/2023 06:48PM

JCenter is now serving artifacts again.

We're monitoring if this has resolved the situation and we'll provide more information later.

INVESTIGATING over 2 years ago - at 06/23/2023 09:14AM

Without any prior announcement, it looks like JCenter is now redirecting to Maven Central instead of serving artifacts.

Builds that have build logic that relies on artifacts available only on JCenter and not Maven Central will fail.

We are investigating what we can do to mitigate the issue. We also contacted JFrog to understand this change.

The Status Page Aggregator with Early Outage Detection

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 5350 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook