54 recorded Jamf incidents since February 2025, with official updates, affected components, duration and resolution information.
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.
We are currently investigating this issue.
The issue has been identified, we've started the process to resume normal operations. Users may continue to experience: - Application slowness and performance degradation for customers using the European cluster - Potential delays in request processing and page load times
The process to resume normal operations is still in progress. Users may continue to experience: - Application slowness and performance degradation for customers using the European cluster - Potential delays in request processing and page load times
Normal operations has resumed. Monitoring will continue.
The interruption with Jamf School has been resolved. This issue effected read speed with our database. We apologize for any inconvenience. Customer Impact: General slowness of Jamf School application in the European cluster.
Customers using Jamf Trust on macOS and iOS/iPadOS are experiencing connectivity failures. Devices are unable to establish a stable tunnel connection and are cycling between bypass mode and tunnel recovery. General internet access remains unaffected, but ZTNA and Private Access functionality is disrupted. Our engineering team is actively investigating the root cause. This is being treated as a critical incident and is our top priority. We appreciate your patience and are committed to resolving this as swiftly as possible.
We have identified that VPN load balancer infrastructure in the APAC region (apse2) experienced an unexpected restart due to resource constraints. Infrastructure has been scaled up and services are being restored. No action is required from customers at this stage, and we will update here once connectivity is restored.
Infrastructure has been successfully scaled up. Services are being monitored to confirm stability. No action is required from customers and Jamf Trust should reconnect automatically.
Full service has been restored, and we will conduct a post-incident review. We appreciate your patience and apologise for any disruption caused.
We are currently investigating this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results. Jamf Protect Console performance is restored. Alerting and Insights may continue to see some delays as the backlog processes.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
Monitoring complete. No additional issues.
We are investigating an issue around Blueprints affecting customers running versions of Jamf Pro 11.24 and lower.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The Jamf Pro integration with GCC High Device Compliance is currently not working. New integrations and new registrations are not possible and device compliance state is not sent. We have identified the cause and we are currently working towards a resolution.
The issue has been identified and a fix is being implemented.
The GCC High Device Compliance for Jamf Pro - Standard and Premium is restored, we are continuing to work towards restoring service for Jamf Pro - Premium Cloud Plus.
A fix has been implemented 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 pursued.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are experiencing performance issues within the US West 2 Region. We are actively investigating this issue.
The issue has been identified and we are working on resolution.
We continue to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
An issue has been identified that is happening with Jamf Pro 11.25 where Smart Groups causes an invalid membership list when using criteria around Device Ownership Type and Personal Device Profiles. We are continuing to investigate at this time.
The issue has been identified and a fix is being investigated. In the interim, identification and workaround instructions are detailed below. Identification and Workaround: To identify which Mobile Device Smart Group may be affected, create a Jamf Pro summary (Settings > Jamf Pro summary) with the checkbox selected for Mobile Devices > Smart Mobile Device Groups. The resulting summary file can be searched for Device Ownership Type to find related smart groups. Review the smart group configurations and ensure that any configurations relating to Device Ownership Type have a valid value. These valid values can be found in edit mode and clicking into the ellipsis ... and are also listed here: Personal (Account-Driven User Enrollment) Personal (User Enrollment) Institutional Institutional (Account-Driven Device Enrollment) If any other value not listed is inputted, the smart group calculation will include Institutional Device Ownership Type devices in the group membership. Contact Jamf Support for questions or assistance.
A fix is being deployed via Jamf Pro 11.25.2; see the following post for more information: https://community.jamf.com/release-announcements-177/jamf-pro-11-25-2-standard-hosted-upgrades-57838
Jamf Pro 11.25.2 deployment to all standard Pro instances is complete.
We are currently experiencing an issue with our emailing service that is preventing outbound emails from being delivered. Our team is actively investigating and working to restore full functionality as soon as possible. We apologize for any inconvenience this may cause and will provide an update once the issue is resolved.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Actions: A fix has been applied for notifications of App Store app flagging as sideloaded. Customer Action Required: UEM Synchronization To remediate the side-loaded app events identified during this incident, please perform a UEM sync between Jamf Security Cloud and your MDM solution. This sync will also update device risk state used by Access policies. To synchronize: Navigate to Jamf Security Cloud > Integrations > UEM Connection > Settings > Actions > Synchronize If you have questions or need assistance, please contact Jamf Support. We apologize for any inconvenience.
This incident has been resolved. Actions: A fix has been applied for notifications of App Store app flagging as sideloaded. Customer Action Required: UEM Synchronization To remediate the side-loaded app events identified during this incident, please perform a UEM sync between Jamf Security Cloud and your MDM solution. This sync will also update device risk state used by Access policies. To synchronize: Navigate to Jamf Security Cloud > Integrations > UEM Connection > Settings > Actions > Synchronize If a UEM sync was previously performed and alerts still persist, please perform a full sync again. The issue has now been fully resolved and syncing will remediate the false positive events. Alternatively, you can manually archive the specific threat in Radar > Threats view. To synchronize: Navigate to Jamf Security Cloud > Integrations > UEM Connection > Settings > Actions > Synchronize If you have questions or need assistance, please contact Jamf Support.
Devices running iOS/iPadOS 26.1 with On-Device Content Filtering enabled may experience loss of network connectivity if Jamf Trust is updated to version 11.47.0 or later while on an unstable network. In some cases, the update may hang and require a factory reset to recover. This issue affects any app implementing the On-Device Content Filtering extension on iOS and is not specific to Jamf Trust. Recommended action: Update devices to iOS/iPadOS 26.2 before updating Jamf Trust. Apple resolved the underlying issue in 26.2. If this is not yet possible, ensure devices are on a stable network during updates. No service disruption is currently ongoing. Jamf Nation Post: https://community.jamf.com/general-discussions-2/jamf-trust-app-updates-on-ios-ipados-26-1-connectivity-issue-57586
Apple resolved the underlying issue in 26.2. Customers are advised to update devices to iOS/iPadOS 26.2 before updating Jamf Trust. If this is not yet possible, ensure devices are on a stable network during updates.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently experiencing degraded data loading in Jamf Security Cloud Console. Some pages and widgets may not load properly. As a temporary workaround, refreshing the page may resolve loading issues in some cases. Our team is actively investigating the root cause and will provide updates as more information becomes available.
The engineering team has investigated the issue, identified the root cause, and implemented a fix. The degradation should now be resolved and all systems should be fully operational.