Jamf Outage History

Started Mar 07, 2026, 06:39 PM UTC· resolved Mar 09, 2026, 01:32 PM UTC

1. investigating Mar 07, 2026, 06:39 PM UTC

   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.

2. identified Mar 07, 2026, 08:07 PM UTC

   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.

3. identified Mar 08, 2026, 04:05 AM UTC

   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

4. resolved Mar 09, 2026, 01:32 PM UTC

   Jamf Pro 11.25.2 deployment to all standard Pro instances is complete.

Read the full incident report →

Started Feb 23, 2026, 06:55 AM UTC· resolved Feb 23, 2026, 11:01 AM UTC

1. identified Feb 23, 2026, 06:55 AM UTC

   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.

2. monitoring Feb 23, 2026, 10:37 AM UTC

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

3. resolved Feb 23, 2026, 11:01 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 03, 2026, 10:21 PM UTC· resolved Feb 04, 2026, 04:21 PM UTC

1. monitoring Feb 03, 2026, 10:21 PM UTC

   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.

2. resolved Feb 04, 2026, 04:21 PM UTC

   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.

Read the full incident report →

Started Feb 01, 2026, 09:39 PM UTC· resolved Feb 03, 2026, 08:04 PM UTC

1. monitoring Feb 01, 2026, 09:39 PM UTC

   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

2. monitoring Feb 03, 2026, 05:55 PM UTC

   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.

3. monitoring Feb 03, 2026, 05:59 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Feb 03, 2026, 08:04 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 06, 2026, 05:59 PM UTC· resolved Jan 06, 2026, 06:26 PM UTC

1. investigating Jan 06, 2026, 05:59 PM UTC

   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.

2. resolved Jan 06, 2026, 06:26 PM UTC

   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.

Read the full incident report →

Started Dec 10, 2025, 01:53 AM UTC· resolved Dec 10, 2025, 03:37 AM UTC

1. investigating Dec 10, 2025, 01:53 AM UTC

   Date/Time: 2025-12-10 01:30 UTC We are investigating increased latency in SecureDNS policy evaluation for Jamf Security Cloud and Jamf Safe Internet in the APAC region. Customers may experience intermittent delays in DNS resolution. Customer Impact: Partial service degradation; browsing or connectivity may be slower for affected users. Affected Services: SecureDNS (Jamf Security Cloud / Jamf Safe Internet) Affected Regions: APAC (ap-northeast-1) Jamf Engineering is investigating and monitoring performance. Updates to follow. No customer action required at this time.

2. monitoring Dec 10, 2025, 03:20 AM UTC

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

3. resolved Dec 10, 2025, 03:37 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 08, 2025, 12:14 PM UTC· resolved Dec 09, 2025, 03:24 PM UTC

1. investigating Dec 08, 2025, 12:14 PM UTC

   We have been notified of an intermittent issue affecting retrieving the JWT for Jamf Auto Update. This is currently under investigation.

2. monitoring Dec 08, 2025, 03:00 PM UTC

   The issue has been identified, and a fix has been rolled out. We will keep monitoring.

3. resolved Dec 09, 2025, 03:24 PM UTC

   Actions: The intermittent outage with Jamf Auto Update has been restored. .Scaling issues identified during the course of that interruption were identified and remediated. We apologize for any inconvenience. We will publish an analysis of this incident once we have completed our internal investigation. Customer Impact: There should be no ongoing impact.

Read the full incident report →

Started Nov 18, 2025, 04:09 PM UTC· resolved Nov 18, 2025, 04:36 PM UTC

1. investigating Nov 18, 2025, 04:09 PM UTC

   Some customers are experiencing an inability to authenticate via OIDC when accessing the Jamf Protect Admin Console with Jamf ID or their IdP configured in Jamf Account, due to an upstream issue with our IDaaS provider.

2. monitoring Nov 18, 2025, 04:31 PM UTC

   Our IDaaS provider has taken the necessary remediation steps and we are now observing full recovery. We are continuing to monitor this issue, however all symptoms have resolved.

3. monitoring Nov 18, 2025, 04:33 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Nov 18, 2025, 04:36 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 16, 2025, 08:53 PM UTC· resolved Nov 16, 2025, 09:01 PM UTC

