Gradle Outage History

Gradle is up right now

Pingoru has recorded 49 incidents for Gradle: 3 in the last 12 months and 1 in the last 90 days.

Source: status.gradle.com

49incidents recorded
3last 12 months
1last 90 days
8 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct4%
Pingoru began tracking Gradle in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202610 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 2026122 of 543 (4%)

Incidents, newest first

Major October 22, 2026 Partial documentation and downloads outage 22h 8m Documentation (docs.gradle.com)

Started Oct 22, 2026, 01:35 PM UTC· resolved Oct 23, 2026, 11:44 AM UTC

  1. identified Oct 22, 2026, 02:35 PM UTC

    Some documentation and downloads, such as the develocityctl CLI and Test Distribution agents, are currently unavailable. The root cause has been identified and is being mitigated.

  2. identified Oct 22, 2026, 02:47 PM UTC

    We are continuing to work on a fix for this issue.

  3. resolved Oct 23, 2026, 11:44 AM UTC

    All missing pages and downloads have been restored.

Read the full incident report →

Notice May 6, 2026 Failed upgrade on the Plugin Portal 20m

Started May 06, 2026, 09:00 AM UTC· resolved May 06, 2026, 09:20 AM UTC

  1. resolved May 06, 2026, 09:56 AM UTC

    While trying to deploy an upgrade, the application was down for 20 minutes from 11:19 GMT+2. We will investigate the root cause and attempt the upgrade at a later date.

Read the full incident report →

Critical December 5, 2025 Plugin portal unreachable due to Cloudflare having issues 51m Public Build Scan service (scans.gradle.com), Downloads (services.gradle.org), User Interface, Repository and 5 more

Started Dec 05, 2025, 09:09 AM UTC· resolved Dec 05, 2025, 10:01 AM UTC

  1. investigating Dec 05, 2025, 09:09 AM UTC

    We are following up news from Cloudflare

  2. investigating Dec 05, 2025, 09:12 AM UTC

    Listing more impacted services, although recovery might be in progress

  3. monitoring Dec 05, 2025, 09:16 AM UTC

    Cloudflare implemented a fix and services seem to be back https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q

  4. resolved Dec 05, 2025, 10:01 AM UTC

    Services are back to normal

Read the full incident report →

Notice August 21, 2025 Connection issues on the Gradle Plugin Portal 1h

Started Aug 21, 2025, 05:30 PM UTC· resolved Aug 21, 2025, 06:30 PM UTC

  1. resolved Aug 22, 2025, 08:06 AM UTC

    The plugin portal suffered connection issues possibly related to incidents with the different providers used: * Heroku: https://status.heroku.com/incidents/2867 * AWS: https://health.aws.amazon.com/health/status?eventID=arn:aws:health:us-east-1::event/INTERNETCONNECTIVITY/AWS_INTERNETCONNECTIVITY_OPERATIONAL_ISSUE/AWS_INTERNETCONNECTIVITY_OPERATIONAL_ISSUE_49824_16DD211EFC1 When restarted, the application started behaving properly.

Read the full incident report →

Critical August 12, 2025 Gradle distribution downloads are failing 14m Downloads (services.gradle.org)

Started Aug 12, 2025, 09:11 PM UTC· resolved Aug 12, 2025, 09:25 PM UTC

  1. investigating Aug 12, 2025, 09:11 PM UTC

    We are currently investigating this issue.

  2. identified Aug 12, 2025, 09:13 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Aug 12, 2025, 09:13 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Aug 12, 2025, 09:25 PM UTC

    services.gradle.org is fully operational again. The outage was caused by a configuration change on services.gradle.org that was not intended to affect this service.

Read the full incident report →

Critical April 25, 2025 Plugin portal is down 16m User Interface, Repository, Gradle's Maven Central redirect

Started Apr 25, 2025, 03:33 PM UTC· resolved Apr 25, 2025, 03:50 PM UTC

  1. investigating Apr 25, 2025, 03:33 PM UTC

    We are currently investigating this issue.

  2. resolved Apr 25, 2025, 03:50 PM UTC

    This incident has been resolved.

Read the full incident report →