Jamf Outage History

Jamf Account underwent a brief, scheduled maintenance window on 2025-02-20. The maintenance began at 11:04 PM UTC and ended at 11:24 PM UTC. The Jamf status page indicated the maintenance was in progress and later confirmed the service returned to normal when the Jamf Account component moved back to up. There were no user reports during the window, and the maintenance completed without additional incidents.

The Jamf School service in the ap-northeast-1 region underwent a scheduled maintenance window. The maintenance began at 12:00 PM UTC and finished at 2:04 PM UTC, lasting about 2 hours and 4 minutes. During this period, components in that region were offline for the maintenance work as described on Jamf's status page.

The provider issued two status updates during the incident: one indicating that maintenance was in progress and another confirming that the service had been restored. The maintenance was specific to the ap-northeast-1 region, with no indication of broader impact.

Jamf School in the ap-northeast-1 region underwent a scheduled maintenance window. The maintenance began at 12:00 PM UTC and completed at 2:04 PM UTC, lasting a little over 2 hours. The Jamf status page indicated the window was in progress and then returned to normal operation once the maintenance concluded. The incident was communicated via two updates on the Jamf status page, first noting the maintenance in progress and later confirming the service was back to normal.

Jamf School in the ap-northeast-1 region entered a scheduled maintenance window starting at 12:00 PM UTC. The status changed to maintenance at Feb 17, 2025 12:09 PM UTC and the service was restored at Feb 17, 2025 2:04 PM UTC. The maintenance lasted about two hours and affected the Jamf School component in ap-northeast-1.

Jamf reported a roaming data policy was incorrectly applied to devices in the Domestic zone, causing devices to be treated as Roaming and blocking cellular data usage. The issue also triggered email alerts to admins and users. This impacted Jamf Threat Defense, Jamf Private Access and Jamf Data Policy components, specifically the Data Policy, Notifications, and Reporting areas.

The incident began at 11:24 AM UTC and was resolved by 4:04 PM UTC, lasting about 4 hours and 40 minutes. Jamf issued 2 official updates during the event and restored normal operation once the policy was corrected.

Jamf Protect Cloud data forwarding degraded, causing delayed forwarding of a very limited number of endpoint telemetry messages in some regions. All other features and functionality remained available. The issue began with an investigation around Jan 30, 2025 7:15 PM UTC and affected six regions: eu-west-2, us-east-1, us-west-2, ap-northeast-1, ap-southeast-2, and eu-central-1.

The Jamf Insights service underwent a scheduled maintenance window affecting multiple regions. The maintenance began at Jan 24, 2025 9:04 PM UTC and concluded at Jan 24, 2025 11:04 PM UTC, lasting 2 hours. Four Jamf Insights components were affected across eu-west-2 and us-east-1: Jamf Insights Standard in eu-west-2 and us-east-1, and Jamf Insights Service-Enabled in eu-west-2 and us-east-1. Jamf communicated the maintenance via its status page, noting the work in progress and that updates would be provided as necessary, before services returned to normal.

Jamf experienced a brief outage affecting Jamf Account and Jamf ID, causing temporary authentication and account access issues for users. The incident began at Jan 13, 2025 3:29 PM UTC and was resolved by Jan 13, 2025 3:54 PM UTC, lasting about 25 minutes. The Jamf status page documented an initial investigation and later confirmation of service restoration, with the provider issuing 2 status updates during the incident. The outage impacted two components (Jamf Account and Jamf ID) and was resolved with systems returning to normal.