Jamf outage history

A scheduled maintenance window for Jamf Insights in the eu-west-2 and us-east-1 regions completed. The upgrade activity began at 10:04 AM UTC and finished by 10:04 PM UTC, during which Jamf Insights Standard and Service Enabled components were in maintenance. After the window, services returned to normal in both regions as the maintenance concluded.

Jamf Now experienced an outage beginning at 9:29 AM UTC when some accounts were deactivated unexpectedly. Affected customers may have seen devices not checking in or be unable to sign in. By 11:49 AM UTC the issue had been identified and Jamf was actively working on next steps to remediate. The service returned to normal later in the day, with Jamf Now progressing back to an up state by 9:34 PM UTC.

Users of Jamf Pro faced degraded performance for a brief period starting at 4:59 PM UTC when Jamf reported slow response times and that a fix was being implemented. The issue was resolved by 5:34 PM UTC, with Jamf Pro returning to normal operations after roughly 35 minutes. The status page noted an identified issue and ongoing remediation, with no regional pattern reported.

Users of Jamf Pro Standard in the EU Central region experienced partial connectivity issues starting at 11:39 AM UTC. The problem affected a subset of Jamf Pro Standard instances in eu-central-1, causing intermittent access problems for affected users. The Jamf status page noted that the issue had been identified and a fix was being implemented.

The issue was resolved by 1:04 PM UTC, with the Jamf Pro Standard component returning to full operation. The disruption lasted a little over an hour and was contained to the eu-central-1 region; no broader outages were reported.

Across Jamf School environments in ap-northeast-1, eu-central-1, and us-east-1, users experienced delays in new apps and licenses appearing in their Jamf dashboards due to issues with VPP v2 integration. The incident began at Oct 23, 2026 10:19 AM UTC and was listed as a degraded condition affecting VPP v2. A fix was implemented by 10:49 AM UTC and Jamf began monitoring results. A subsequent update at 12:09 PM UTC indicated the fix was in place and monitoring continued. The affected regions returned to normal by 12:24 PM UTC as Jamf School services moved back to up.

The incident began at 9:04 AM UTC when the On-Device Content Filtering test page (odcf-test.jamfcloud.com) became unavailable, with Jamf Security Cloud / Threat Defense listed as degraded. In parallel, Jamf School Upload Functionality faced issues as engineers investigated. Around 2:09 PM UTC, Jamf disclosed a public vulnerability related to intermediate certificate authority keys from eMudhra that could affect certificate trust across the internet, though Jamf noted there was no loss of functionality across Jamf products at that time.

Impact began at 8:09 AM UTC when Jamf School Upload Functionality moved to a degraded state, making upload services including VPP/ADE tokens, macOS app packages, wallpapers, custom profiles, attachments in support tickets, and the Title Editor unavailable. In some cases, customers could also be unable to create support tickets directly in Jamf School. By 9:04 AM UTC, the On-Device Content Filtering test page also became unavailable, while Jamf Security Cloud / Threat Defense was listed in a degraded state. The issue evolved over the afternoon with ongoing mitigation efforts as certificate trust concerns began to surface.

In the afternoon, the public disclosure of compromised intermediate certificate authority keys (eMudhra) prompted Jamf engineering to prioritize mitigations to certificate trust configurations across Jamf products. Jamf noted that there was no loss of functionality at that time, and work continued to restore services. By 6:14 PM UTC, a fix had been implemented to restore all services and monitoring continued. Title Editor functionality had been restored by 5:59 PM UTC, and the Threat Defense component returned to up by 8:19 PM UTC. Overall, Jamf products and services were brought back online within hours of the initial disruption.

Jamf experienced a brief database issue that affected Jamf Pro Standard in the us-west-2 region, causing degraded availability for affected users. The incident began at 6:14 AM UTC when the status page flagged Database Issues for the Jamf Pro Standard component in us-west-2. By 6:19 AM UTC, the issue had been identified and a fix was being implemented. The service was restored at 6:49 AM UTC after about 35 minutes, with Jamf Pro Standard returning to normal.

An outage affected Jamf Pro in the Central US region due to certificate issues, leaving users unable to access or manage Jamf Pro - Azure / central-us for a short period. The incident began at 6:30 AM UTC and was resolved by 7:04 AM UTC. Jamf's status page noted Central US Certificate Issues and that an investigation was underway, followed by confirmation that the issue had been identified and a fix was being implemented before restoration of service. The disruption was localized to the Central US region with no broader impact reported.

An outage affected Jamf Account and Jamf School services across multiple regions. The disruption began at Sep 16, 2026 11:34 AM UTC, with Jamf reporting continued investigation into a fulfillment services issue. Affected regions included Jamf School in ap-northeast-1, eu-central-1, and us-east-1, where provisioning and fulfillment-related features were impacted.