1. monitoring Nov 16, 2025, 08:53 PM UTC

   Some customers experienced a temporary inability to authenticate via OIDC when accessing services with Jamf ID or their IdP configured in Jamf Account, due to an upstream issue with our IDaaS provider. Affected Services: All Jamf services relying on Jamf ID / OIDC authentication Affected Regions: Global Business Impact: Temporary service interruption; users unable to log in Estimated Users Impacted: Unknown; global authentication flow Actions: Jamf identified upstream authentication errors beginning at 2025-11-16 20:04 UTC. Services began recovering at 2025-11-16 20:14 UTC after stabilisation of the IDaaS provider. We are monitoring authentication performance as the provider continues their investigation. A support ticket remains open with the vendor for further detail. Workaround / Customer Actions: No customer action required at this time.

2. resolved Nov 16, 2025, 09:01 PM UTC

   Our IDaaS provider has taken the necessary remediation steps and we are now observing full recovery. We are continuing to monitor this issue, however all symptoms have resolved.

Read the full incident report →

Started Nov 05, 2025, 11:25 PM UTC· resolved Nov 06, 2025, 02:25 PM UTC

1. identified Nov 05, 2025, 11:25 PM UTC

   Details: Customers using Device Compliance with Jamf Pro on iOS may see registration fail on devices running Self Service 11.4. Current Actions: We have halted the phased release of 11.4, are verifying update/distribution paths, and are preparing a corrected build to restore registration on affected devices. Impact: Device Compliance registration on iOS for devices running Self Service 11.4. We appreciate your patience and are committed to resolving this as swiftly as possible.

2. identified Nov 06, 2025, 01:28 AM UTC

   Jamf engineering has identified the issue and is working towards service restoration. We have submitted a new build of Self Service for App Store approval and requested expedited review. Currently impacted customers should contact Jamf Support if more immediate remediation required.

3. identified Nov 06, 2025, 03:47 AM UTC

   We’ve submitted a fixed version of Self Service 11.4.1 to Apple for App Store approval and have requested expedited review. We’re currently awaiting approval and do not yet have an ETA for release. We will update this post as soon as the new version becomes available. Customers leveraging Device Compliance and managing iOS devices should disable any automatic app update workflows to prevent Self Service from updating to version 11.4. We appreciate your patience and will continue to provide updates as new information becomes available.

4. identified Nov 06, 2025, 08:00 AM UTC

   We are awaiting approval of Self Service 11.4.1, and have requested expedited review. We do not yet have an ETA for release, though will update this post as soon as the new version becomes available. Customers leveraging Device Compliance and managing iOS devices should disable any automatic app update workflows to prevent Self Service from updating to version 11.4. We appreciate your patience and will continue to provide updates as new information becomes available.

5. monitoring Nov 06, 2025, 10:23 AM UTC

   Earlier today, we identified an issue in Self Service version 11.4 that could cause registration failures when using Device Compliance with Jamf Pro on iOS. This issue was isolated to version 11.4. To resolve this, version 11.4 has been removed and replaced with Self Service 11.4.1, which is functioning as expected. We recommend ensuring that devices are now running Self Service 11.4.1, which is available as of 9:27 UTC. If you continue to experience any problems, please reach out to Jamf Support for further assistance.

6. resolved Nov 06, 2025, 02:25 PM UTC

   PRELIMINARY INVESTIGATION STATEMENT Incident Start Date and Time: 11/5/2025 11:18 PM UTC Incident End Date and Time: 11/6/2025 09:21 AM UTC Duration: 10h 3m Symptoms: Failed registration on devices running Self Service 11.4. Following recent architectural improvements to the iOS Self Service 11.4 application, a device compliance functionality experienced partial outage resulting in failed registration on devices running Self Service 11.4. This issue was not identified during standard regression or beta testing. A detailed root cause analysis will be published once we have completed our internal investigation. We apologize for any inconvenience this caused our customers.

