Skip to content
PulseWatchOUTAGE.INTEL
Jamf logo

Productivity

Is Jamf down right now?

NormalOfficial status last polled Oct 12, 2026 15:38 UTCwww.jamf.comOfficial status page

Are you on the Jamf team and see something inaccurate? Report it to us. We respond within one business day.

Is Jamf down right now?

No. Jamf has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Oct 12, 2026 15:41 UTC

Normal

Jamf is operating normally

As of Oct 12, 2026 15:41 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

0

Last incident

Oct 1, 2026 08:00 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Jamf.

3

Incident days

27

No recorded incident

6h 44m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical
Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.
Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Jamf. Hover a day for detail.

Sep 13Sep 18Sep 23Sep 28Oct 3Oct 801234

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

3

Days with incidents

1 incident

Busiest day

6h 44m

Recorded duration

Report volume

0 reports in last 24H

03:30 PM07:00 PM10:30 PM02:00 AM05:30 AM09:00 AM12:30 PM00.511.52baseline 1

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Jamf: vendor-reported incident on October 1 (tracked 1h 29m)

Oct 1, 06:30 AM → Oct 1, 08:00 AM · 1h 29m · medium

Jamf reported an incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 1h 29m, from Thu, 01 Oct 2026 06:30:29 GMT to Thu, 01 Oct 2026 08:00:25 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
1h 29m
tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident, so it cannot describe what users experienced. The vendor's own status page is the only source PulseWatch has for it.

Incident timeline

  1. Oct 1, 06:30 AM

    The vendor reported an incident on its own status page; PulseWatch began tracking it

  2. Oct 1, 06:30 AM

    Status updated: possible issue

  3. Oct 1, 08:00 AM

    PulseWatch closed the incident

Official updates

  1. Oct 1, 06:30 AM

    Jamf reported the incident on its status page.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the vendor's own status page.

Reliability

Detected by PulseWatch

30-day uptime

99.06%

90-day uptime

99.57%

Calculated from Jamf's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other productivity services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

500 characters left

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →
ResolvedMedium

Jamf: the vendor reports a partial outage on its own status page. Single origin, not independently confirmed. Users who watch Jamf or have an alert rule on it can be alerted, labelled vendor-reported.

10/1/2026, 6:30:29 AM · 1h 29m

06:30 AM08:00 AM
Detection10/1/2026, 6:30:29 AM · 11d ago

Detected — medium severity

Jamf: the vendor reports a partial outage on its own status page. Single origin, not independently confirmed. Users who watch Jamf or have an alert rule on it can be alerted, labelled vendor-reported.

ResolvedHigh

Jamf: the vendor reports a critical-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Jamf or have an alert rule on it can be alerted, labelled vendor-reported.

9/24/2026, 6:30:46 AM · 1h 29m

06:30 AM08:00 AM
Detection9/24/2026, 6:30:46 AM · 18d ago

Detected — high severity

Jamf: the vendor reports a critical-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Jamf or have an alert rule on it can be alerted, labelled vendor-reported.

ResolvedHigh

Jamf: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Jamf or have an alert rule on it can be alerted, labelled vendor-reported.

9/16/2026, 12:31:25 PM · 3h 44m

12:31 PM04:16 PM
Detection9/16/2026, 12:31:25 PM · 26d ago

Detected — high severity

Jamf: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Jamf or have an alert rule on it can be alerted, labelled vendor-reported.

ResolvedMedium

Jamf incident correlated across 1 signal group: official/vendor.

9/3/2026, 10:14:31 PM · 2h 32m

10:14 PM12:46 AM
Detection9/3/2026, 10:14:31 PM · 1mo ago

Detected — medium severity

Jamf incident correlated across 1 signal group: official/vendor.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment Jamf enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

Live signal

Status
Normal
Monitoring
Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).
Coverage
Verified against the vendor's own incident history
Reports (24h)
0
Baseline / hour
5
Open threshold
3x

Official site

www.jamf.com