Gradle 장애 기록

1. 2026년 10월 22일 오후 2:35 UTCidentified

   Develocityctl CLI 및 Test Distribution Agent와 같은 일부 문서 및 다운로드는 현재 사용할 수 없습니다. 뿌리 원인은 식별되어 mitigated 것입니다.

2. 2026년 10월 22일 오후 2:47 UTCidentified

   이 문제를 해결하기 위해 계속 노력하고 있습니다.

3. 2026년 10월 23일 오전 11:44 UTCresolved

   모든 누락된 페이지 및 다운로드가 복원되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 5월 6일 오전 9:56 UTCresolved

   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.

1. 2025년 12월 5일 오전 9:09 UTCinvestigating

   We are following up news from Cloudflare

2. 2025년 12월 5일 오전 9:12 UTCinvestigating

   Listing more impacted services, although recovery might be in progress

3. 2025년 12월 5일 오전 9:16 UTCmonitoring

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

4. 2025년 12월 5일 오전 10:01 UTCresolved

   Services are back to normal

1. 2025년 8월 22일 오전 8:06 UTCresolved

   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.

1. 2025년 8월 12일 오후 9:11 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 8월 12일 오후 9:13 UTCidentified

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

3. 2025년 8월 12일 오후 9:13 UTCmonitoring

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

4. 2025년 8월 12일 오후 9:25 UTCresolved

   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.

1. 2025년 4월 25일 오후 3:33 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 4월 25일 오후 3:50 UTCresolved

   This incident has been resolved.

1. 2024년 7월 23일 오후 7:43 UTCinvestigating

   We are currently investigating this issue.

2. 2024년 7월 23일 오후 8:00 UTCresolved

   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.

1. 2024년 5월 23일 오전 8:32 UTCresolved

   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.

1. 2024년 2월 1일 오전 10:16 UTCinvestigating

   We are currently investigating the issue. Traffic against the plugin portal has increased heavily this week, with a serious uptake in traffic from user agents identifying as Renovate and some specific source IPs having increased traffic from nearly nothing to multiple millions requests an hour. We have enforced rate limiting for the worst offender.

2. 2024년 2월 1일 오후 12:53 UTCmonitoring

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

3. 2024년 2월 1일 오후 4:41 UTCresolved

   This incident has been resolved. We will continue to monitor the system in the coming days.

1. 2024년 1월 31일 오후 4:35 UTCinvestigating

   We are currently investigating this issue.

2. 2024년 1월 31일 오후 4:47 UTCmonitoring

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

3. 2024년 2월 1일 오전 8:45 UTCresolved

   This incident has been resolved. We will continue close monitoring of the system in the coming days.

1. 2023년 6월 23일 오전 9:14 UTCinvestigating

   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.

2. 2023년 6월 23일 오후 6:48 UTCmonitoring

   JCenter is now serving artifacts again. We're monitoring if this has resolved the situation and we'll provide more information later.

3. 2023년 6월 23일 오후 8:51 UTCresolved

   This incident has been resolved.

1. 2023년 3월 27일 오전 11:03 UTCinvestigating

   We are currently investigating this issue.

2. 2023년 3월 27일 오전 11:30 UTCidentified

   We continue looking into the issue. We disabled uploading of new plugins to the plugin portal for the time being.

3. 2023년 3월 27일 오후 6:30 UTCidentified

   We are continuing to investigate slow response times and errors on https://plugins.gradle.org. New account creation and plugin uploads are still disabled.

4. 2023년 3월 27일 오후 9:53 UTCmonitoring

   A fix has been implemented and we're monitoring the impact on the Plugin Portal. We are still seeing above average response times, but overall timeouts are down. New account creation and plugin uploads have been re-enabled.

5. 2023년 3월 28일 오후 1:46 UTCmonitoring

   We are seeing increased load and timeouts again. We're investigating the cause.

6. 2023년 3월 29일 오후 1:20 UTCmonitoring

   We've deployed another fix and are monitoring the impact.

7. 2023년 3월 29일 오후 3:36 UTCresolved

   This incident has been resolved.

1. 2023년 3월 20일 오전 9:08 UTCinvestigating

   The plugin portal is encountering issues with JCenter right now. We are seeing "Remote host terminated the handshake". Investigating and reaching out to JFrog.