7. postmortem Nov 20, 2025, 02:21 PM UTC

   **Incident Summary** **–** Post-Incident Review **Detailed Root Cause Analysis Report: Device Compliance Broken in iOS Self Service 11.4.0** **Incident Start Date and Time \(in UTC\):** Nov 5, 5:46 PM UTC **Incident End Date and Time \(in UTC\):** Nov 6, 9:21 AM UTC **Severity: SEV2** **Duration: 15h 35m** **Impact:** Global disruption of Microsoft Device Compliance workflow for users using iOS Self Service 11.4.0. **Summary** On 11-05-2025 a release of iOS Self Service 11.4.0 broke the Microsoft Device Compliance workflow. Impacted users could not access resources protected by Microsoft Device Compliance policies. **Root Cause & Timeline** * **Root Cause:** Incorrect configuration of keychain access group in production release of iOS Self Service 11.4.0 * **Key Events:** * November 5, 5:46 PM UTC - Self Service 11.4.0 was released * November 5, 9:50 PM UTC - Issue with Device Compliance worfklow in Self Service 11.4.0 was escalated to Jamf * November 6, 12:18 AM UTC - Self Service 11.4.1 was submitted to Apple for expedited review * November 6, 9:21 AM UTC - Self Service 11.4.1 is available for all customers and users **Business & User Impact** * Users unable to access internal company resources protected by Microsoft Device Compliance policies. * Affected Capabilities: Device Compliance **Gaps Identified** * Gap in automated and human-driven release testing coverage. **Remediation & Next Steps** · The functionality was restored with a new release of iOS Self Service 11.4.1 that reverted the changes introduced in 11.4.0. · Test automation and human-driven release test case coverage was extended to cover the affected workflow end-to-end.

Read the full incident report →

Started Nov 04, 2025, 09:03 AM UTC· resolved Nov 04, 2025, 09:35 AM UTC

1. investigating Nov 04, 2025, 09:03 AM UTC

   We are currently investigating this issue.

2. identified Nov 04, 2025, 09:16 AM UTC

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

3. monitoring Nov 04, 2025, 09:29 AM UTC

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

4. resolved Nov 04, 2025, 09:35 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 20, 2025, 09:47 AM UTC· resolved Oct 20, 2025, 09:42 PM UTC

1. monitoring Oct 20, 2025, 09:47 AM UTC

   We are seeing early signs of recovery across Jamf products and services following a widespread outage on the back of the AWS incident. We are monitoring the situation, Jamf will provide ongoing updates.

2. monitoring Oct 20, 2025, 09:48 AM UTC

   We are continuing to monitor for any further issues.

3. monitoring Oct 20, 2025, 09:50 AM UTC

   We are continuing to monitor for any further issues.

4. monitoring Oct 20, 2025, 10:00 AM UTC

   We are continuing to monitor for any further issues.

5. monitoring Oct 20, 2025, 10:33 AM UTC

   We are continuing to monitor for any further issues.

6. monitoring Oct 20, 2025, 10:58 AM UTC

   The disruption as a result of the AWS incident has been mostly resolved. Remaining customer impact: A subset of customers may see continued impact with API functionality. Jamf will provide ongoing updates.

7. monitoring Oct 20, 2025, 12:25 PM UTC

   The disruption as a result of the AWS incident has been mostly resolved. Remaining customer impact: A small subset of customers may see continued impact with API functionality due to the ongoing AWS latency issues. Jamf will provide ongoing updates.

8. monitoring Oct 20, 2025, 02:17 PM UTC

   Multiple AWS systems continue to stabilize, and we are still seeing limited intermittent impact across the Jamf Platform. The vast majority of Jamf systems remain fully operational. However, a small subset of Identity Automation customers may continue to experience degraded performance or limited functionality due to ongoing AWS latency.

9. monitoring Oct 20, 2025, 03:10 PM UTC

   We continue to experience stability issues resulting from today's AWS outage in us-east-1 region. Jamf School product is currently unavailable.

10. monitoring Oct 20, 2025, 03:12 PM UTC

    We are continuing to monitor for any further issues.

11. monitoring Oct 20, 2025, 04:10 PM UTC

    We've implemented a temporary workaround for Jamf School US region not to rely on AWS services affected by today's AWS outage.

12. monitoring Oct 20, 2025, 04:18 PM UTC

    We are continuing to monitor for any further issues.

13. monitoring Oct 20, 2025, 06:53 PM UTC

    Customers are experiencing an interruption in data processing when using Jamf Protect due to the ongoing AWS latency issues. This is affecting Telemetry, ULogs, and Alerts when sending to Jamf Cloud. Jamf will provide ongoing updates.

