Jamf 장애 기록

1. 2026년 9월 3일 PM 10:05 UTCidentified

   문제는 Jamf Pro 고객에 영향을 미치는 것으로 확인되었습니다. 우리는 해결하고 45 분 안에 다음 업데이트를 제공합니다.

2. 2026년 9월 4일 AM 12:17 UTCmonitoring

   우리는 업스트림 서비스 제공 업체와 상황을 모니터링하고 있습니다. 우리는 일단 공급자가 그들의 사건이 닫히는 것을 한 번 해결하기 위하여 이동할 것입니다.

3. 2026년 9월 4일 AM 12:22 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 17일 AM 9:54 UTCinvestigating

   Jamf는 미국의 Blueprint 관리에 영향을 미치는 문제를 조사하고 있습니다. 이 시간에 Blueprints를 관리 할 수 없습니다. 우리의 엔지니어링 팀은 적극적으로 투자하고 더 많은 정보를 제공 할 것입니다. Symptoms: 미국 기반 고객은 Blueprints를 관리할 수 있는 완벽한 Inability를 경험하고 있습니다. 고객 충격: 서비스: Blueprints (블루프린트 관리 시스템) 지역: 미국

2. 2026년 8월 17일 AM 9:56 UTCinvestigating

   이 문제를 조사하고 있습니다.

3. 2026년 8월 17일 AM 10:19 UTCmonitoring

   Blueprint 관리 서비스는 현재 운영되고 있지만 엔지니어링 팀은 여전히 모니터링하고 있습니다. Blueprints를 관리하는 데 경험이 풍부한 미국 고객은 더 이상 어떤 영향을 미치지 않습니다. 우리는 불편을 끼쳐 드려 대단히 감사합니다.

4. 2026년 8월 17일 AM 11:28 UTCresolved

   이 사건은 해결되었습니다. 미국 고객을 위한 Blueprint 관리 서비스는 완전히 운영되고, 더 이상 충격은 예상되지 않습니다. 우리는이 발생하고 당신의 인내에 감사드립니다 어떤 불편을 위해 사과합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 24일 AM 8:56 UTCidentified

   Jamf Trust 앱이 고객 기기에서 비활성화되는 문제가 있습니다. 앱이 비활성화되었지만, Zero Trust Network Access (ZTNA) 및 콘텐츠 필터링을 포함한 보호 기능은 시행되지 않습니다. 모든 플랫폼에서 디바이스에 영향을 줍니다: iOS, macOS, Android 및 Windows. 우리의 엔지니어링 팀은 원인을 확인하고 수정은 생산에 배포됩니다. 수정이 생길 때, 영향을받는 장치는 최종 사용자 또는 관리자 작업을 필요로 할 수 있습니다 재 활성화해야합니다. 우리는 수정이 확인 된대로 더 많은 세부 사항을 게시 할 것입니다.

2. 2026년 7월 24일 AM 9:53 UTCmonitoring

   수정은 이제 생산에 있으며 확산에서 문제가 중단되었으므로 추가 장치가 영향을 미치지 않습니다. Jamf Trust 앱이 이미 비활성화 된 장치는 자동으로 해결되지 않을 수 있습니다. - 일부는 자신의 회복 할 수 있지만 다른 사람은 추가 치료 단계를 필요로합니다. 우리는 영향을 받은 고객의 보고서를 준수하고 Zero Trust Network Access (ZTNA) 및 콘텐츠 필터링을 포함한 장치 및 복원 보호를 다시 활성화하기 위해 단계별 지침과 함께 영향을받는 계정을 직접 도달하기 위해 노력하고 있습니다. 우리는 또한 여기에 그 지시를 게시합니다. 그들은 모두 영향을받습니다.

3. 2026년 7월 24일 AM 11:52 UTCmonitoring

   생산에 대한 수정은 계속 유지하고 추가 장치가 영향을받지 않습니다. Jamf Trust 앱이 비활성화된 기기에 대한 반복적인 지침을 준비하고 있습니다.

4. 2026년 7월 24일 PM 4:05 UTCresolved

   문제는 해결되었습니다. Jamf Trust 앱은 더 이상 기기에서 비활성화되지 않습니다. Remaining Customer Impact: 이전에 비활성화 된 Jamf Trust 앱의 경우 재 활성화해야합니다. 배포 설정에 따라 자동 또는 수동 반응이 필요할 수 있습니다. reactivating Device에 대한 지원은 Jamf 계정 포털에 로그인하고, Jamf Trust 앱 비활성화를 참조하는 티켓(연락처 지원)를 만듭니다. Jamf Trust 앱이 비활성화되었지만 Zero Trust Network Access (ZTNA) 및 콘텐츠 필터링을 포함한 보호 기능은 시행되지 않습니다. 모든 플랫폼에서 디바이스에 영향을 줍니다: iOS, macOS, Android 및 Windows. 우리는 어떤 불편든지를 위해 apologize.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 23일 PM 5:42 UTCinvestigating

   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.

2. 2026년 6월 23일 PM 6:38 UTCidentified

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

3. 2026년 6월 23일 PM 8:57 UTCmonitoring

   A fix has been implemented and we are monitoring the results. Performance is expected to continually improve over the next several hours.

