Historique des pannes de Jamf

1. 3 septembre 2026 à 22:05 UTCidentified

   Un problème a été identifié qui affecte certains clients de Jamf Pro. Nous travaillons à la résolution et fournirons la prochaine mise à jour dans 45 minutes.

2. 4 septembre 2026 à 00:17 UTCmonitoring

   Nous surveillons la situation avec le fournisseur de services en amont. Nous passerons à Resolved une fois que le fournisseur confirmera que leur incident est fermé.

3. 4 septembre 2026 à 00:22 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 17 août 2026 à 09:54 UTCinvestigating

   Jamf enquête sur un problème touchant la gestion du Plan directeur pour les clients aux États-Unis. Certains clients pourraient ne pas être en mesure de gérer les plans directeurs pour le moment. Notre équipe d'ingénieurs enquête activement et fournira des mises à jour à mesure que de plus amples informations seront disponibles. Symptômes : Les clients américains sont incapables de gérer les plans directeurs. Impact client : Services touchés : plans directeurs (système de gestion du plan directeur) Régions touchées: États-Unis

2. 17 août 2026 à 09:56 UTCinvestigating

   Nous continuons d'enquêter sur cette question.

3. 17 août 2026 à 10:19 UTCmonitoring

   Les services de gestion du plan directeur sont maintenant opérationnels, mais notre équipe d'ingénierie continue de surveiller. Aux États-Unis, les clients qui connaissent des problèmes de gestion des plans directeurs ne devraient plus voir d'impact. Nous nous excusons pour le désagrément et vous remercions de votre patience pendant que nous réglons ce problème.

4. 17 août 2026 à 11:28 UTCresolved

   Cet incident a été résolu. Les services de gestion du plan directeur pour les clients américains sont pleinement opérationnels, et aucun autre impact n'est attendu. Nous nous excusons de tout inconvénient que cela pourrait avoir causé et nous vous remercions de votre patience.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 24 juillet 2026 à 08:56 UTCidentified

   Nous sommes conscients d'un problème qui provoque la désactivation de l'application Jamf Trust sur les appareils clients. Bien que l'application soit désactivée, ses protections — y compris Zero Trust Network Access (ZTNA) et le filtrage de contenu — ne sont pas appliquées. Cela affecte les appareils sur toutes les plateformes : iOS, macOS, Android et Windows. Notre équipe d'ingénierie a identifié la cause et la réparation est déployée à la production. Une fois que le correctif est en direct, les appareils affectés devront être réactivés, ce qui peut nécessiter une action de l'utilisateur final ou de l'administrateur. Nous publierons plus de détails ici dès que la correction sera confirmée.

2. 24 juillet 2026 à 09:53 UTCmonitoring

   Une solution est maintenant en production et a empêché la propagation du problème, donc aucun dispositif supplémentaire ne sera affecté. Les appareils dont l'application Jamf Trust a déjà été désactivée peuvent ne pas être résolus automatiquement — certains peuvent se rétablir seuls, mais d'autres nécessiteront des mesures d'assainissement supplémentaires. Nous compilons un rapport des clients touchés et nous travaillons à atteindre les comptes touchés directement avec des instructions étape par étape pour réactiver leurs appareils et restaurer les protections, y compris Zero Trust Network Access (ZTNA) et le filtrage de contenu. Nous publierons également ces instructions ici afin qu'elles soient à la disposition de toutes les personnes touchées.

3. 24 juillet 2026 à 11:52 UTCmonitoring

   La fixation en production continue de se maintenir, et aucun autre dispositif n'est affecté. Nous compilons toujours la liste des clients touchés et nous préparons les instructions d'assainissement pour les appareils où l'application Jamf Trust a été désactivée.