14. monitoring Oct 20, 2025, 08:19 PM UTC

    Customers should be back to normal and we continue to monitor the situation.

15. resolved Oct 20, 2025, 09:42 PM UTC

    All services have been restored. We apologize for any inconvenience. We will publish an analysis of this incident once we have completed our internal investigation.

Read the full incident report →

Started Oct 14, 2025, 08:24 PM UTC· resolved Oct 15, 2025, 09:51 AM UTC

1. investigating Oct 14, 2025, 08:24 PM UTC

   We are currently investigating this issue.

2. identified Oct 14, 2025, 08:28 PM UTC

   We have identified the issue, and are working on a solution. Impacted areas are performance of the Admin UI and API.

3. identified Oct 14, 2025, 09:30 PM UTC

   We are continuing to investigate this issue. Impact remains unchanged.

4. identified Oct 14, 2025, 10:19 PM UTC

   We are continuing to investigate the root cause of this issue. Performance has stabilized. We will update again tomorrow.

5. monitoring Oct 15, 2025, 08:15 AM UTC

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

6. resolved Oct 15, 2025, 09:51 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 10, 2025, 01:17 PM UTC· resolved Oct 10, 2025, 01:54 PM UTC

1. investigating Oct 10, 2025, 01:17 PM UTC

   We are currently investigating this issue.

2. identified Oct 10, 2025, 01:17 PM UTC

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

3. monitoring Oct 10, 2025, 01:28 PM UTC

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

4. resolved Oct 10, 2025, 01:54 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 02, 2025, 04:14 AM UTC· resolved Oct 02, 2025, 05:28 AM UTC

1. investigating Oct 02, 2025, 04:14 AM UTC

   We are currently investigating increased latency affecting DNS requests in the ap-northeast-1 (Tokyo) region. All other JSC regions are operating normally. Our Secure Connectivity engineering team is actively working on the issue, but we do not have an estimated time for resolution at this stage.

2. resolved Oct 02, 2025, 05:28 AM UTC

   The earlier issue causing increased latency for DNS requests in the ap-northeast-1 (Tokyo) region has been resolved. Performance has returned to normal and all services are operating as expected. We will continue to monitor closely. Thank you for your patience.

Read the full incident report →

Started Oct 01, 2025, 03:25 PM UTC· resolved Oct 01, 2025, 06:21 PM UTC

1. investigating Oct 01, 2025, 03:25 PM UTC

   We are currently investigating this issue.

2. identified Oct 01, 2025, 03:28 PM UTC

   The issue has been identified. The root cause has been fixed. There are still a number of unprocessed activation messages which are now being worked through. This may cause delays in the processing of new JSC activation requests.

3. monitoring Oct 01, 2025, 05:07 PM UTC

   The older activation messages are now processed. The system is fully operational again. We are monitoring it further.

4. resolved Oct 01, 2025, 06:21 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 24, 2025, 04:59 PM UTC· resolved Oct 13, 2025, 03:20 PM UTC

1. investigating Sep 24, 2025, 04:59 PM UTC

   Jamf Insights may not display mobile devices properly on the "Mobile devices" page. Devices might be missing from this view.

2. identified Sep 25, 2025, 03:53 PM UTC

   The issue has been investigated. Development of a fix is underway.

3. monitoring Sep 29, 2025, 12:06 PM UTC

   We have identified a workaround solution and implemented it selectively. If your instance still encounters this issue, please contact your JAMF customer representative.

4. resolved Oct 13, 2025, 03:20 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 24, 2025, 08:43 AM UTC· resolved Sep 24, 2025, 08:52 AM UTC

1. investigating Sep 24, 2025, 08:43 AM UTC

   We are currently experiencing an outage in eu-central-1, we are investigating the issue and will provide updates shortly.

2. identified Sep 24, 2025, 08:44 AM UTC

   We have identified the issue and are implementing a fix.

3. monitoring Sep 24, 2025, 08:46 AM UTC

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

4. resolved Sep 24, 2025, 08:52 AM UTC

   This incident has been resolved.

