Jamf Outage History

Two regional maintenance windows were triggered by a planned upgrade to Jamf Pro Standard 11.24.1. EU-central-1 began maintenance at 11:14 AM UTC and US-East-2 began at 2:24 PM UTC. The two regions completed maintenance at different times, with EU-central-1 returning to normal by 6:34 AM UTC and US-East-2 by 8:34 AM UTC. The provider issued four status updates during the incident, and there were no user reports indicating broader impact.

The Jamf Security Cloud Console experienced degraded data loading, causing some pages and widgets to fail to load. The issue affected Jamf Threat Defense, Jamf Private Access, and Jamf Data Policy / Reporting within the Security Cloud Console. The degradation began at Jan 6, 2026 6:04 PM UTC and was resolved by Jan 6, 2026 6:29 PM UTC, lasting about 25 minutes. As a workaround, refreshing the page may resolve loading issues in some cases.

The Jamf status page posted two updates during the incident as investigators worked to identify the root cause and restore full functionality.

Jamf School in the ap-northeast-1 region underwent scheduled maintenance. The maintenance window began at 2:00 PM UTC and completed by 4:04 PM UTC, lasting roughly 2 hours and 4 minutes. The Jamf status page showed the service as in maintenance during the window and then returned to normal after the update, with 2 status updates issued during the incident. The impact was limited to the Jamf School service in that region and did not indicate a broader outage.

Jamf experienced partial degradation affecting SecureDNS in the APAC region, causing intermittent DNS resolution delays for Jamf Security Cloud and Jamf Safe Internet. Users in APAC (ap-northeast-1) may have experienced slower browsing or connectivity. The issue began at Dec 10, 2025 1:30 AM UTC with Jamf teams investigating increased latency in SecureDNS policy evaluation.

Jamf posted two status updates during the incident. The issue progressed from investigation to partial degradation at Dec 10, 2025 1:54 AM UTC and was resolved by Dec 10, 2025 3:39 AM UTC, with affected services returning to normal. The outage lasted about 2 hours and 9 minutes and affected two core components: Threat Defense and Data Policy.

The Jamf Auto Update / CDN experienced a partial outage that degraded update delivery for a period. The incident began at Dec 8, 2025 12:09 PM UTC when the Jamf status page moved from up to Partially Degraded Service for Jamf Auto Update / CDN, and was resolved at Dec 8, 2025 3:04 PM UTC, lasting about 2 hours and 55 minutes.

The Jamf status page issued two updates during the incident as the service progressed from degraded to normal. The issue appeared isolated to Jamf Auto Update / CDN and did not indicate broader impact on other Jamf components.

Jamf conducted scheduled maintenance affecting Jamf Threat Defense, Jamf Private Access, and Jamf Data Policy / Authentication and Admin Management. The maintenance began at 9:34 AM UTC and concluded at 10:09 AM UTC, lasting about 35 minutes. During the window, the affected components were temporarily unavailable as the maintenance proceeded. This was a planned activity announced on Jamf's status page with the in-progress update suggesting ongoing maintenance and a later update confirming restoration to normal.

The incident was contained to the maintenance window, with Jamf returning the status to up at 10:09 AM UTC. Two official status updates were published during the event, and there was no indication of unplanned outages beyond the scheduled window.

Jamf School in the ap-northeast-1 region underwent a scheduled maintenance window beginning at 2:00 PM UTC and ending at 5:04 PM UTC. The Jamf status page indicated the service entered maintenance during this period, with updates as the work progressed. The maintenance was limited to the ap-northeast-1 region and the service was restored after the window closed, with two official updates documenting the process and completion.

Jamf Protect experienced intermittent authentication failures when logging into the Admin Console with Jamf ID or IdP configured in Jamf Account. The issue appeared to be caused by an upstream IDaaS provider and impacted users across multiple Jamf Protect regions, including ap-northeast-1, ap-southeast-2, eu-central-1, eu-west-2, us-east-1, and us-west-2. The incident lasted about 20 minutes, during which users could encounter difficulties authenticating before services returned to normal.

According to Jamf status updates, the problem began at 4:14 PM UTC and was resolved by 4:34 PM UTC. The affected components were restored to the standard operating state after the upstream IDaaS issue was addressed. There were no indication of broader service disruption beyond the authentication flow for Jamf Protect Admin Console.

Jamf School in the EU-central-1 region experienced an outage related to delivering restrictions to student devices. Some restrictions may not have been applied or were delayed during the incident. The outage lasted 35 minutes, beginning at 9:04 AM UTC and ending at 9:39 AM UTC. The issue was isolated to Jamf School in eu-central-1 and did not appear to affect other Jamf services. Two official status updates were posted during the incident: an initial investigation notice at Nov 4, 2025 9:04 AM UTC and a recovery update at Nov 4, 2025 9:39 AM UTC confirming resolution.

Jamf School conducted scheduled maintenance in the ap-northeast-1 region from Oct 23, 2025 1:04 PM UTC to Oct 23, 2025 4:04 PM UTC. During this window, users relying on Jamf School in that region may have experienced limited access. A user in Ashburn, Virginia reported noticing issues around 3:58 PM UTC.

The Jamf status page posted two updates during the window: the initial update indicating that maintenance was in progress and a follow-up confirming that Jamf School had returned to normal at Oct 23, 2025 4:04 PM UTC. The incident affected a single component, Jamf School in ap-northeast-1, and lasted about 3 hours. Overall, user reports during the window were limited.