Updates.jenkins.io on Jenkins Status Page

[Resolved] Maintenance on trusted.ci.jenkins.io

Mon, 04 May 2026 09:30:00 +0000

[Final Message] Operation completed successfully, no issue encountered but took 2h30 (a bit longer than expected).

[Initial Message] Monday “May the Fourth” (be with you) 2026, starting at 09:30 UTC, the virtual machine running trusted.ci.jenkins.io will be migrated to a new Azure subscription.

This migration requires a full downtime estimated between 30 minutes and 2 hours. During that time, updates.jenkins.io, www.jenkins.io and javadoc.updates.jenkins.io won’t be updated, along with no new Jenkins CI Docker images will be released. The CD tokens managed by the repository-permission-updated should not impacted as we’ll run the job right before the operation (letting 3 hours before expiration).

See more details at https://github.com/jenkins-infra/helpdesk/issues/5084.

[Resolved] Maintenance on trusted.ci.jenkins.io

Thu, 23 Apr 2026 07:00:00 +0000

[Final Message] Operation completed successfully, no issue encountered.

[Initial Message] Thursday April 23 2026, starting at 07:00 UTC, we’ll switch several jobs of trusted.ci.jenkins.io including the one updating updates.jenkins.io to a new permanent agent.

This operation will require to stop those jobs and disable the current permanent agent for about 3 hours. During that time, updates.jenkins.io won’t be updated, no other disruptions are expected.

See more details at https://github.com/jenkins-infra/helpdesk/issues/5067

[Resolved] update center issue

Thu, 16 Apr 2026 09:00:00 +0000

[Final message]

The issue was relarted to CNI driver of publick8s cluster, resolved after recycling its nodes.

Update Center is back to normal.

[Initial message]

updates.jenkins.io is returning random HTTP/502 errors, plugin updates are stuck.

We’re working on it, expect an LDAP restart.

[Resolved] Update Center slow due to CloudFlare outage

Tue, 20 Jan 2026 07:30:00 +0000

[Final Message] CloudFlare maintenance is finished: we’ve enabled the East America mirror as it is now responding as expected.

