Historial de interrupciones de Jamf

1. 3 de septiembre de 2026 a las 22:05 UTCidentified

   Se ha identificado un problema que está afectando a algunos clientes de Jamf Pro. Trabajamos para resolver y proporcionaremos la siguiente actualización en 45 minutos.

2. 4 de septiembre de 2026 a las 0:17 UTCmonitoring

   Estamos monitoreando la situación con el proveedor de servicios de emergencia. Nos moveremos a Resolver una vez que el proveedor confirme que su incidente está cerrado.

3. 4 de septiembre de 2026 a las 0:22 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 17 de agosto de 2026 a las 9:54 UTCinvestigating

   Jamf está investigando un problema que afecta a la gestión de Blueprint para clientes en los Estados Unidos. Algunos clientes pueden ser incapaces de gestionar Blueprints en este momento. Nuestro equipo de ingeniería está investigando activamente y proporcionará actualizaciones a medida que se disponga de más información. Síntomas: los clientes estadounidenses están experimentando una total incapacidad para gestionar Blueprints. Impacto del cliente: Servicios Afectados: Blueprints (Sistema de Gestión de Piezas) Regiones afectadas: Estados Unidos

2. 17 de agosto de 2026 a las 9:56 UTCinvestigating

   Seguimos investigando esta cuestión.

3. 17 de agosto de 2026 a las 10:19 UTCmonitoring

   Los servicios de gestión de planos están en funcionamiento pero nuestro equipo de ingeniería sigue vigilando. Los clientes de EE.UU. que experimentaron problemas manejando Blueprints ya no deberían ver ningún impacto. Nos disculpamos por la molestia y le agradecemos su paciencia mientras resolvimos este tema.

4. 17 de agosto de 2026 a las 11:28 UTCresolved

   Este incidente ha sido resuelto. Los servicios de gestión de planos para los clientes estadounidenses están plenamente operativos, y no se espera ningún nuevo impacto. Nos disculpamos por cualquier inconveniente que esto pueda haber causado y gracias por su paciencia.

Traducido automáticamente desde la actualización oficial del incidente.

1. 24 de julio de 2026 a las 8:56 UTCidentified

   Somos conscientes de un problema que hace que la aplicación Jamf Trust sea desactivada en dispositivos de clientes. Aunque la aplicación está desactivada, sus protecciones —incluyendo Zero Trust Network Access (ZTNA) y el filtro de contenido— no se aplican. Esto afecta a los dispositivos en todas las plataformas: iOS, macOS, Android y Windows. Nuestro equipo de ingeniería ha identificado la causa y la solución está siendo implementada a la producción. Una vez que la solución esté en vivo, los dispositivos afectados tendrán que ser reactivados, lo que puede requerir la acción de usuario final o administrador. Publicaremos más detalles aquí tan pronto como se confirme la solución.

2. 24 de julio de 2026 a las 9:53 UTCmonitoring

   Una solución está ahora en producción y ha impedido que el problema se difunda, por lo que ningún dispositivo adicional será afectado. Los dispositivos en los que la aplicación Jamf Trust ya estaba desactivada no pueden resolverse automáticamente; algunos pueden recuperarse por su cuenta, pero otros requerirán pasos adicionales de remediación. Estamos recopilando un informe de clientes afectados y estamos trabajando para llegar directamente a cuentas afectadas con instrucciones paso a paso para reactivar sus dispositivos y restaurar protecciones, incluyendo Zero Trust Network Access (ZTNA) y el filtrado de contenidos. También publicaremos estas instrucciones aquí para que estén disponibles para todos los afectados.

3. 24 de julio de 2026 a las 11:52 UTCmonitoring

   La fijación en la producción sigue manteniendo, y no se están afectando dispositivos adicionales. Aún estamos recopilando la lista de clientes afectados y preparando las instrucciones de remediación para dispositivos donde la aplicación Jamf Trust fue desactivada.

4. 24 de julio de 2026 a las 16:05 UTCresolved

   La cuestión se ha resuelto. La aplicación Jamf Trust ya no será desactivada inesperadamente en dispositivos. Permanecer el impacto del cliente: Para las aplicaciones de Jamf Trust que habían sido desactivadas anteriormente, tendrán que ser reactivadas. Dependiendo de la configuración de implementación esto puede ser automático o requerir reactivación manual. Para asistencia con dispositivos de reactivación, por favor inicie sesión en el portal Jamf Account y cree un ticket (Apoyo de Contacto) que hace referencia a la desactivación de la aplicación Jamf Trust. Aunque la aplicación Jamf Trust está desactivada, sus protecciones —incluyendo Zero Trust Network Access (ZTNA) y el filtrado de contenidos— no se aplican. Esto afecta a los dispositivos en todas las plataformas: iOS, macOS, Android y Windows. Nos disculpamos por cualquier inconveniente.

