Is Jamf Down?

No — Jamf is up

Reachable from all 8 checked regions

Average response time: 139ms

Last checked 5 hours ago · checks run every 6 hours

Official status page: https://status.jamf.com

Jamf uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

165ms

Avg response, 30 days

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

30-day history

75-day clean streak

Sep 14 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.

ams

94ms

DNS 67ms TCP 2ms TLS 7ms TTFB 88ms

arn

112ms

DNS 93ms TCP 1ms TLS 5ms TTFB 108ms

cdg

54ms

DNS 34ms TCP 1ms TLS 6ms TTFB 49ms

dfw

94ms

DNS 76ms TCP 1ms TLS 4ms TTFB 89ms

ewr

138ms

DNS 72ms TCP 14ms TLS 10ms TTFB 114ms

fra

91ms

DNS 72ms TCP 1ms TLS 3ms TTFB 86ms

gru

395ms

DNS 377ms TCP 1ms TLS 5ms TTFB 392ms

iad

136ms

DNS 111ms TCP 3ms TLS 4ms TTFB 129ms

What Jamf does

Jamf manages fleets of Macs, iPhones, iPads and Apple TVs for companies and schools, handling enrolment, configuration profiles, app deployment and endpoint security from one console. IT teams depend on it to bring a new device under management and to push changes to devices already in the field, so an outage tends to block onboarding first.

What an outage looks like

Enrolment stalls for new devices, leaving a Mac sitting at setup with no profiles applied. Policies and configuration changes do not reach devices already deployed. The Jamf Pro console will not load or times out on login. Self Service shows an empty catalogue, and package downloads fail so installs never finish. Devices already configured keep their existing settings and carry on working.

What to do about it

Check status.jamf.com and find your own hosting region. Jamf Pro is listed per AWS region, including us-east-1, us-west-2, eu-central-1, eu-west-2, ap-northeast-1 and ap-southeast-2, with separate Standard and Premium tiers and a separate Azure section. Jamf Now, Jamf Nation and the Cloud Distribution Service are tracked independently, so package delivery can fail while the console is fine.

Is it down for everyone, or just you?

If this page says Jamf 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.

Test it yourself

Related services

Jamf outage FAQ

Do managed Macs stop working when Jamf is down?

No. Profiles, restrictions and applications already installed stay in place, because they are enforced on the device rather than fetched live. What breaks is change: new policies do not arrive, enrolment cannot complete, and Self Service has nothing to offer. Users on configured machines usually notice nothing, while IT loses the ability to act on the fleet.

Is my Jamf Pro instance in the affected region?

Check the hostname of your own Jamf Pro URL against the region list. The status page reports each AWS region separately, so an incident in eu-central-1 does not touch a tenant in us-east-1. Standard and Premium are also split out, which means two customers in the same region can have different experiences during the same incident.

Why do app installs fail when the console looks fine?

Because package distribution is a separate service. The Jamf Cloud Distribution Service is tracked on its own and is region-specific, so the console can load and policies can dispatch while the actual package download fails. An install that starts and never completes points at distribution rather than at Jamf Pro itself.

Can I still enrol a new device during an outage?

Generally not, and this is the most common impact. Enrolment requires a live conversation between the device and Jamf Pro to receive its management profile, so a device set up during an incident ends up unmanaged rather than partially managed. Waiting and re-running enrolment afterwards is cleaner than trying to force it through.

Does a Jamf outage affect Apple services like Apple Business Manager?

They are separate systems with separate failures. Jamf depends on Apple for parts of enrolment and app licensing, so an Apple-side problem can look identical to a Jamf outage from the console. If status.jamf.com reads operational for your region and enrolment still fails, check Apple's own system status before continuing to troubleshoot Jamf.

How we measure this

We request Jamf'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 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 Jamf 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 Jamf 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

Free plan available No credit card required