4. 24 juillet 2026 à 16:05 UTCresolved

   La question a été réglée. L'application Jamf Trust ne sera plus désactivée de façon inattendue sur les appareils. Impact client restant : Pour les applications Jamf Trust qui avaient déjà été désactivées, elles devront être réactivées. Selon la configuration de déploiement, cela peut être automatique ou nécessiter une réactivation manuelle. Pour obtenir de l'aide pour réactiver les appareils, veuillez vous connecter au portail du compte Jamf et créer un ticket (Contact Support) se référant à l'application Jamf Trust désactivation. Alors que l'application Jamf Trust est désactivée, ses protections, y compris Zero Trust Network Access (ZTNA) et le filtrage de contenu, ne sont pas appliquées. Cela affecte les appareils sur toutes les plateformes : iOS, macOS, Android et Windows. Nous nous excusons pour tout désagrément.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 23 juin 2026 à 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 juin 2026 à 18:38 UTCidentified

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

3. 23 juin 2026 à 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 juin 2026 à 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 juin 2026 à 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 juin 2026 à 11:54 UTCmonitoring

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

3. 22 juin 2026 à 12:01 UTCresolved

   This incident has been resolved.

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

   We are continuing to investigate this issue.

3. 15 juin 2026 à 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 juin 2026 à 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 juin 2026 à 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 juin 2026 à 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 à 10:13 UTCinvestigating

   We are currently investigating this issue.

2. 18 mai 2026 à 10:53 UTCidentified

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

3. 18 mai 2026 à 14:45 UTCmonitoring

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

4. 18 mai 2026 à 17:50 UTCresolved

   This issue has been resolved.

1. 14 mai 2026 à 14:54 UTCinvestigating

   We are currently investigating this issue.

2. 14 mai 2026 à 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 à 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 à 01:01 UTCmonitoring

   Normal operations has resumed. Monitoring will continue.

5. 15 mai 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 15:41 UTCinvestigating

   We are currently investigating this issue.

2. 6 avril 2026 à 16:37 UTCinvestigating

   We are continuing to investigate this issue.

3. 6 avril 2026 à 17:51 UTCidentified

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

4. 6 avril 2026 à 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 avril 2026 à 13:06 UTCresolved

   This incident has been resolved.

1. 2 avril 2026 à 12:53 UTCidentified

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

2. 2 avril 2026 à 13:56 UTCidentified

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

3. 2 avril 2026 à 15:37 UTCmonitoring

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

4. 2 avril 2026 à 21:07 UTCresolved

   Monitoring complete. No additional issues.

1. 26 mars 2026 à 14:05 UTCidentified

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

2. 26 mars 2026 à 15:00 UTCmonitoring

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

3. 26 mars 2026 à 21:03 UTCresolved

   This incident has been resolved.

1. 26 mars 2026 à 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 mars 2026 à 13:44 UTCidentified

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

3. 26 mars 2026 à 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 mars 2026 à 15:29 UTCmonitoring

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

5. 26 mars 2026 à 15:52 UTCresolved

   This incident has been resolved.

1. 11 mars 2026 à 15:45 UTCinvestigating

   We are currently investigating this issue.

2. 11 mars 2026 à 16:06 UTCidentified

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

3. 11 mars 2026 à 16:36 UTCmonitoring

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

4. 11 mars 2026 à 19:46 UTCresolved

   This incident has been resolved.

1. 9 mars 2026 à 13:58 UTCinvestigating

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

2. 9 mars 2026 à 15:17 UTCidentified

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

3. 9 mars 2026 à 16:21 UTCidentified

   We continue to work on a fix for this issue.

4. 9 mars 2026 à 16:39 UTCmonitoring

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

5. 9 mars 2026 à 17:16 UTCresolved

   This incident has been resolved.

1. 7 mars 2026 à 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 mars 2026 à 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 mars 2026 à 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 mars 2026 à 13:32 UTCresolved

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

1. 23 février 2026 à 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 février 2026 à 10:37 UTCmonitoring

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

3. 23 février 2026 à 11:01 UTCresolved

   This incident has been resolved.

1. 3 février 2026 à 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 février 2026 à 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 février 2026 à 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 février 2026 à 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 février 2026 à 17:59 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 3 février 2026 à 20:04 UTCresolved

   This incident has been resolved.

1. 6 janvier 2026 à 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 janvier 2026 à 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.