Jamf outage history

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

This incident has been resolved.

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating the impact of the eMudhra CA keys vulnerability with regard to all Jamf Products Jamf engineering and security teams are prioritizing the services customers depend on most and applying mitigations, including updates to certificate trust configurations where applicable. At this time there is no loss of functionality or degradation across any Jamf products

All Jamf products and services remain operational. Actions: Jamf engineering and security teams continue deploying mitigations to certificate trust configurations where applicable. Customer Actions: No customer action required at this time

This incident has been resolved.

We are currently working on a fix for the On-Device Content Filtering (ODCF) test page (odcf-test.jamfcloud.com) which is currently unavailable. Note - This does NOT mean ODCF is unavailable. This status is only regarding the functionality of the test page (Not ODCF itself).

Filtering capabilities on odcf are operational. Users may notice a minor degradation in user experience. Jamf engineering continues to work toward full service restoration. Next Update: 2026-10-22 15:00 UTC

This incident has been resolved.

We are working on a fix for an issue affecting Jamf School upload functionality. In the meantime, upload services, including but not necessarily limited to the following are currently unavailable: - Importing User Data - Uploading device placeholders - Uploading photos - Attachments in support tickets - Title Editor We will provide an update when we have new information. We apologize for the inconvenience.

We are continuing to work on a fix for this issue.

Jamf School remains operational. Jamf engineering is actively investigating the upload functionality and will provide updates as they become available.

Title Editor functionality has been restored. Jamf engineering continues to investigate the remaining impacted service.

A fix has been implemented to restore all services and we are monitoring the results.

This incident has been resolved.

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

We are continuing to monitor for any further issues.

This incident has been resolved.

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

Salesforce service Interruption is impacting all Jamf fulfillment services Customer Impact: • Affected Services: Provisioning, licensing, billing services, including Jamf Account services Customer Actions: No customer action required at this time.

We are continuing to investigate this issue.

All Jamf fulfillment services are fully operational.

We are currently investigating an issue with Jamf Security Cloud that results in a delayed propagation of policy changes. Current configurations are working. If a policy change is made the updated configuration may not take effect immediately.

We are continuing to investigate the issue. Current Status: Jamf Security Cloud Policy Updates are unable to be saved. Previously changed configurations continue to see a propagation delay.

Jamf engineering has identified the issue and affecting Data Policy updates. Data Policy changes cannot be saved in any region right now while we put a fix in place. Workaround/Customer Action: While the fix is in flight, we are asking customers with large policy sets to hold off on bulk or repeated Data Policy changes — particularly rule imports applied at a parent org unit, which regenerate policy across every org unit beneath it. Two things worth knowing: - Your existing policies remain fully enforced. There is no gap in protection on your devices. - Access Policies, Threat Prevention Policy are unaffected.

We are continuing to monitor for any further issues.

Update — additional impact identified: Devices that change network context (roaming ↔ domestic) during this incident will not receive the corresponding Data Policy update. The Data Policy in effect prior to the network change remains applied until the fix is in place. Access Policies and Threat Prevention Policy are not affected by this. We are still working on a resolution and will continue to post updates here as they're available.

We are continuing to monitor for any further issues. The previous update is still relevant.

The fix has been applied to the affected service, and the root cause has been resolved. The policies need to be replicated to all edge regions, which should take a few hours. The page will be updated once replication is complete and the issue is fixed.

Data Policies are now fully synchronized across all edge regions, and policy updates in the Radar/JSC Web Console have been re-enabled. The CSV import feature will remain temporarily disabled while improvements are implemented.

We are currently investigating an issue affecting content filtering functionality for a subset of customers. Some previously blocked web content may not be filtered as expected. Our team is actively working on a resolution and we will provide updates as they become available. Affected Regions: AP East1, AP Northeast1, AP Northeast2, AP Southeast1 regions Workaround/Customer Actions: No customer action required at this time.

This incident has been resolved.

We are currently investigating an issue affecting content filtering functionality for a subset of customers. Some previously blocked web content may not be filtered as expected. Our team is actively working on a resolution and we will provide updates as they become available. Affected Regions: AP East1, AP Northeast1, AP Northeast2, AP Southeast1 regions Workaround/Customer Actions: No customer action required at this time.

Symptoms: Partial interruption with configuration profile delivery and MDM device communication. Managed devices fail to receive or update configuration profiles, and MDM commands and device check-ins fail. Affected devices remain in a pending state and do not apply configuration changes. Customer Impact: * Affected Services: Configuration profile delivery to managed devices; MDM device communication (check-ins and commands) * Affected Regions: US and EU * Business Impact: Service degradation — configuration changes not applied for the duration. No data loss and no incorrect changes to device configuration. Actions: Jamf engineering identified a failure in a shared authentication component used by configuration profile delivery and MDM communication, and restored service by reloading that component and cycling the affected application instances. Workaround/Customer Actions: No customer action required. Devices retry automatically and apply pending configuration profiles once requests succeed.