Traducido automáticamente desde la actualización oficial del incidente.

1. 23 de junio de 2026 a las 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 de junio de 2026 a las 18:38 UTCidentified

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

3. 23 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 11:54 UTCmonitoring

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

3. 22 de junio de 2026 a las 12:01 UTCresolved

   This incident has been resolved.

1. 15 de junio de 2026 a las 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 de junio de 2026 a las 13:33 UTCinvestigating

   We are continuing to investigate this issue.

3. 15 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de mayo de 2026 a las 10:13 UTCinvestigating

   We are currently investigating this issue.

2. 18 de mayo de 2026 a las 10:53 UTCidentified

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

3. 18 de mayo de 2026 a las 14:45 UTCmonitoring

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

4. 18 de mayo de 2026 a las 17:50 UTCresolved

   This issue has been resolved.

1. 14 de mayo de 2026 a las 14:54 UTCinvestigating

   We are currently investigating this issue.

2. 14 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 1:01 UTCmonitoring

   Normal operations has resumed. Monitoring will continue.

5. 15 de mayo de 2026 a las 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. 21 de abril de 2026 a las 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. 21 de abril de 2026 a las 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. 21 de abril de 2026 a las 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. 21 de abril de 2026 a las 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. 6 de abril de 2026 a las 15:41 UTCinvestigating

   We are currently investigating this issue.

2. 6 de abril de 2026 a las 16:37 UTCinvestigating

   We are continuing to investigate this issue.

3. 6 de abril de 2026 a las 17:51 UTCidentified

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

4. 6 de abril de 2026 a las 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 de abril de 2026 a las 13:06 UTCresolved

   This incident has been resolved.

1. 2 de abril de 2026 a las 12:53 UTCidentified

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

2. 2 de abril de 2026 a las 13:56 UTCidentified

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

3. 2 de abril de 2026 a las 15:37 UTCmonitoring

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

4. 2 de abril de 2026 a las 21:07 UTCresolved

   Monitoring complete. No additional issues.

1. 26 de marzo de 2026 a las 14:05 UTCidentified

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

2. 26 de marzo de 2026 a las 15:00 UTCmonitoring

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

3. 26 de marzo de 2026 a las 21:03 UTCresolved

   This incident has been resolved.

1. 26 de marzo de 2026 a las 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 de marzo de 2026 a las 13:44 UTCidentified

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

3. 26 de marzo de 2026 a las 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 de marzo de 2026 a las 15:29 UTCmonitoring

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

5. 26 de marzo de 2026 a las 15:52 UTCresolved

   This incident has been resolved.

1. 11 de marzo de 2026 a las 15:45 UTCinvestigating

   We are currently investigating this issue.

2. 11 de marzo de 2026 a las 16:06 UTCidentified

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

3. 11 de marzo de 2026 a las 16:36 UTCmonitoring

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

4. 11 de marzo de 2026 a las 19:46 UTCresolved

   This incident has been resolved.

1. 9 de marzo de 2026 a las 13:58 UTCinvestigating

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

2. 9 de marzo de 2026 a las 15:17 UTCidentified

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

3. 9 de marzo de 2026 a las 16:21 UTCidentified

   We continue to work on a fix for this issue.

4. 9 de marzo de 2026 a las 16:39 UTCmonitoring

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

5. 9 de marzo de 2026 a las 17:16 UTCresolved

   This incident has been resolved.

1. 7 de marzo de 2026 a las 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 de marzo de 2026 a las 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 de marzo de 2026 a las 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. 9 de marzo de 2026 a las 13:32 UTCresolved

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

1. 23 de febrero de 2026 a las 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. 23 de febrero de 2026 a las 10:37 UTCmonitoring

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

3. 23 de febrero de 2026 a las 11:01 UTCresolved

   This incident has been resolved.

1. 3 de febrero de 2026 a las 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 de febrero de 2026 a las 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 de febrero de 2026 a las 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 de febrero de 2026 a las 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 de febrero de 2026 a las 17:59 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 3 de febrero de 2026 a las 20:04 UTCresolved

   This incident has been resolved.

1. 6 de enero de 2026 a las 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 de enero de 2026 a las 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.