2. 2023년 3월 20일 오전 9:18 UTCmonitoring

   JCenter is now accepting connections, we are monitoring the situation.

3. 2023년 3월 20일 오전 9:19 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2023년 3월 20일 오전 10:13 UTCresolved

   This incident has been resolved.

1. 2022년 11월 26일 오전 7:24 UTCinvestigating

   JCenter has expired SSL certificates, the Plugin Portal now uses Maven Central has its backing repository. This will cause issue for libraries that are available on JCenter but not Maven Central. This can include older versions of plugins.

2. 2022년 11월 26일 오후 3:50 UTCresolved

   JCenter's certificate has been renewed.

1. 2022년 11월 7일 오후 7:08 UTCinvestigating

   We are currently investigating this issue.

2. 2022년 11월 7일 오후 7:12 UTCmonitoring

   The issue appears to be upstream. We're monitoring for failures and will take action if failures increase.

3. 2022년 11월 7일 오후 11:58 UTCmonitoring

   We received more reports that some dependency downloads are failing from jcenter.bintray.com. For now, we've changed the backend to redirect to Maven Central. You may notice some redirects to JCenter for the next few hours until caches expire. Unfortunately, this means artifacts that were only available on JCenter/Bintray and were never migrated to Maven Central will not be available from the Plugin Portal. If you are using dependency verification, you may also notice different artifact checksums for libraries that were re-uploaded to Maven Central. We'll continue to monitor the situation.

4. 2022년 11월 8일 오후 4:01 UTCmonitoring

   We've restored the redirect to JCenter. You may notice some redirects to Maven Central for the next few hours until caches expire. We will continue to monitor for increased failures.

5. 2022년 11월 8일 오후 7:59 UTCresolved

   This incident has been resolved.

1. 2022년 10월 31일 오전 9:56 UTCidentified

   While the mirroring put in place alleviates some of the JCenter being down impact, the mirror is a bit out of date and currently cannot sync recent artifacts. This continues to impact builds.

2. 2022년 10월 31일 오후 1:26 UTCresolved

   The new settings have resolved most of the issues. Note that you may still experience problems if the package only exists on JCenter and was never mirrored until now.

1. 2022년 10월 31일 오전 7:07 UTCidentified

   JCenter has had issues a good part of Sunday October 30th and continues to have issues this morning. A temporary solution has been put in place to reduce the impact on users of the Gradle Plugin Portal.

2. 2022년 10월 31일 오전 8:08 UTCresolved

   Impacts from the JCenter issue should be resolved. We will keep monitoring the situation.

1. 2022년 8월 24일 오전 12:29 UTCidentified

   The plugins.gradle.org service depends on the Heroku hosting platform, which is currently suffering a widespread outage affecting DNS resolution. We are currently investigating options and tracking the root cause Heroku outage.

2. 2022년 8월 24일 오전 12:54 UTCidentified

   Temporary mitigation has been put in place to restore service. As the upstream Heroku outage evolves, further downtime may be experienced.

3. 2022년 8월 24일 오전 12:57 UTCmonitoring

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

4. 2022년 8월 24일 오전 6:31 UTCresolved

   This incident has been resolved.

1. 2022년 6월 21일 오전 7:24 UTCinvestigating

   We are currently investigating this issue.

2. 2022년 6월 21일 오전 7:55 UTCmonitoring

   We have identified that our communication with S3 in the backend was showing an increased error rate. This had an effect on response time for the plugin portal. Our logging shows that the error rate is back to normal. We will continue to monitor the service closely for a bit longer.

3. 2022년 6월 21일 오전 8:10 UTCresolved

   The root cause was the Cloudflare outage - see https://www.cloudflarestatus.com/incidents/xvs51y9qs9dj - which is now resolved.

1. 2022년 4월 29일 오후 1:00 UTCinvestigating

   We are currently investigating this issue.

2. 2022년 4월 29일 오후 2:25 UTCinvestigating

   A change is being deployed with expectations that it will improve the situation.

3. 2022년 4월 29일 오후 4:27 UTCresolved

   This incident has been resolved.