Störungsverlauf von Jamf

1. 3. September 2026 um 22:05 UTCidentified

   Es wurde ein Problem identifiziert, das einige Jamf Pro-Kunden betrifft. Wir arbeiten daran, dies zu lösen und werden das nächste Update in 45 Minuten bereitstellen.

2. 4. September 2026 um 00:17 UTCmonitoring

   Wir beobachten die Situation mit dem vorgelagerten Dienstleister. Wir werden zu Resolved wechseln, sobald der Anbieter bestätigt, dass sein Vorfall abgeschlossen ist.

3. 4. September 2026 um 00:22 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 17. August 2026 um 09:54 UTCinvestigating

   Jamf untersucht ein Problem, das das Blueprint-Management für Kunden in den USA betrifft. Einige Kunden können Blueprints derzeit möglicherweise nicht verwalten. Unser Engineering-Team untersucht aktiv und wird Updates bereitstellen, sobald mehr Informationen verfügbar sind. Symptome: US-amerikanische Kunden erleben eine völlige Unfähigkeit, Blueprints zu verwalten. Customer Impact: Betroffene Dienste: Blueprints (Blueprint Management System) Betroffene Regionen: USA

2. 17. August 2026 um 09:56 UTCinvestigating

   Wir werden dieses Problem weiter untersuchen.

3. 17. August 2026 um 10:19 UTCmonitoring

   Blueprint Management Services sind jetzt in Betrieb, aber unser Engineering-Team überwacht immer noch. Kunden in den USA, die Probleme mit der Verwaltung von Blueprints hatten, sollten keine Auswirkungen mehr sehen. Wir entschuldigen uns für die Unannehmlichkeiten und danken Ihnen für Ihre Geduld, während wir dieses Problem gelöst haben.

4. 17. August 2026 um 11:28 UTCresolved

   Dieser Vorfall wurde behoben. Blueprint Management Services für US-Kunden sind voll funktionsfähig und es werden keine weiteren Auswirkungen erwartet. Wir entschuldigen uns für alle Unannehmlichkeiten, die dies verursacht haben könnte, und danken Ihnen für Ihre Geduld.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 24. Juli 2026 um 08:56 UTCidentified

   Uns ist ein Problem bekannt, das dazu führt, dass die Jamf Trust App auf Kundengeräten deaktiviert wird. Während die App deaktiviert ist, werden ihre Schutzmaßnahmen - einschließlich Zero Trust Network Access (ZTNA) und Inhaltsfilterung - nicht durchgesetzt. Dies betrifft Geräte auf allen Plattformen: iOS, macOS, Android und Windows. Unser Engineering-Team hat die Ursache identifiziert und die Lösung wird in der Produktion eingesetzt. Sobald der Fix live ist, müssen die betroffenen Geräte reaktiviert werden, was möglicherweise eine Endbenutzer- oder Administratoraktion erfordert. Wir werden hier weitere Details veröffentlichen, sobald der Fix bestätigt ist.

2. 24. Juli 2026 um 09:53 UTCmonitoring

   Ein Fix ist jetzt in Produktion und hat die Ausbreitung des Problems gestoppt, so dass keine zusätzlichen Geräte betroffen sind. Geräte, bei denen die Jamf Trust-App bereits deaktiviert wurde, werden möglicherweise nicht automatisch aufgelöst – einige können sich von selbst erholen, andere erfordern jedoch zusätzliche Sanierungsschritte. Wir erstellen einen Bericht über betroffene Kunden und arbeiten daran, betroffene Konten direkt mit Schritt-für-Schritt-Anweisungen zu erreichen, um ihre Geräte zu reaktivieren und den Schutz wiederherzustellen, einschließlich Zero Trust Network Access (ZTNA) und Inhaltsfilterung. Wir werden diese Anweisungen auch hier veröffentlichen, damit sie allen Betroffenen zur Verfügung stehen.

3. 24. Juli 2026 um 11:52 UTCmonitoring

   Der Fix in der Produktion hält weiter und es sind keine zusätzlichen Geräte betroffen. Wir erstellen derzeit noch die Liste der betroffenen Kunden und erstellen die Mängelbehebungsanweisungen für Geräte, bei denen die Jamf Trust-App deaktiviert wurde.

