Live  /  Jamf  /  Incident

Jamf: Jamf Security Cloud - Delay in Data Policy Change Propagation

Jamf · jamf.comMajor incidentResolved2026-09-11 11:26 UTC
Public — what happened

Summary

Jamf reported a major issue in Jamf Security Cloud in which changes to data policies were slow to take effect, beginning on 2026-09-10 at 16:05 UTC. Jamf said it had applied a fix and addressed the underlying cause, though it did not describe what that cause was. The company noted that updated policies still had to be copied out to all of its edge regions, a process it expected to take a few hours, and it listed the incident as being monitored with a resolution time of 2026-09-11 at 14:08.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Jamf against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Jamf: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Jamf report →

More from Jamf

Covered in The Squid’s Ink, Week 38, 2026, our weekly internet health report.

The full archive is on the Jamf status & history page.

Related: Jamf status & history. SquidGrid is not affiliated with Jamf.