Is Gradle Down Right Now? Check if there is a current outage ongoing.

This incident has been resolved.

We are currently investigating this issue.

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.

We are currently investigating this issue.

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.

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

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.

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

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

We are currently investigating this issue.

This incident has been resolved.

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

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.

This incident has been resolved.

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

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

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.

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

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

We are currently investigating this issue.

This incident has been resolved.

We are continuing to monitor for any further issues.

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

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

JCenter's certificate has been renewed.

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.

This incident has been resolved.

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.

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.

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

We are currently investigating this issue.

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.

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.

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

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.

This incident has been resolved.

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

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

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.

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

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.

We are currently investigating this issue.

This incident has been resolved.

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

We are currently investigating this issue.

This incident has been resolved.

Currently no Build Scan activation emails are sent when activating a Build Scan. We are currently investigating together with the mail provider what the issue is that emails are not sent. Build Scan ingestion works and all build scans can be viewed once the activation email service is functional again.

This incident has been resolved.

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

We are currently investigating this issue.

For 2.5 hours, the Gradle plugin portal was having issue serving artifacts from JCenter. This also caused maven-metadata.xml, used for dynamic version ranges, to fail to resolve.

This incident has been resolved.

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

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

We are currently investigating this issue.

This incident has been resolved.

We are monitoring the stability of the plugin portal.

The plugin portal is experiencing a very high number of requests for non-existent artifacts.

