Is Jamf down?

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. 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.