4. 24. Juli 2026 um 16:05 UTCresolved

   Das Problem ist gelöst. Die Jamf Trust App wird auf Geräten nicht mehr unerwartet deaktiviert. Remaining Customer Impact: Für Jamf Trust Apps, die zuvor deaktiviert wurden, müssen sie reaktiviert werden. Je nach Einsatzkonfiguration kann dies automatisch erfolgen oder eine manuelle Reaktivierung erfordern. Für Unterstützung beim Reaktivieren von Geräten melden Sie sich bitte im Jamf Account Portal an und erstellen Sie ein Ticket (Kontaktsupport), das auf die Deaktivierung der Jamf Trust App verweist. Während die Jamf Trust-App deaktiviert ist, werden ihre Schutzmaßnahmen - einschließlich Zero Trust Network Access (ZTNA) und Inhaltsfilterung - nicht durchgesetzt. Dies betrifft Geräte auf allen Plattformen: iOS, macOS, Android und Windows. Wir entschuldigen uns für jegliche Unannehmlichkeiten.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 23. Juni 2026 um 17: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. 23. Juni 2026 um 18:38 UTCidentified

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

3. 23. Juni 2026 um 20: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. 24. Juni 2026 um 13: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. 22. Juni 2026 um 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. 22. Juni 2026 um 11:54 UTCmonitoring

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

3. 22. Juni 2026 um 12:01 UTCresolved

   This incident has been resolved.

1. 15. Juni 2026 um 13: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. 15. Juni 2026 um 13:33 UTCinvestigating

   We are continuing to investigate this issue.

3. 15. Juni 2026 um 14: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. 15. Juni 2026 um 14: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. 15. Juni 2026 um 16: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. 15. Juni 2026 um 17: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. 18. Mai 2026 um 10:13 UTCinvestigating

   We are currently investigating this issue.

2. 18. Mai 2026 um 10:53 UTCidentified

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

3. 18. Mai 2026 um 14:45 UTCmonitoring

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

4. 18. Mai 2026 um 17:50 UTCresolved

   This issue has been resolved.

1. 14. Mai 2026 um 14:54 UTCinvestigating

   We are currently investigating this issue.

2. 14. Mai 2026 um 15: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. 14. Mai 2026 um 21: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. 15. Mai 2026 um 01:01 UTCmonitoring

   Normal operations has resumed. Monitoring will continue.

5. 15. Mai 2026 um 01: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. 21. April 2026 um 02: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. 21. April 2026 um 02: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. 21. April 2026 um 02: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. 21. April 2026 um 03: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. 6. April 2026 um 15:41 UTCinvestigating

   We are currently investigating this issue.

2. 6. April 2026 um 16:37 UTCinvestigating

   We are continuing to investigate this issue.

3. 6. April 2026 um 17:51 UTCidentified

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

4. 6. April 2026 um 20: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. 7. April 2026 um 13:06 UTCresolved

   This incident has been resolved.

1. 2. April 2026 um 12:53 UTCidentified

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

2. 2. April 2026 um 13:56 UTCidentified

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

3. 2. April 2026 um 15:37 UTCmonitoring

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

4. 2. April 2026 um 21:07 UTCresolved

   Monitoring complete. No additional issues.

1. 26. März 2026 um 14:05 UTCidentified

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

2. 26. März 2026 um 15:00 UTCmonitoring

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

3. 26. März 2026 um 21:03 UTCresolved

   This incident has been resolved.

1. 26. März 2026 um 13: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. 26. März 2026 um 13:44 UTCidentified

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

3. 26. März 2026 um 14: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. 26. März 2026 um 15:29 UTCmonitoring

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

5. 26. März 2026 um 15:52 UTCresolved

   This incident has been resolved.

1. 11. März 2026 um 15:45 UTCinvestigating

   We are currently investigating this issue.

2. 11. März 2026 um 16:06 UTCidentified

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

3. 11. März 2026 um 16:36 UTCmonitoring

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

4. 11. März 2026 um 19:46 UTCresolved

   This incident has been resolved.

1. 9. März 2026 um 13:58 UTCinvestigating

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

2. 9. März 2026 um 15:17 UTCidentified

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

3. 9. März 2026 um 16:21 UTCidentified

   We continue to work on a fix for this issue.

4. 9. März 2026 um 16:39 UTCmonitoring

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

5. 9. März 2026 um 17:16 UTCresolved

   This incident has been resolved.

1. 7. März 2026 um 18: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. 7. März 2026 um 20: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. 8. März 2026 um 04: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. 9. März 2026 um 13:32 UTCresolved

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

1. 23. Februar 2026 um 06: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. 23. Februar 2026 um 10:37 UTCmonitoring

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

3. 23. Februar 2026 um 11:01 UTCresolved

   This incident has been resolved.

1. 3. Februar 2026 um 22: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. 4. Februar 2026 um 16: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. 1. Februar 2026 um 21: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. 3. Februar 2026 um 17: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. 3. Februar 2026 um 17:59 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 3. Februar 2026 um 20:04 UTCresolved

   This incident has been resolved.

1. 6. Januar 2026 um 17: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. 6. Januar 2026 um 18: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.