An issue has been identified that is affecting some Jamf Pro customers. We are working to resolve and will provide next update in 45 minutes.

We are monitoring the situation with the upstream service provider. We will move to Resolved once the provider confirms their incident is closed.

This incident has been resolved.

Jamf is investigating an issue affecting Blueprint management for customers in the US. Some customers may be unable to manage Blueprints at this time. Our engineering team is actively investigating and will provide updates as more information becomes available. Symptoms: US-based customers are experiencing a complete inability to manage Blueprints. Customer Impact: Affected Services: Blueprints (Blueprint Management System) Affected Regions: US

We are continuing to investigate this issue.

Blueprint management services are now operational but our engineering team is still monitoring. Customers in the US who experienced issues managing Blueprints should no longer see any impact. We apologize for the inconvenience and thank you for your patience while we resolved this issue.

This incident has been resolved. Blueprint management services for US customers are fully operational, and no further impact is expected. We apologize for any inconvenience this may have caused and thank you for your patience.

We are aware of an issue causing the Jamf Trust app to be deactivated on customer devices. While the app is deactivated, its protections — including Zero Trust Network Access (ZTNA) and content filtering — are not enforced. This affects devices on all platforms: iOS, macOS, Android, and Windows. Our engineering team has identified the cause and fix is being deployed to production. Once the fix is live, affected devices will need to be reactivated, which may require end-user or administrator action. We will post more details here as soon as the fix is confirmed.

A fix is now in production and has stopped the issue from spreading, so no additional devices will be affected. Devices where the Jamf Trust app was already deactivated may not be resolved automatically — some may recover on their own, but others will require additional remediation steps. We are compiling a report of impacted customers and are working to reach affected accounts directly with step-by-step instructions to reactivate their devices and restore protections, including Zero Trust Network Access (ZTNA) and content filtering. We will also post those instructions here so they are available to everyone affected.

The fix in production continues to hold, and no additional devices are being affected. We are still compiling the list of impacted customers and preparing the remediation instructions for devices where the Jamf Trust app was deactivated.

The issue has been resolved. The Jamf Trust app will no longer be unexpectedly deactivated on devices. Remaining Customer Impact: For Jamf Trust apps that had been previously deactivated, they will need to be reactivated. Depending on deployment configuration this may be automatic or require manual reactivation. For assistance with reactivating devices, please login to the Jamf Account portal and create a ticket (Contact Support) referencing Jamf Trust app deactivation. While the Jamf Trust app is deactivated, its protections — including Zero Trust Network Access (ZTNA) and content filtering — are not enforced. This affects devices on all platforms: iOS, macOS, Android, and Windows. We apologize for any inconvenience.

Incident Summary: Degraded Performance in Jamf Protect for macOS, Customer Impact: Client machines may experience delays with retrieving configurations, plan updates and checking-in to Jamf Protect backend. Status: The issue is under active investigation by our Engineering teams. We appreciate your patience and are committed to resolving this as swiftly as possible.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results. Performance is expected to continually improve over the next several hours.

This incident has been resolved. In the process we've reverted from version 8.16.0 to 8.15.0. Please refer to the Jamf Protect macOS Security Portal Release Notes for future updates.

Incident Summary: Public API client management unavailable in Jamf Account integrations Customer Impact: Customers may be unable to create, edit, or delete the API clients used to connect Jamf Account to other tools via the Public APIs. Existing integrations continue to function normally. Status: Our team has identified the cause and has a fix prepared. It is being validated now. We will update this page as the fix is deployed and full functionality is restored. We appreciate your patience and are committed to resolving this as swiftly as possible.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

Symptoms: Customers using the European cluster of Jamf Insights are experiencing a partial service degradation — device data is not updating and MDM commands are not functional. US region is unaffected. Customer Impact: Affected Services: Jamf Insights (EU cluster) — device data refresh, extension attribute visibility, MDM command delivery Affected Regions: European cluster only; US region verified healthy Business Impact: Service degradation — device management data is stale; MDM commands not executing through Insights Estimated Users Impacted: Up to ~5,500 EU tenants Workaround/Customer Actions: MSPs with direct Jamf Pro access can manage their customers via Jamf Pro until the fix is in place. All other customers — no additional action required at this time.

We are continuing to investigate this issue.

We have identified the issue and are currently verifying the fix. Once the fix is confirmed effective, the team will continue working to fully restore the service.

A fix has been applied and the service should now be restored. We are running verification and will continue to monitor the situation closely. We expect to know more within approximately one hour and will provide a further update then.

We are continuing to run validation to confirm the service has been fully restored for all customers. We will provide a further update once this is complete.

The service interruption with Jamf Insights (EU) has been restored. An issue with the credential rotation process prevented Jamf Insights from authenticating to customers' Jamf Pro instances. We apologize for any inconvenience. We will publish an analysis of this incident once we have completed our internal investigation. Customer Impact: Up to 900 EU tenants were affected. During the interruption, affected customers were unable to issue MDM commands or refresh device data (including extension attributes) through Jamf Insights.

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This issue has been resolved.