Vendor Status Watch

← all vendors

Gradle status history

Current state: operational — “All Systems Operational” per https://status.gradle.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

0incidents, last 30 days
0incidents, last 90 days
4incidents on record

How long do Gradle incidents last?

32 minmedian incident duration4 measured
60 min90th percentile1 in 10 ran longer
32 minmedian, major/critical only2 incidents

From 4 incidents with a vendor-posted start and resolve time. Longest on record: Connection issues on the Gradle Plugin Portal — 60 min (2025-08-21 17:30 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (4)

StartedIncidentStatusImpactDuration
2026-05-06 09:00 UTCFailed upgrade on the Plugin Portalresolvednone0 min
2025-12-05 09:09 UTCPlugin portal unreachable due to Cloudflare having issuesresolvedcritical51 min
2025-08-21 17:30 UTCConnection issues on the Gradle Plugin Portalresolvednone1 h 00 min
2025-08-12 21:11 UTCGradle distribution downloads are failingresolvedcritical14 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Gradle with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "gradle"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}