4. 2026년 6월 24일 PM 1:08 UTCresolved

   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.

1. 2026년 6월 22일 AM 11:34 UTCidentified

   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.

2. 2026년 6월 22일 AM 11:54 UTCmonitoring

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

3. 2026년 6월 22일 PM 12:01 UTCresolved

   This incident has been resolved.

1. 2026년 6월 15일 PM 1:32 UTCinvestigating

   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.

2. 2026년 6월 15일 PM 1:33 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 6월 15일 PM 2:18 UTCidentified

   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.

4. 2026년 6월 15일 PM 2:46 UTCmonitoring

   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.

5. 2026년 6월 15일 PM 4:19 UTCmonitoring

   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.

6. 2026년 6월 15일 PM 5:02 UTCresolved

   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.

1. 2026년 5월 18일 AM 10:13 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 5월 18일 AM 10:53 UTCidentified

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

3. 2026년 5월 18일 PM 2:45 UTCmonitoring

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

4. 2026년 5월 18일 PM 5:50 UTCresolved

   This issue has been resolved.

1. 2026년 5월 14일 PM 2:54 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 5월 14일 PM 3:13 UTCidentified

   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

3. 2026년 5월 14일 PM 9:08 UTCidentified

   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

4. 2026년 5월 15일 AM 1:01 UTCmonitoring

   Normal operations has resumed. Monitoring will continue.

5. 2026년 5월 15일 AM 1:57 UTCresolved

   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.

1. 2026년 4월 21일 AM 2:15 UTCinvestigating

   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.

2. 2026년 4월 21일 AM 2:36 UTCidentified

   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.

3. 2026년 4월 21일 AM 2:45 UTCmonitoring

   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.

4. 2026년 4월 21일 AM 3:03 UTCresolved

   Full service has been restored, and we will conduct a post-incident review. We appreciate your patience and apologise for any disruption caused.

1. 2026년 4월 6일 PM 3:41 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 4월 6일 PM 4:37 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 4월 6일 PM 5:51 UTCidentified

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

4. 2026년 4월 6일 PM 8:04 UTCmonitoring

   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.

5. 2026년 4월 7일 PM 1:06 UTCresolved

   This incident has been resolved.

1. 2026년 4월 2일 PM 12:53 UTCidentified

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

2. 2026년 4월 2일 PM 1:56 UTCidentified

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

3. 2026년 4월 2일 PM 3:37 UTCmonitoring

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

4. 2026년 4월 2일 PM 9:07 UTCresolved

   Monitoring complete. No additional issues.

1. 2026년 3월 26일 PM 2:05 UTCidentified

   We are investigating an issue around Blueprints affecting customers running versions of Jamf Pro 11.24 and lower.

2. 2026년 3월 26일 PM 3:00 UTCmonitoring

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

3. 2026년 3월 26일 PM 9:03 UTCresolved

   This incident has been resolved.

1. 2026년 3월 26일 PM 1:42 UTCinvestigating

   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.

2. 2026년 3월 26일 PM 1:44 UTCidentified

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

3. 2026년 3월 26일 PM 2:20 UTCidentified

   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.

4. 2026년 3월 26일 PM 3:29 UTCmonitoring

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

5. 2026년 3월 26일 PM 3:52 UTCresolved

   This incident has been resolved.

1. 2026년 3월 11일 PM 3:45 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 3월 11일 PM 4:06 UTCidentified

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

3. 2026년 3월 11일 PM 4:36 UTCmonitoring

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

4. 2026년 3월 11일 PM 7:46 UTCresolved

   This incident has been resolved.

1. 2026년 3월 9일 PM 1:58 UTCinvestigating

   We are experiencing performance issues within the US West 2 Region.  We are actively investigating this issue.

2. 2026년 3월 9일 PM 3:17 UTCidentified

   The issue has been identified and we are working on resolution.

3. 2026년 3월 9일 PM 4:21 UTCidentified

   We continue to work on a fix for this issue.

4. 2026년 3월 9일 PM 4:39 UTCmonitoring

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

5. 2026년 3월 9일 PM 5:16 UTCresolved

   This incident has been resolved.

1. 2026년 3월 7일 PM 6:39 UTCinvestigating

   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. 2026년 3월 7일 PM 8:07 UTCidentified

   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. 2026년 3월 8일 AM 4:05 UTCidentified

   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. 2026년 3월 9일 PM 1:32 UTCresolved

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

1. 2026년 2월 23일 AM 6:55 UTCidentified

   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. 2026년 2월 23일 AM 10:37 UTCmonitoring

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

3. 2026년 2월 23일 AM 11:01 UTCresolved

   This incident has been resolved.

1. 2026년 2월 3일 PM 10:21 UTCmonitoring

   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. 2026년 2월 4일 PM 4:21 UTCresolved

   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.

1. 2026년 2월 1일 PM 9:39 UTCmonitoring

   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. 2026년 2월 3일 PM 5:55 UTCmonitoring

   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. 2026년 2월 3일 PM 5:59 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2026년 2월 3일 PM 8:04 UTCresolved

   This incident has been resolved.

1. 2026년 1월 6일 PM 5:59 UTCinvestigating

   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. 2026년 1월 6일 PM 6:26 UTCresolved

   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.