Home
/
Status
/
Service
Build automation and testing tool for developers.
Source
auto
Category
Development
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 3m ago
16
Components
0
Active incidents
0
Maintenance
20%
90d uptime
Failed upgrade on the Plugin Portal
May 6, 9:00 AM
Normalized official status-page data for incidents, maintenance, components, and history.
20%
Known uptime
5 known history days
16
Components tracked
0 outage, 0 degraded
49
Incidents indexed
0 active right now
9
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
Develocity (gradle.com)
Operational
Public Build Scan service (scans.gradle.com)
Operational
Gradle Plugin portal (plugins.gradle.org)
Operational
Heroku
Operational
DPE University (dpeuniversity-develocity.gradle.com)
Operational
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
1
operational days
1
degraded days
1
outage days
2
maintenance days
85
unknown days
Latest outages and degradations detected from the official status page.
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.
Services are back to normal
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.
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.
This incident has been resolved.
This incident has been resolved. Between 19:14 and 19:36 UTC the Plugin Portal UI experienced degraded performance and had a small portion of requests fail with errors.
On May 23, from 7:42 AM UTC to 8 AM, the Plugin Portal was unavailable following a failed maintenance operation. Service has been restored successfully.
This incident has been resolved. We will continue to monitor the system in the coming days.
This incident has been resolved. We will continue close monitoring of the system in the coming days.
This incident has been resolved.
Scheduled and completed maintenance windows are separated from incidents.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
During the course of this 24 hour trial period we ended up blocking just under 513k HTTP requests against our various [gradle.org](http://gradle.org) domains which is ~1.2% of our traffic. During this time we did see a decrease in the number of requests using HTTP instead HTTPS. Gradle has also officially dropped support for TLSv1.0 across all of our domains. TLSv1.3 was enabled yesterday but due to a race condition bug the TLSv1.3 logic in early versions of JDK 11 and JDK 12 we have decided to turn off TLSv1.3 support for the time being. [https://bugs.openjdk.java.net/browse/JDK-8213202](https://bugs.openjdk.java.net/browse/JDK-8213202) Overall, we believe this test was a success and plan on moving forward with the planned decommission of HTTP on January 15th, 2020.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Database Upgrade completed successfully at 00:32 UTC. All systems operational.
Uptimus tracks the official Gradle status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.gradle.com
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Showing 1 to 16 of 16 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
Gradle Plugin portal (plugins.gradle.org) The central repository of community contributed Gradle plugins. | Operational | Group | 6/19/2026 |
Develocity (gradle.com) | Operational | Group | 6/18/2026 |
Gradle Build Tool (gradle.org) | Operational | Group | Not recorded |
Downloads (services.gradle.org) Serves the Gradle Build Tool binaries for manual download, and via the Gradle wrapper. | Operational | Component | Not recorded |
Public Build Scan service (scans.gradle.com) Receives build data from Gradle builds and presents build scans. | Operational | Component | 6/18/2026 |
User Interface Searching and viewing plugin information. | Operational | Component | Not recorded |
DPE University (dpeuniversity-develocity.gradle.com) | Operational | Component | Not recorded |
Documentation (docs.gradle.org) The user documentation for the Gradle Build Tool. | Operational | Component | Not recorded |
Repository Provides the plugin binaries and metadata required to use the plugins in builds. | Operational | Component | Not recorded |
Docker registry (registry.gradle.com) The Docker registry for Gradle Enterprise image repositories and Gradle Enterprise airgap bundles. | Operational | Component | Not recorded |
Gradle Enterprise instance (ge.gradle.org) | Operational | Component | Not recorded |
Helm repository (helm.gradle.com) The Helm repository for Gradle Enterprise Helm charts. | Operational | Component | Not recorded |
Heroku | Operational | Component | 6/19/2026 |
Gradle's Maven Central redirect Gradle redirects non-plugin requests to Maven Central https://status.maven.org/ | Operational | Component | Not recorded |
License server (harbor.gradle.com) | Operational | Component | Not recorded |
Documentation (docs.gradle.com) The user documentation for Gradle Enterprise. | Operational | Component | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
Related status pages based on category, adapter type, and operational history.
Gradle is currently marked as Operational in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.