5. postmortem Sep 29, 2025, 07:22 AM UTC

   **Incident Date:** September 24, 2025 **Duration:** 15 minutes **Impact:** Temporary unavailability of Jamf School services in eu-central-1 **Summary and Timeline** On September 17th, Jamf School experienced a performance degradation. To remediate and prevent recurrence, we scheduled a schema change to add a supporting index to high-concurrency table. When executed, the index creation acquired an unexpected lock that blocked concurrent application queries, resulting in a full Jamf School service interruption for eu-central-1 customers. Automated and manual monitoring triggered rapid investigation; engineers terminated the locking DDL session and service fully recovered within 15 minutes. **Root Cause & Timeline** **Root Cause:** An online index creation on a high-concurrency table resulted in a blocking table-level lock due to contention and execution plan timing. This prevented critical application queries from proceeding, causing service unavailability. **Key Events:** * 08:30 UTC – Planned schema/index change initiated * 08:31 UTC – Monitoring alert: elevated errors / unresponsive application * 08:34 UTC – Incident response bridge \(war room\) activated * 08:38 UTC – Root cause isolated: blocking lock on core table from index creation * 08:44 UTC – Lock cleared / blocking process stopped * 08:46 UTC – Services fully recovered; continued elevated monitoring initiated. **Business & User Impact** * Jamf School web console: Unavailable for 15 minutes * Device management \(MDM communication\): Temporarily degraded \(devices unable to check in\) * Scope: eu-central-1 environment only * Data integrity: No data loss or corruption observed **Gaps Identified** * The eu-central-1 environment exhibited higher peak concurrent activity than other regions where the same index change had already been applied successfully. * The change was executed during a period of high traffic in eu-central-1 region * Staging and prior rollout experience did not fully reproduce the eu-central-1 peak concurrency, reducing the predictive value of the pre-change assessment. **Remediation Items & Next Steps** * The status page was updated to reflect the outage and ensure customer awareness – Complete * Implement detailed change risk assessment for all database changes \(even those identified as low risk\). * Add pre-change load/lock simulation harness \(prod-like concurrency\) * Enforce execution windows for high-risk database changes \(off-peak / maintenance window\)

Read the full incident report →

Started Sep 19, 2025, 10:00 PM UTC· resolved Sep 20, 2025, 10:05 PM UTC

1. resolved Oct 02, 2025, 06:19 PM UTC

   Between Wed, Sept 10, 22:05 UTC and Fri, Sept 19, 22:05 UTC, customers may have experienced unreported service degradation for Jamf Protect's reporting and forwarding capabilities via JamfCloud. The impacts to the degraded service were not fully understood until now. We're improving monitoring to better detect and surface hidden impacts going forward. During this time window, affected customers may have experienced a lower volume of reported events and telemetry. On-device protections including Threat Prevention, Advanced Threat Controls, Device Controls, and Tamper Prevention remained effective during this time. The underlying issue was resolved, and the service has been stable since Fri, Sept 19, 22:05 UTC.

Read the full incident report →

Started Sep 18, 2025, 08:10 AM UTC· resolved Sep 18, 2025, 10:29 AM UTC

1. investigating Sep 18, 2025, 08:10 AM UTC

   Some environments could now experience slower loading times

2. monitoring Sep 18, 2025, 08:28 AM UTC

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

3. resolved Sep 18, 2025, 10:29 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 16, 2025, 02:09 PM UTC· resolved Sep 16, 2025, 04:00 PM UTC

1. investigating Sep 16, 2025, 02:09 PM UTC

   Self Hosted customers who integrate with US Government sovereign cloud Device Compliance will not be able to create new integrations nor submit compliance data to Microsoft Intune. We have identified the cause of the issue and are working on implementing a fix.

2. identified Sep 16, 2025, 02:10 PM UTC

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

3. identified Sep 16, 2025, 04:00 PM UTC

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

4. resolved Sep 16, 2025, 04:00 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 17, 2025, 11:43 AM UTC· resolved Jul 17, 2025, 12:45 PM UTC

1. resolved Jul 17, 2025, 01:59 PM UTC

   At approximately 11:45 UTC, an outage was detected in the Jamf Cloud Distribution Service. The team quickly identified the root cause and worked to restore the service. Service was restored within 1 hour this incident has been resolved and connectivity to JCDS packages have been restored.

