Is Jenkins Down?
Reachable from all 8 checked regions
Average response time: 228ms
Last checked · checks run every 6 hours
Official status page: https://status.jenkins.io
Jenkins uptime
Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 59 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
30-day history
59-day clean streakReachability by region
Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.
What Jenkins does
Jenkins is self-hosted build automation, so the software runs on your own servers and cannot go down as a service. What can go down is the project's shared infrastructure: the update centre serving plugin metadata, the mirrors distributing releases, and the plugin site. This page measures that shared infrastructure, not your own build server.
What an outage looks like
Plugin installation and upgrade fail inside an otherwise healthy Jenkins, with the update centre reporting no available plugins or timing out. Fresh installations cannot download packages through the mirror redirector. Pipelines that fetch a plugin or a tool during the build break, while pipelines using only what is already installed run normally.
What to do about it
Confirm which side is failing before restarting anything. status.jenkins.io lists updates.jenkins.io, plugins.jenkins.io, get.jenkins.io, and pkg.jenkins.io separately from the main website, so the component matching your error names the fault. A controller that builds fine but cannot fetch plugins is hitting project infrastructure, where waiting beats reinstalling.
Is it down for everyone, or just you?
If this page says Jenkins is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
Jenkins outage FAQ
My Jenkins is down. Does this page tell me why?
Why do plugin installs fail when my Jenkins is running fine?
Is there a hosted Jenkins that can have outages?
Do failed plugin downloads break running builds?
How we measure this
- We request Jenkins's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Jenkins publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.
Get alerted when Jenkins goes down
This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring