Cronologia delle interruzioni di Jamf

1. 3 settembre 2026 alle ore 22:05 UTCidentified

   È stato identificato un problema che riguarda alcuni clienti Jamf Pro. Stiamo lavorando per risolvere e forniremo il prossimo aggiornamento in 45 minuti.

2. 4 settembre 2026 alle ore 00:17 UTCmonitoring

   Stiamo monitorando la situazione con il fornitore di servizi a monte. Ci trasferiremo a Risolto una volta che il fornitore conferma il loro incidente è chiuso.

3. 4 settembre 2026 alle ore 00:22 UTCresolved

   Questo incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 17 agosto 2026 alle ore 09:54 UTCinvestigating

   Jamf sta indagando su un problema che riguarda la gestione Blueprint per i clienti negli Stati Uniti. Alcuni clienti potrebbero non essere in grado di gestire Blueprint in questo momento. Il nostro team di ingegneria sta attivamente indagando e fornirà aggiornamenti come ulteriori informazioni diventano disponibili. Sintomi: i clienti americani stanno vivendo una completa incapacità di gestire Blueprints. Impatto del cliente: Servizi interessati: Blueprints (Blueprint Management System) Regioni interessate: Stati Uniti

2. 17 agosto 2026 alle ore 09:56 UTCinvestigating

   Stiamo continuando a indagare su questo problema.

3. 17 agosto 2026 alle ore 10:19 UTCmonitoring

   I servizi di gestione delle impronte sono ora operativi, ma il nostro team di ingegneria è ancora in monitoraggio. I clienti negli Stati Uniti che hanno sperimentato problemi di gestione Blueprints non dovrebbero più vedere alcun impatto. Ci scusiamo per l'inconveniente e vi ringraziamo per la vostra pazienza mentre abbiamo risolto questo problema.

4. 17 agosto 2026 alle ore 11:28 UTCresolved

   Questo incidente è stato risolto. I servizi di gestione delle stampe per i clienti statunitensi sono pienamente operativi e non è previsto alcun ulteriore impatto. Ci scusiamo per qualsiasi inconveniente che questo potrebbe aver causato e grazie per la vostra pazienza.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 24 luglio 2026 alle ore 08:56 UTCidentified

   Siamo consapevoli di un problema che causa la disattivazione dell'app Jamf Trust sui dispositivi dei clienti. Mentre l'applicazione è disattivata, le sue protezioni — tra cui Zero Trust Network Access (ZTNA) e il filtraggio dei contenuti — non sono applicate. Questo colpisce i dispositivi su tutte le piattaforme: iOS, macOS, Android e Windows. Il nostro team di ingegneri ha identificato la causa e la correzione è in fase di distribuzione alla produzione. Una volta che la correzione è live, i dispositivi interessati dovranno essere riattivati, che possono richiedere l'azione dell'utente finale o dell'amministratore. Posteremo ulteriori dettagli qui non appena la correzione è confermata.

2. 24 luglio 2026 alle ore 09:53 UTCmonitoring

   Una correzione è ora in produzione e ha fermato il problema dalla diffusione, quindi nessun dispositivo aggiuntivo sarà interessato. I dispositivi in cui l'applicazione Jamf Trust era già disattivata non possono essere risolti automaticamente — alcuni possono recuperare da soli, ma altri richiederanno ulteriori passaggi di bonifica. Stiamo compilando un rapporto di clienti colpiti e stiamo lavorando per raggiungere i conti colpiti direttamente con le istruzioni passo-passo per riattivare i loro dispositivi e ripristinare le protezioni, tra cui Zero Trust Network Access (ZTNA) e il filtraggio dei contenuti. Verremo anche pubblicare queste istruzioni qui in modo che siano disponibili per tutti gli interessati.

3. 24 luglio 2026 alle ore 11:52 UTCmonitoring

   La fissazione della produzione continua a contenere, e nessun dispositivo aggiuntivo viene interessato. Stiamo ancora compilando l'elenco dei clienti colpiti e preparando le istruzioni di bonifica per i dispositivi in cui l'applicazione Jamf Trust è stata disattivata.

4. 24 luglio 2026 alle ore 16:05 UTCresolved

   Il problema è stato risolto. L'applicazione Jamf Trust non sarà più inaspettatamente disattivata sui dispositivi. Remaining Customer Impact: Per le app Jamf Trust che erano state precedentemente disattivate, dovranno essere riattivate. A seconda della configurazione di distribuzione questo può essere automatico o richiedere la riattivazione manuale. Per assistenza con dispositivi di riattivazione, si prega di accedere al portale Jamf Account e creare un biglietto (Contact Support) che riferisce la disattivazione dell'app Jamf Trust. Mentre l'applicazione Jamf Trust è disattivata, le sue protezioni - tra cui Zero Trust Network Access (ZTNA) e il filtraggio dei contenuti - non sono applicate. Questo colpisce i dispositivi su tutte le piattaforme: iOS, macOS, Android e Windows. Ci scusiamo per qualsiasi inconveniente.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 23 giugno 2026 alle ore 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 giugno 2026 alle ore 18:38 UTCidentified

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

3. 23 giugno 2026 alle ore 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 giugno 2026 alle ore 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 giugno 2026 alle ore 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 giugno 2026 alle ore 11:54 UTCmonitoring

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

3. 22 giugno 2026 alle ore 12:01 UTCresolved

   This incident has been resolved.

1. 15 giugno 2026 alle ore 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 giugno 2026 alle ore 13:33 UTCinvestigating

   We are continuing to investigate this issue.

3. 15 giugno 2026 alle ore 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 giugno 2026 alle ore 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 giugno 2026 alle ore 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 giugno 2026 alle ore 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 maggio 2026 alle ore 10:13 UTCinvestigating

   We are currently investigating this issue.

2. 18 maggio 2026 alle ore 10:53 UTCidentified

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

3. 18 maggio 2026 alle ore 14:45 UTCmonitoring

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

4. 18 maggio 2026 alle ore 17:50 UTCresolved

   This issue has been resolved.

1. 14 maggio 2026 alle ore 14:54 UTCinvestigating

   We are currently investigating this issue.

2. 14 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 01:01 UTCmonitoring

   Normal operations has resumed. Monitoring will continue.

5. 15 maggio 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 15:41 UTCinvestigating

   We are currently investigating this issue.

2. 6 aprile 2026 alle ore 16:37 UTCinvestigating

   We are continuing to investigate this issue.

3. 6 aprile 2026 alle ore 17:51 UTCidentified

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

4. 6 aprile 2026 alle ore 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 aprile 2026 alle ore 13:06 UTCresolved

   This incident has been resolved.

1. 2 aprile 2026 alle ore 12:53 UTCidentified

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

2. 2 aprile 2026 alle ore 13:56 UTCidentified

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

3. 2 aprile 2026 alle ore 15:37 UTCmonitoring

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

4. 2 aprile 2026 alle ore 21:07 UTCresolved

   Monitoring complete. No additional issues.

1. 26 marzo 2026 alle ore 14:05 UTCidentified

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

2. 26 marzo 2026 alle ore 15:00 UTCmonitoring

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

3. 26 marzo 2026 alle ore 21:03 UTCresolved

   This incident has been resolved.

1. 26 marzo 2026 alle ore 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 marzo 2026 alle ore 13:44 UTCidentified

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

3. 26 marzo 2026 alle ore 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 marzo 2026 alle ore 15:29 UTCmonitoring

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

5. 26 marzo 2026 alle ore 15:52 UTCresolved

   This incident has been resolved.

1. 11 marzo 2026 alle ore 15:45 UTCinvestigating

   We are currently investigating this issue.

2. 11 marzo 2026 alle ore 16:06 UTCidentified

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

3. 11 marzo 2026 alle ore 16:36 UTCmonitoring

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

4. 11 marzo 2026 alle ore 19:46 UTCresolved

   This incident has been resolved.

1. 9 marzo 2026 alle ore 13:58 UTCinvestigating

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

2. 9 marzo 2026 alle ore 15:17 UTCidentified

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

3. 9 marzo 2026 alle ore 16:21 UTCidentified

   We continue to work on a fix for this issue.

4. 9 marzo 2026 alle ore 16:39 UTCmonitoring

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

5. 9 marzo 2026 alle ore 17:16 UTCresolved

   This incident has been resolved.

1. 7 marzo 2026 alle ore 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 marzo 2026 alle ore 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 marzo 2026 alle ore 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 marzo 2026 alle ore 13:32 UTCresolved

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

1. 23 febbraio 2026 alle ore 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 febbraio 2026 alle ore 10:37 UTCmonitoring

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

3. 23 febbraio 2026 alle ore 11:01 UTCresolved

   This incident has been resolved.

1. 3 febbraio 2026 alle ore 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 febbraio 2026 alle ore 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 febbraio 2026 alle ore 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 febbraio 2026 alle ore 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 febbraio 2026 alle ore 17:59 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 3 febbraio 2026 alle ore 20:04 UTCresolved

   This incident has been resolved.

1. 6 gennaio 2026 alle ore 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 gennaio 2026 alle ore 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.