2. postmortem Jul 25, 2025, 05:44 PM UTC

   **Detailed Root Cause Analysis Report: JCDS Outage** **Incident Date:** July 17, 2025 **Duration:** 29 minutes **Impact:**  Global disruption of Jamf Cloud Distribution Service \(JCDS\) **Summary and Timeline** On July 17, 2025, a JCDS outage impacted customers globally when a parameter value did not update, blocking content distribution to end-user devices. Jamf restored full service within 29 minutes. **Root Cause & Timeline** * **Root Cause:** The ‘CsaIssuer’ parameter set in non-production was different than the way it was set in production. * **Key Events:** * 11:43 UTC – JCDS was updated to support authentication through the Tyk API gateway using both ‘tenant\_id’ and ‘Instance\_id’ values. This will support the new API gateway for customers who have not yet adopted tenantID. * 11:45 UTC – Incident triage initiated. Post-deployment alerts investigated. Root cause identified. * 12:12 UTC – Initiated rollback to the prior JCDS deployment. Services restored. * 12:45 UTC – Continued monitoring confirmed rollback was successful and Jamf Pro instances were communicating successfully with JCDS. **Business & User Impact** * Unable to distribute content to devices using the JCDS * Affected products: Jamf Pro * Services affected: Jamf Cloud Distribution Service \(JCDS\). JCDS is a cloud distribution point utilizing server-less deployment architecture leveraging AWS Lambdas to manage file uploads and downloads. Since JCDS is a serverless stack and decoupled from Jamf Pro, changes are deployed to JCDS without customer facing maintenance windows. This type of service does not require downtime for new deployments or upgrades. No customer data loss occurred from this outage. **Gaps Identified** * The cloud formation stack’s URL parameter was not updated when the JCDS deployment pipeline ran for production. The team discovered that modifying the default value in the pipeline template does not automatically update the value in the main template. * Pre-production testing did not reveal this parameter update behavior. **Remediation Items & Next Steps** * The status page was updated to reflect the outage and ensure customer awareness - Complete * The JCDS deployment was rolled back - Complete * Change the pipeline so parameters are passed in the same way in each environment. * Review rollback procedures to ensure for any future deployment issues. * Enhance pipeline monitoring by improving alerts when pipeline tests fail. * Fine tune additional JCDS alerts for service issues.

Read the full incident report →

Started Jun 26, 2025, 10:39 AM UTC· resolved Jun 26, 2025, 11:26 AM UTC

1. investigating Jun 26, 2025, 10:39 AM UTC

   We are currently investigating this issue.

2. monitoring Jun 26, 2025, 11:17 AM UTC

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

3. resolved Jun 26, 2025, 11:26 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 15, 2025, 03:02 AM UTC· resolved Jun 15, 2025, 04:31 AM UTC

1. investigating Jun 15, 2025, 03:02 AM UTC

   We are currently investigating this issue.

2. identified Jun 15, 2025, 03:17 AM UTC

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

3. monitoring Jun 15, 2025, 04:18 AM UTC

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

4. resolved Jun 15, 2025, 04:31 AM UTC

   This incident has been resolved.

