54 Jamf incidents · 2025年2月 — official updates, affected components, duration and resolution details.
一部のJamf Proの顧客に影響を与える問題が特定されました。 次回のアップデートは45分以内に行います.
上流サービスプロバイダで状況を監視しています。 プロバイダがその事件を閉鎖したことを確認したら、解決に移ります.
この事件は解決しました.
公式のインシデント更新を自動翻訳しています。
Jamf は、米国の顧客向けの Blueprint 管理に影響を及ぼす問題について調査しています。 一部の顧客は、この時点でBlueprintsを管理することができない場合があります。 当社のエンジニアリングチームは積極的に調査を行い、より多くの情報が利用できるように更新を提供します。 症状:米国を拠点とする顧客は、Blueprintsを管理するための完全な不能性を経験しています。 顧客の影響: 欠陥のあるサービス:ブループリント(ブループリント管理システム) 感染地域:米国
今後もこの問題について調査を続けてまいります.
Blueprint管理サービスは現在運用中ですが、エンジニアリングチームは引き続き監視しています。 Blueprintsを管理する問題を経験した米国の顧客は、もはや影響が見られないはずです。 誠に有難うございますが、ご迷惑をお掛けし、誠に有難うございます.
この事件は解決しました。 米国の顧客向けBlueprint管理サービスが本格稼働しており、さらなる影響は期待できません。 ご迷惑をおかけいたしますが、何卒ご理解賜りますようお願い申し上げます.
公式のインシデント更新を自動翻訳しています。
Jamf Trustアプリが顧客デバイス上で非アクティブ化される問題を認識しています。 アプリが非アクティブ化される一方で、その保護はゼロトラストネットワークアクセス(ZTNA)やコンテンツフィルタリングを含みます。 これは、iOS、macOS、Android、Windowsのすべてのプラットフォーム上のデバイスに影響を与えます。 当社のエンジニアリングチームは、原因を特定し、修正が生産に展開されています。 修正が生きていると、影響を受けたデバイスは、エンドユーザーまたは管理者アクションを必要とする、再アクティブ化する必要があります。 修正が確認されたら、こちらから詳細を投稿します.
修正は現在生産中ですが、問題が拡大しなくなったため、追加のデバイスは影響しません。 Jamf Trust アプリが既に非アクティブ化されているデバイスは、自動的に解決されない場合があります。一部のデバイスは、自分で復元できますが、他のデバイスは追加の是正手順が必要になります。 私たちは、影響を受けた顧客のレポートをコンパイルし、ゼロトラストネットワークアクセス(ZTNA)やコンテンツフィルタリングなど、デバイスを再活性化し、保護を回復するためのステップバイステップの手順で直接影響を受けたアカウントに到達するために取り組んでいます。 また、その指示をここに掲示しますので、全員に影響を受けることができます.
生産の修正は保持し続け、追加のデバイスは影響を受けません。 当社は、Jamf Trustアプリが非アクティブ化したデバイス向けの、影響を受けた顧客リストを引き続きコンパイルし、修正手順を準備しています.
問題は解決しました。 Jamf Trust アプリは、デバイスに不意に非アクティブ化されることはありません。 顧客の影響の維持: 以前非アクティブ化していたJamf Trustアプリでは、再アクティブ化する必要があります。 導入設定によっては、自動または手動再活性化が必要になる場合があります。 デバイスを再アクティブにするためのサポートは、Jamfアカウントポータルにログインし、Jamf Trustアプリの非アクティブ化を参照するチケット(連絡先サポート)を作成してください。 Jamf Trust アプリが非アクティブ化される一方で、Zero Trust Network Access (ZTNA) やコンテンツフィルタリングなど、その保護は強化されていません。 これは、iOS、macOS、Android、Windowsのすべてのプラットフォーム上のデバイスに影響を与えます。 大変申し訳ございません.
公式のインシデント更新を自動翻訳しています。
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.