[Initial Message] CloudFlare is performing a maintenance (https://www.cloudflarestatus.com/incidents/y5xbgk3fh95y) with re-routed traffic. Since 07:30 UTC, our monitoring detected a lot of timeouts for the Update Center requests targeted at our East US mirror due to the re-routing latency.

We’ve disabled the East US mirror in favor of West europe or archives.jenkins.io at 08:00 UTC for now.

[Resolved] CloudFlare outage

Tue, 18 Nov 2025 11:48:00 +0000

Final message: CloudFlare incident has been resolved:

Cloudflare services are currently operating normally. We are no longer observing elevated errors or latency across the network.

Initial message: CloudFlare is down: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

This impacts the Update Center, and element channels like #jenkins-infra

We’ll keep this status updated.

[Resolved] Outage on get.jenkins.io and updates.jenkins.io

Thu, 09 Oct 2025 07:08:20 +0000

[Final Message] The outage seems resolved https://github.com/jenkins-infra/helpdesk/issues/4827

[Initial Message] we are encountering an outage on get.jenkins.io and updates.jenkins.io our publick8s cluster. We are seeing problems that azure doesn’t acknowledge, probably related to an Azure outage.

see https://github.com/jenkins-infra/helpdesk/issues/4827 for information

[Resolved] Outage on get.jenkins.io and updates.jenkins.io

Tue, 07 Oct 2025 07:03:00 +0000

[Final Message] The outage seems resolved https://github.com/jenkins-infra/helpdesk/issues/4827 . We did a refresh of the 3 nodes of publick8s but were impacted with an azure outage that is not public yet.

[Initial Message] We are encountering an outage on get.jenkins.io, currently investigating. The same problem is visible on updates.jenkins.io.

[Resolved] Enforced HTTPS for Update Center

Wed, 06 Aug 2025 07:00:00 +0000

Wednesday 06 August 2025 at 07:00am UTC, the service https://updates.jenkins.io will be upgraded to enforced HTTPS as described in https://www.jenkins.io/blog/2025/08/04/update-center-enforce-https/.

The operation should take from 5 to 30 minutes (depends on the Azure Cloud ability to spin up resources on demand).

All Jenkins users are impacted but should not see any functional change. Eventually, some requests may time out during the deployment of the new settings.

More details in https://github.com/jenkins-infra/helpdesk/issues/4758.

[Resolved] Disruption of mirror selections on get.jenkins.io and Update Center

Thu, 05 Dec 2024 13:00:00 +0000

User reported that mirror selection is acting randomly with message in mirrorbit web UI saying “Cannot locate the client IP (ASN0)”.

Requests are still served but it may disrupt download performances.

More details in https://github.com/jenkins-infra/helpdesk/issues/4441.

[Resolved] Outage on the Update Center with 404-502 errors

Thu, 28 Nov 2024 08:45:00 +0000

[Final Message]

Multiple issues opened such as https://github.com/jenkins-infra/helpdesk/issues/4427 or https://github.com/jenkins-infra/helpdesk/issues/4428.

Remediation consisted in cordoning and draining the Kubernetes nodes to bypass the CSI SMB/CIFS errors causing the outage. Long term fix has been applied the 29 Nov.: see https://github.com/jenkins-infra/helpdesk/issues/4402 for details.

[Initial message] The update center is having errors 404 and 502, remediation incoming

More details in https://matrix.to/#/!JLUOInpEYmxJIYXlzs:matrix.org/$Uvn4cn3an3RDVQT_trYGbPT3OKdV8yf0NFfjcW_Tejo?via=g4v.dev&via=gitter.im&via=matrix.org.

[Resolved] Update Center Brownout (6)

Thu, 07 Nov 2024 09:00:00 +0000

Thursday 07 November 2024 at 09:00am UTC, the service https://updates.jenkins.io will switch its implementation to a new system for 24 hours.

All Jenkins users are impacted but should not see any functional change.

⚠️ Please, check that your organization respects the advertised DNS TTL or you might be stuck in the brownout longer that expected.

Under the hood, any HTTP request made to this service will be redirected to a mirror close to user locations during these brownouts.

More details in https://github.com/jenkins-infra/helpdesk/issues/2649.

[Resolved] Update Center Brownout (5)

Thu, 24 Oct 2024 10:00:00 +0000

Thursday 24 October 2024 at 10:00am UTC, the service https://updates.jenkins.io will switch its implementation to a new system for 24 hours.

All Jenkins users are impacted but should not see any functional change.

⚠️ Please, check that your organization respects the advertised DNS TTL or you might be stuck in the brownout longer that expected.

Under the hood, any HTTP request made to this service will be redirected to a mirror close to user locations during these brownouts.

More details in https://github.com/jenkins-infra/helpdesk/issues/2649.

[Resolved] Update Center Brownout (4)

Thu, 26 Sep 2024 07:00:00 +0000

Thursday 26 September 2024 at 07:00am UTC, the service https://updates.jenkins.io will switch its implementation to a new system for 24 hours.

All Jenkins users are impacted but should not see any functional change.

⚠️ Please, check that your organization respects the advertised DNS TTL or you might be stuck in the brownout longer that expected.

Under the hood, any HTTP request made to this service will be redirected to a mirror close to user locations during these brownouts.

More details in https://github.com/jenkins-infra/helpdesk/issues/2649.

[Resolved] Update Center Brownout (3)

Wed, 11 Sep 2024 14:00:00 +0000

Wednesday 11 September 2024 from 02:00pm UTC until Thursday 12 September 2024 02:00pm UTC, the service https://updates.jenkins.io will switch its implementation to a new system.

All Jenkins users are impacted but should not see any functional change.

⚠️ Please, check that your organization respects the advertised DNS TTL or you might be stuck in the brownout longer that expected.

Under the hood, any HTTP request made to this service will be redirected to a mirror close to user locations during these brownouts.

More details in https://github.com/jenkins-infra/helpdesk/issues/2649 and https://www.jenkins.io/blog/2024/09/10/update-center-brownouts-3/.

[Resolved] Update Center Brownout (2)

Mon, 09 Sep 2024 14:00:00 +0000

Monday 9 September 2024 at 02:00pm UTC, the service https://updates.jenkins.io will switch its implementation to a new system during 1 hour.

All Jenkins users are impacted but should not see any functional change.

⚠️ Please, check that your organization respects the advertised DNS TTL or you might be stuck in the brownout longer that expected.

Under the hood, any HTTP request made to this service will be redirected to a mirror close to user locations during these brownouts.

More details in https://github.com/jenkins-infra/helpdesk/issues/2649.

[Resolved] Update Center Brownout (1)

Fri, 06 Sep 2024 07:00:00 +0000

Friday 6 September 2024 at 07:00am UTC, the service https://updates.jenkins.io will switch its implementation to a new system during 1 hour.

All Jenkins users are impacted but should not see any functional change.

⚠️ Please, check that your organization respects the advertised DNS TTL or you might be stuck in the brownout longer that expected.

Under the hood, any HTTP request made to this service will be redirected to a mirror close to user locations during these brownouts.

More details in https://github.com/jenkins-infra/helpdesk/issues/2649.

[Resolved] update center maintenance

Mon, 25 Mar 2024 13:30:00 +0000

[Final message]

Migration finished.

See https://github.com/jenkins-infra/helpdesk/issues/3414 for more details.

[Initial message]

We’ll migrate scripts used by the update center from blobxfer to azcopy today at 13h30 UTC, which might result in a latency of plugins new releases availability.

See https://github.com/jenkins-infra/helpdesk/issues/3414 for more details.

[Resolved] get.jenkins.io latest 2.443 issue

Tue, 30 Jan 2024 15:00:00 +0000

[Final Message]

Release Core packaging process finished with success, both services are back to normal.

[Initial Message]

Tuesday January 30 2024, starting at 15:05 UTC, get.jenkins.io and updates.jenkins.io return an error when trying to download the latest Jenkins Weekly release 2.443, due to an issue in the release process.

More details in https://github.com/jenkins-infra/helpdesk/issues/3927

[Resolved] trusted.ci.jenkins.io migration to Azure

Fri, 02 Jun 2023 08:30:00 +0000

[Final message] The migration was finished at 17h00 UTC and everything looks good: Update Center, RPU, jenkins.io and all jobs are successful.

[Initial message] A migration of the “Trusted” controller (trusted.ci.jenkins.io) virtual machines from AWS EC2 to Azure is planned today on Friday 2 of June 2023 starting at 08h30 UTC. The service will be down until the migration is complete and finished.

It has an impact on:

The Update Center (updates.jenkins.io): any release of a plugin won’t be visible until the end of the migration
The CD plugin process: the Repository Permission Updater system won’t be updated until the end of the migration: Publishing a new plugin with the CD process or logging-in to Artifactory (repo.jenkins-ci.org) could be impacted
The Plugin site (plugins.jenkins.io) and the Javadoc (javadoc.jenkins.io) won’t be updated during the migration

More details on https://github.com/jenkins-infra/helpdesk/issues/3486.

[Resolved] Update Center certificate issue (updates.jenkins.io)

Tue, 14 Jun 2022 12:42:00 +0000

[Initial message]

There is an issue with the Update Center certificate, resulting in this error message in Jenkins instances:

It seems plugin updates still work.

We’re working on it, you can follow the issue here: https://github.com/jenkins-infra/helpdesk/issues/2950

[Resolved] Update Center not updated with new released plugins

Tue, 31 May 2022 12:00:00 +0000

[Close Issue] the new certificate had been issued and stored within the trusted controller. Both the crawler and the update-center jobs run smoothly again since 07:34am UTC.

The plugin “gap” was filled at 09:47am UTC as per https://github.com/jenkins-infra/helpdesk/issues/2950#issuecomment-1143374848.

[Open Issue] The service updates.jenkins.io, which provides a catalog of the jenkins plugins, is not updated since the 31th of May 2022, around noon UTC. It is caused by a safety measure that forbid updates of the catalog: the signing certificate expires soon and must be renewed. More details on https://github.com/jenkins-infra/helpdesk/issues/2950.

[Resolved] Update Center (updates.jenkins.io) flaky, slow with timeouts

Sat, 28 May 2022 02:00:00 +0000

[close issue] We were able to fix the configuration of the service to a fine tuned value. Closing the incident after 24 hours without issues.

[edit] Issue to track changes: https://github.com/jenkins-infra/helpdesk/issues/2960.

[Open Issue] The service https://updates.jenkins.io is experimenting flakiness with a lot of HTTP timeouts. We are searching the source of trouble and we’ll keep you informed.

[Resolved] Maintenance on updates.jenkins.io

Fri, 27 May 2022 09:00:00 +0000

[Initial message] We are performing a maintenance on the virtual machine hosting the website https://updates.jenkins.io (“Update Center”) as part of https://github.com/jenkins-infra/helpdesk/issues/2888. No disruption is expected (unless a human mistake is made of course).

[Resolved] Outage on updates.jenkins.io - Invalid certificate

Thu, 19 May 2022 08:10:00 +0000

[edit] Fix applied, but it should take up to 1 hour depending on the DNS cache of your internet providers. More details on https://github.com/jenkins-infra/helpdesk/issues/2888#issuecomment-1131453254.

[Initial message] The website updates.jenkins.io is responding either HTTP/404 pages or “Invalid certificate” (when accessed through HTTPS).

[Resolved] Update center content not refreshed, recent plugin releases not visible

Wed, 07 Jul 2021 10:00:00 +0000

The update center had its content not refreshed from the 07th of July 2021 until the 12th of July 2021.

More details on what went wrong and how it was fixed can be found in the following page: INFRA-3023.

[Resolved] Windows LTS Package Unavailable

Wed, 02 Jun 2021 18:59:00 +0000

Due to a technical issue in the release process, the Windows package for the LTS Jenkins release was unavailable during almost 13 hours.

The release process has been fixed and executed successfully the 03rd of June 2021 at 06:50 UTC and finished at 07:02 UTC.

At 07:00 UTC, the Windows package was available again from https://jenkins.io/download.

[Resolved] Update center job on trusted.ci.jenkins.io is blocked

Sun, 30 May 2021 08:13:00 +0000

The Jenkins update center relies on a job that runs periodically on trusted.ci.jenkins.io to record the latest releases. That job blocked on May 30 and has not been performing updates.

Timeline

2021-05-30T08:13 - Update center job on trusted.ci.jenkins.io reports blocked waiting for agent-1
2021-06-01T19:45 - Mark Waite investigates Jenkins 2.296 not being visible on www.jenkins.io, detects blocked update center job
2021-06-01T23:50 - EU team hands over, detects there was a DNS resolution issue in trusted.ci.jenkins.io and changed the configuration of agent-1 accordingly: the update_center build moved from the “waiting” state to “building” state on agent-1
2021-06-02T01:50 - After a manualy apply of the update_center + a successful build, the latest weekly 2.296 appears on the update center.json

[Resolved] Windows Weekly Package Unavailable

Tue, 25 May 2021 11:30:00 +0000

Due to a technical issue in the release process, the Windows package for the weekly Jenkins release was unavailable from 2021-05-25 11:30 UTC until 2021-05-26 07:51 UTC.

A Post-Mortem is available on hackmd.io.

[Resolved] Update sites not updating

Sun, 21 Mar 2021 10:00:00 +0000

Update sites are currently not updating. Plugin updates released since this outage started are not made available to users.

[Resolved] get.jenkins.io dns update

Sun, 13 Dec 2020 13:20:00 +0000

INFRA-2846

Because of the previous get.jenkins.io outage, we temporarily redeployed the service on a virtual machine. The azure file storage issue is now resolved and the service ready to handle the traffic as it used to be. I am going to update the dns record to redirect from the temporary virtual machine to our kubernetes cluster.

No downtime is expected

[Resolved] get.jenkins.io issues

Thu, 12 Nov 2020 15:54:00 +0000

2020-11-23: Azure is investigating the root cause of the issue
2020-11-19: The Azure blog storage is back without additional information
*2020-11-14: We temporarily deploy get.jenkins.io outside Azure
2020-11-17: We have a call with Azure support today

The network volume used by get.jenkins.io is currently down. This outage affect every services relying on get.jenkins.io like updates.jenkins.io and pkg.jenkins.io

Twitter Discussion