We are continuing to investigate. The web UI (https://plugins.gradle.org) and plugin downloads are sporadically unavailable.

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved.

Looks like the service is available again, we will keep monitoring the situation.

We are continuing to investigate this issue.

Connections to plugins.gradle.org are failing. At first sight, this seems to be related to an underlying Heroku outage. We are investigating further

This incident has been resolved.

The plugin portal is now using JCenter directly until the situation on the mirror is resolved.

The mirror of JCenter used by the plugin portal seems to have increased response time for serving artifacts.

From 2.30 PM UTC to around 4.40 PM UTC, instability in our JCenter mirror and JCenter itself caused disruption for plugin and plugin dependency resolution on the plugin portal.

Postmortem can be found at [https://blog.gradle.org/plugins-jcenter](https://blog.gradle.org/plugins-jcenter)

JCenter is now back online, systems are fully operational.

We have deployed a second fix that should resolve another set of issues encountered by the JCenter outage. What will remain broken: - Dependencies that only exist in JCenter and were not mirrored to one of Gradle’s repository manager. There is no solution for those unfortunately until JCenter comes back up. We will do a post-mortem and explain our plan to remove that dependency altogether later this week.

Issue with resolution of `maven-metadata.xml` for plugins hosted on the Gradle Plugin Portal should be resolved. However regular library dependencies of plugins will still fail to resolve because of the underlying failure of JCenter. We are looking at a solution for this as well.

We have a temporary fix being validated in development right now which should resolve a number of issues. We’ll update here when it is deployed so that we can assess whether or not it is enough to get going for now. We will work on a more permanent solution after that in the coming days.

We are continuing to investigate this issue.

We are currently investigating this issue.

JCenter had an invalid certificate for less than an hour today causing interactions with the Gradle Plugin Portal to fail. This now seems resolved.

This incident has been resolved.

We are continuing to monitor for any further issues.

The issue on the JCenter side seems to have been resolved. There might still be an impact on performance. We will keep monitoring the situation.

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

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

JCenter response time is currently very slow and affects operations on the Gradle plugin portal.

This incident has been resolved.

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

We are currently investigating this issue.

This incident has been resolved.

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

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved.

JCenter requests seem to be working again. We are monitoring to see if the issue returns.

We've identified the root cause to be an outage of JCenter due to their scheduled maintenance. Many of the resource that the Gradle Plugin Portal relies upon are resolved and/or mirrored through to JCenter.

We are continuing to investigate this issue.

This may be partially related to the ongoing JCenter Scheduled Maintenance. We are actively investigating the root cause. https://status.bintray.com/incidents/286206vrzm1x

This incident has been resolved.

This issue originates with JCenter Bintray. Many of our plugin requests are mirrored through to JCenter. https://status.bintray.com/incidents/6g51h2w0s2gw

We are currently investigating this issue.

Looking at our cloudflare analytics, this issue looks to be resolved.

We are currently in discussions with both Cloudflare and Heroku around this issue. Exploring our logs, this issue seems to have resolved itself as of 12:30 PM EDT. We are continuing to monitor the issue to verify that it doesn't occur again.

We are currently investigating this issue.

This incident has been resolved.

We are currently facing an issue sending build scan activation emails. Users who have previously activated a build scan and that are using the 'Remember me' functionality are unaffected.

Plugin publishing has been restored. New user accounts that were created in the last 12 hours may need to regenerate the publishing keys for their profile. We're sorry for the inconvenience.

We are investigating an issue with plugin publishing keys. Plugin publishing will not work during the outage.

This incident has been resolved.

There was only a single crash in the last 24 hours. We've deployed a fix to prevent the application from crashing and we're now monitoring for the situation that was causing the crash.

We're still seeing intermittent failures that cause the Plugin Portal application to crash and restart. These outages typically last seconds, but they may be sustained for several minutes if the application restarts multiple times. The failure is particular hard to catch and diagnose because it occurs in our logging framework. We believe we're seeing an instance of https://jira.qos.ch/browse/LOGBACK-1027. We've deployed a change to the Plugin Portal to capture more information and are working on deploying a workaround. Thank you for your patience.

We are currently investigating this issue.

An update of the Plugin Portal needed to be reverted. This incident has been resolved.

We've identified the problem and rollbacked to the last working version of the plugin portal. Service should be back to normal. We'll update here if we expect another outage.

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved.

Earlier today, all plugin requests to the plugin portal experienced high response times. Normal response times are <100ms, while response times during the incident were nearly 20 seconds. The database used by the plugin portal was experiencing load throttling, which slowed down all operations with the plugin portal. A new database was provisioned and the plugin portal application was redeployed to use the new database. After the migration, all response times returned to normal. We will monitor the plugin portal, but we believe the issue has been resolved. To limit your organization's exposure to plugin portal outages, please consider mirroring the plugin portal. https://plugins.gradle.org/docs/mirroring

This incident has been resolved.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are currently investigating this issue.

Update complete

App is currently being updated.

This issue has been resolved.

Some emails are failing to send due to connectivity issues with Mandrill. See http://status.mandrillapp.com/ for details. This affects build scan activation emails and Gradle Enterprise trial requests. We are monitoring the situation and will update this page when the service is fully operational again.

Database maintenance complete

scans.gradle.com is undergoing scheduled database maintenance. Expected downtime roughly 30 mins

Response times from Bintray have returned to near-normal levels, and the vast majority of builds should no longer be impacted. We will consider this resolved, and continue monitoring for any changes.

Timeouts contacting Bintray's servers have reduced significantly over the past 2 hours. We are continuing monitoring.

Many plugins are hosted on Bintray and fail to resolve with an HTTP 502 error. See http://status.bintray.com/ for details. We are monitoring the situation and will update this page when the service is fully operational again.

An upgrade of an internal component caused errors for plugin authors publishing to the portal. The error has been resolved and our automated testing has been improved to prevent similar errors in the future.

Some users have reported that they are receiving an unauthorized response when trying to publish new versions of their Gradle Plugins. See https://discuss.gradle.org/t/gradle-publish-plugin-keys-not-working for details.

This incident has been resolved.

HTTP access has been restored.

Some users are reporting that they are unable to download Gradle distributions over HTTP https://github.com/gradle/gradle/issues/1573

This incident has been resolved.

We are experiencing some issues with some of our online services due to the ongoing issues with Amazon S3 services. We are monitoring the situation and will provide and update when services are restored.

This incident has been resolved.

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

https://www.cloudflarestatus.com/incidents/nmcvfb923w0b