5. postmortem Jun 16, 2025, 09:28 PM UTC

   **June 15, 2025 - Jamf SecureDNS Outage RCA** **Summary and Timeline** On June 15, 2025 \(00:00 UTC\), devices using SecureDNS lost internet access due to an outage affecting Web Threat Prevention and Content Filtering capabilities within Jamf Safe Internet, Jamf Protect, and Jamf Trust services.The root cause of the incident was an expired SSL certificate, leading to loss of security features or loss of internet connectivity for end user devices. Although the certificate in question was renewed on May 22nd, 2025, the process used to deploy this certificate had an error, which resulted in incomplete distribution across our global cloud environment.After receiving customer reports of the outage, we investigated, identified the issue and impacted services, and then manually deployed the new certificate to restore the service. We are currently conducting a thorough internal review of the outage and will work to improve the certificate management process to minimize the risk of a repeat occurrence. **Incident Timeline \(UTC\)** * June 15, 2025 at 00:00: The SSL certificate expires * June 15, 2025 at ~00:25 : Troubleshooting efforts begin * June 15, 2025 at 01:45: Root cause identified * June 15, 2025 at 02:30: Teams locate all services requiring updated certificate * June 15, 2025 at 04:15: New certificate is deployed to US regions * June 15, 2025 at 04:30: Jamf verifies that the issue has been resolved across all regions Service disruption duration: 270 minutes **Impact Assessment** Users Affected: All end user devices with Encrypted DNS Gateway configured, lost internet access. Services Impacted: SecureDNS **Remediation Items & Next Steps** We are currently conducting a thorough internal investigation of the events that led to the outage and identifying any gaps that we will need to address to minimize the risk of such occurrences. Our key areas of focus include: **1. Certificate management reviews –** Ensure certificate documentation is up to date and include explicit verification steps for each service component. Enhance existing certificate expiration monitoring. **2. Monitoring** – review and enhance monitoring and alerting of anomalies in traffic patterns. Add in synthetic monitoring. **3. Communications** – Refine internal and customer-facing workflows to ensure rapid response and clarity during incidents. 4\. Evaluate adding additional critical domains to **on-device content filtering safe list.** _For additional questions and needs, please reach out to your customer success manager or log a support ticket at_ [_support.jamf.com_](http://support.jamf.com/)_._

Read the full incident report →

Started Apr 15, 2025, 08:42 PM UTC· resolved Apr 16, 2025, 08:32 PM UTC

1. investigating Apr 15, 2025, 08:42 PM UTC

   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.

2. investigating Apr 15, 2025, 09:07 PM UTC

   An infrastructure issue has been identified and a fix is being worked on currently. At this time we do not have an estimated time of resolution, however all teams have been engaged to address the issue. We apologize for and inconveniences this has caused.

3. investigating Apr 15, 2025, 09:54 PM UTC

   An infrastructure issue has been identified and a fix is being worked on currently. At this time we do not have an estimated time of resolution, however all teams have been engaged to address the issue. We apologize for and inconveniences this has caused.

4. identified Apr 15, 2025, 11:16 PM UTC

   An infrastructure issue has been identified and a fix is in process of being implemented and distributed to all customers. At this time we do not have an estimated time of resolution, however all teams have been engaged to address the issue. We apologize for and inconveniences this has caused.

5. identified Apr 16, 2025, 12:20 AM UTC

   We are still in the process of implementing a fix and distributing it to all customer instances. Some instances are back and functioning, however the resolution is taking longer than anticipated. We are exploring any and all means to ensure all instances are brought up as soon as possible. We apologize for the inconvenience this may have caused.

6. identified Apr 16, 2025, 01:22 AM UTC

   We are still in the process of implementing a fix and distributing it across all customer instances. While some instances have been successfully restored and are functioning as expected, the overall resolution is still in progress. We apologize for any inconvenience this may have caused.

7. identified Apr 16, 2025, 02:26 AM UTC

   We are continuing to roll out the fix across all instances. Our teams are actively monitoring progress to ensure full restoration as quickly and smoothly as possible. We appreciate your patience and understanding as we work to bring all services back to expected performance levels.

8. identified Apr 16, 2025, 03:16 AM UTC

   All premium instances have been successfully updated. We are currently in the process of distributing the update to all standard instances. While some instances are now operational, the overall resolution is taking longer than initially expected. We apologize for any inconvenience this may have caused.

9. identified Apr 16, 2025, 04:16 AM UTC

   We are continuing to roll out the fix across all standard instances. Our teams are actively monitoring progress to ensure full restoration as quickly and smoothly as possible. We appreciate your patience and understanding as we work to bring all services back to expected performance levels.

10. identified Apr 16, 2025, 05:15 AM UTC

    We are continuing to roll out the fix across all standard instances. Our teams are actively monitoring progress to ensure full restoration as quickly and smoothly as possible. We appreciate your patience and understanding as we work to bring all services back to expected performance levels.

11. identified Apr 16, 2025, 06:00 AM UTC

    We are continuing to roll out the fix across all standard instances. Our teams are actively monitoring progress to ensure full restoration as quickly and smoothly as possible. We appreciate your patience and understanding as we work to bring all services back to expected performance levels.

12. identified Apr 16, 2025, 07:03 AM UTC

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

13. identified Apr 16, 2025, 08:00 AM UTC

    We are continuing to roll out the fix across all standard instances. Our teams are actively monitoring progress to ensure full restoration as quickly and smoothly as possible. We appreciate your patience and understanding as we work to bring all services back to expected performance levels.

14. identified Apr 16, 2025, 09:00 AM UTC

    An infrastructure issue has been identified and a fix is in process of being implemented and distributed to all customers. At this time we do not have an estimated time of resolution, however all teams have been engaged to address the issue. We apologize for and inconveniences this has caused.

15. identified Apr 16, 2025, 10:09 AM UTC

    We are still in the process of implementing a fix and distributing it across all customer instances. While some instances have been successfully restored and are functioning as expected, the overall resolution is still in progress. We apologize for any inconvenience this may have caused.

16. identified Apr 16, 2025, 11:08 AM UTC

    We are still in the process of implementing a fix and distributing it across all customer instances. While some instances have been successfully restored and are functioning as expected, the overall resolution is still in progress. We apologize for any inconvenience this may have caused.

17. identified Apr 16, 2025, 12:07 PM UTC

    We are still in the process of implementing a fix and distributing it across all customer instances. While some instances have been successfully restored and are functioning as expected, the overall resolution is still in progress. We apologize for any inconvenience this may have caused.

18. identified Apr 16, 2025, 01:18 PM UTC

    All Premium and APAC instances have been resolved. US and EU Standard instances are currently in progress, and some clusters have been resolved within those regions. Please check the status bar for your specific region for more information. We appreciate your patience and apologize for the inconvenience this has caused.

19. identified Apr 16, 2025, 02:02 PM UTC

    All Premium and APAC instances have been resolved. US and EU Standard instances are currently in progress, and some clusters have been resolved within those regions. Please check the status bar for your specific region for more information. We appreciate your patience and apologize for the inconvenience this has caused.

20. identified Apr 16, 2025, 03:04 PM UTC

    All Premium and APAC instances have been resolved. EU & US standard instances have been largely restored, for those with a custom URL service will unfortunately continue to be intermittent. Please check the status bar for your specific region for more information. We appreciate your patience and apologise for the inconvenience this has caused.

21. identified Apr 16, 2025, 04:09 PM UTC

    UPDATE: A small subset of our standard instances in each of the identified regions in the EU and US are still impacted. Those with a custom URL service will, unfortunately, continue to be intermittent as we work through them as quickly as possible. Please check the status bar for your specific region for more information. We appreciate your patience and apologize for the inconvenience this has caused. We will provide an update in the next hour.

22. identified Apr 16, 2025, 05:18 PM UTC

    UPDATE: We continue working through a smaller subset of our standard instances with a custom URL in each identified EU and US regions. Please check the status bar for your specific region for more information. We appreciate your patience. We will continue to provide updates in the next hour. *We have also restarted our sandbox, trial, and beta classes in all regions. No outage expected, just a logout and log back in.

23. monitoring Apr 16, 2025, 06:05 PM UTC

    UPDATE: We have resolved all Production instances in all regions at this time. We still have some ongoing restarts in our non-production environments, including sandbox, trial, and betas. At this time, we will monitor the situation closely for the next hour before resolving the incident to ensure all systems are functional. Again, we apologize and greatly appreciate your patience during the incident.

24. monitoring Apr 16, 2025, 07:26 PM UTC

    UPDATE: A subset of Standard Production instances with a custom URL require a restart of the service, which will cause a logout situation. This impacts all regions. We appreciate your patience and apologize for the inconvenience this has caused, we will provide an update in the next hour.

25. resolved Apr 16, 2025, 08:32 PM UTC

    At this time, we have resolved all instances in all classes. We appreciate your patience and apologize for the inconvenience they may have caused.

26. postmortem Apr 18, 2025, 02:31 PM UTC

    **Root Cause Analysis of Jamf Pro Outage** During scheduled maintenance on a low-level component of the Jamf Pro cloud infrastructure, an update failed, resulting in an outage that affected Jamf Pro customers. The component in question is a critical part of our auto-scaling infrastructure, which enables Jamf to support millions of devices. The failure of this upgrade led to a widespread outage. * The update was not backwards-compatible, making it impossible to roll back to the previous version. * We were able to quickly restore services for some configurations, including Premium Cloud customers. * Larger clusters could not be recovered through the standard workflow and required manual intervention. We had to downsize these clusters to enable recovery. * For customers with custom domains, an additional step was needed before service could be fully restored.

Read the full incident report →