Skip to main content

Is Jenkins Down?

No — Jenkins is up

Reachable from all 8 checked regions

Average response time: 16ms

Last checked · checks run every 6 hours

Official status page: https://status.jenkins.io

Jenkins uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
121ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 8 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

8-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: no data
Aug 7: no data
Aug 8: no data
Aug 9: no data
Aug 10: no data
Aug 11: no data
Aug 12: no data
Aug 13: no data
Aug 14: no data
Aug 15: no data
Aug 16: 100.00% uptime, 15 checks
Aug 17: 100.00% uptime, 32 checks
Aug 18: 100.00% uptime, 32 checks
Aug 19: 100.00% uptime, 32 checks
Aug 20: 100.00% uptime, 45 checks
Aug 21: 100.00% uptime, 31 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 32 checks
Jul 25 Today
No downtime Partial Downtime Not measurable No data

Reachability 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.

jnb
904ms
DNS 0ms TCP 171ms TLS 345ms TTFB 687ms
lax
24ms
DNS 1ms TCP 1ms TLS 15ms TTFB 19ms
lhr
13ms
DNS 0ms TCP 1ms TLS 5ms TTFB 10ms
nrt
15ms
DNS 1ms TCP 1ms TLS 6ms TTFB 12ms
ord
20ms
DNS 0ms TCP 1ms TLS 6ms TTFB 17ms
sin
11ms
DNS 0ms TCP 0ms TLS 5ms TTFB 8ms
sjc
17ms
DNS 0ms TCP 1ms TLS 6ms TTFB 13ms
syd
12ms
DNS 0ms TCP 0ms TLS 5ms TTFB 9ms
yyz
16ms
DNS 0ms TCP 0ms TLS 6ms TTFB 13ms

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 all 18 regions to find out where it breaks.

Test it yourself

Related services

Jenkins outage FAQ

My Jenkins is down. Does this page tell me why?
Probably not. Jenkins runs on your own hardware, so a controller that will not start is a local problem: disk, memory, Java version, or a plugin upgrade gone wrong. This page tracks the Jenkins project's shared services. It answers whether plugin downloads and release mirrors are working, not whether your server is.
Why do plugin installs fail when my Jenkins is running fine?
Because plugin metadata and downloads come from updates.jenkins.io rather than from your controller. When that service or the mirror redirector behind get.jenkins.io has an incident, an otherwise healthy Jenkins shows an empty plugin list or times out mid-download. The controller itself is untouched and existing plugins keep working.
Is there a hosted Jenkins that can have outages?
The project does not offer Jenkins as a hosted service. CloudBees and various managed providers sell hosted distributions, and those carry their own status pages and their own incidents. An outage at a commercial Jenkins host is unrelated to the state of the project infrastructure measured here.
Do failed plugin downloads break running builds?
Only builds that fetch something mid-run. A pipeline using plugins already installed on the controller runs normally throughout. Builds that download a tool, a dependency, or a Jenkins plugin as a step will fail at that step. Pinning versions and caching dependencies locally removes the dependency on the update centre entirely.

How we measure this

  • We request Jenkins's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means 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 the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required