Jamf outage history

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.

Jamf Security Cloud / Private Access underwent a brief maintenance window during which normal service was temporarily unavailable. The maintenance began at 7:04 AM UTC and ended at 8:04 AM UTC, after which the service returned to full operation. The period was limited to maintenance and no extended impact occurred.

Jamf conducted a scheduled maintenance window that briefly paused access to Jamf ID and Jamf Account. Impact began when the maintenance window started at 4:14 PM UTC and concluded at 5:34 PM UTC, lasting about an hour and twenty minutes. During this period, access to Jamf ID and Jamf Account was temporarily limited, with services returning to normal after the maintenance window completed. The Jamf status page documented the transition from up to maintenance and back to up for these components, indicating a short, planned disruption.

Jamf Security Cloud faced a propagation delay for Data Policy changes, preventing new configurations from taking effect promptly. The issue began at Sep 10, 2026 4:09 PM UTC as the service moved into a degraded state and escalated to an outage for policy updates by Sep 10, 2026 4:54 PM UTC. The disruption affected the Data Policy channel within Jamf Security Cloud, with related components such as Jamf Account and Jamf ID entering maintenance during investigation. As a result, updated configurations could take longer to propagate and some devices might not receive the expected Data Policy updates in a timely manner.

During the following period, Jamf provided ongoing updates and identified an additional impact: at Sep 11, 2026 4:44 AM UTC devices that change network context (roaming vs domestic) during the incident would not receive the corresponding Data Policy update, while Access Policies and Threat Prevention Policy remained unaffected. A fix was implemented and replication to edge regions was required, a process expected to take a few hours. By Sep 11, 2026 1:59 PM UTC the Data Policy component had moved from warn to up, and by Sep 11, 2026 4:09 PM UTC Jamf Account and Jamf ID were restored to up as replication completed.

With policy replication completing across edge regions, the incident was declared resolved and Jamf Security Cloud returned to normal operation. Users should now experience timely propagation of policy changes across devices, with edge regions updated accordingly.

An incident in Jamf caused content filtering to stop working for a subset of customers in APAC between 1:19 PM UTC and 1:44 PM UTC. Jamf's Secure Proxies in APAC — covering Hong Kong, Japan, Singapore, and South Korea — briefly went down, affecting users in AP East1, AP Northeast1, AP Northeast2, and AP Southeast1 regions. Some previously blocked sites may have been accessible during the disruption. The issue has been resolved with services restored to normal, and no customer action was required.

A subset of Jamf customers in APAC experienced content filtering not applying as expected, with some blocked content slipping through. The issue began around 1:04 PM UTC and by 1:19 PM UTC the disruption was observed across content filtering. Affected components included Jamf Pro Premium in ap-northeast-1 and ap-southeast-2, Jamf Pro Standard in the same regions, and Jamf Security Cloud Secure Proxies in APAC regions (Hong Kong, Japan, Singapore, South Korea). The incident spanned AP East1, AP Northeast1, AP Northeast2, and AP Southeast1 regions, indicating a regional impact. Jamf investigated and worked on a fix, and the affected components returned to normal by 1:44 PM UTC. No customer action was required. The outcome was a partial outage with degraded filtering rather than a full service outage.

A partial outage impacted Jamf Pro - Premium in the us-west-2 region, disrupting scripting and app installation for some customers. The disruption began at 10:09 PM UTC and lasted a little over two hours, with user reports noting issues such as scripting not running and apps failing to install (for example, a New Zealand user reported problems at 11:56 PM UTC).

Jamf documented the incident on the status page as a Partial Outage affecting Jamf Pro - Premium in us-west-2, and promised a follow-up update within 45 minutes. The service recovered by 12:19 AM UTC, at which point Jamf Pro - Premium returned to normal operation. The impact appears regional to us-west-2 and did not indicate a global outage.

Jamf faced a brief outage affecting the Blueprint Management feature for US customers. The issue began at 9:59 AM UTC and progressed to a degraded state at 10:19 AM UTC before full recovery by 10:24 AM UTC. The status page indicated Blueprint Management was unavailable while the team investigated, and service was restored shortly afterward. The disruption appears limited to this component and did not indicate a broader Jamf service impact.

An outage occurred when the Jamf Trust app was deactivated on customer devices, leaving protections such as Zero Trust Network Access (ZTNA) and content filtering unenforced. The issue affected devices across iOS, macOS, Android, and Windows. The incident began at 8:59 AM UTC with the Trust app deactivation for all customers. Jamf identified the cause and said a fix was being deployed to production; once the fix is live, affected devices will need to be reactivated.