Is Jamf Down Right Now? Check if there is a current outage ongoing.

We are performing upgrades on Jamf Cloud beginning on May 31st 0700 UTC and running through May 31st at 1800 UTC. More information will be available on Jamf Nation here:https://learn.jamf.com/en-US/bundle/jamf-pro-release-notes-current/page/New_Features_and_Enhancements.htmlhttps://community.jamf.com/t5/release-info/jamf-pro-11-17-now-available/ta-p/352860

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We are performing upgrades on Jamf Cloud beginning on May 31st 0400 UTC and running through May 31st at 1400 UTC. More information will be available on Jamf Nation here:https://learn.jamf.com/en-US/bundle/jamf-pro-release-notes-current/page/New_Features_and_Enhancements.htmlhttps://community.jamf.com/t5/release-info/jamf-pro-11-17-now-available/ta-p/352860

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We are performing upgrades on Jamf Cloud beginning on May 30th 2300 UTC and running through May 31st at 0600 UTC. More information will be available on Jamf Nation here:https://learn.jamf.com/en-US/bundle/jamf-pro-release-notes-current/page/New_Features_and_Enhancements.htmlhttps://community.jamf.com/t5/release-info/jamf-pro-11-17-now-available/ta-p/352860

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We are performing upgrades on Jamf Cloud beginning on May 30th at 2200 UTC and running through May 31st at 0900 UTC. More information will be available on Jamf Nation here:https://learn.jamf.com/en-US/bundle/jamf-pro-release-notes-current/page/New_Features_and_Enhancements.htmlhttps://community.jamf.com/t5/release-info/jamf-pro-11-17-now-available/ta-p/352860

We are performing upgrades on Jamf Cloud beginning on May 30th 1500 UTC and running through May 30th at 2300 UTC. More information will be available on Jamf Nation here:https://learn.jamf.com/en-US/bundle/jamf-pro-release-notes-current/page/New_Features_and_Enhancements.htmlhttps://community.jamf.com/t5/release-info/jamf-pro-11-17-now-available/ta-p/352860

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We are performing upgrades on Jamf Cloud beginning on May 30th 1400 UTC and running through May 30th at 2000 UTC. More information will be available on Jamf Nation here:https://learn.jamf.com/en-US/bundle/jamf-pro-release-notes-current/page/New_Features_and_Enhancements.htmlhttps://community.jamf.com/t5/release-info/jamf-pro-11-17-now-available/ta-p/352860

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We are performing upgrades on Jamf Cloud beginning on May 17th 0700 UTC and running through May 17th at 1800 UTC. More information will be available on Jamf Nation here:https://learn.jamf.com/en-US/bundle/jamf-pro-release-notes-current/page/New_Features_and_Enhancements.htmlhttps://community.jamf.com/t5/release-info/jamf-pro-11-16-now-available/ta-p/351195

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We are performing upgrades on Jamf Cloud beginning on May 17th 0400 UTC and running through May 17th at 1400 UTC. More information will be available on Jamf Nation here:https://learn.jamf.com/en-US/bundle/jamf-pro-release-notes-current/page/New_Features_and_Enhancements.htmlhttps://community.jamf.com/t5/release-info/jamf-pro-11-16-now-available/ta-p/351195

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We are performing upgrades on Jamf Cloud beginning on May 16th 2300 UTC and running through May 17th at 0600 UTC. More information will be available on Jamf Nation here:https://learn.jamf.com/en-US/bundle/jamf-pro-release-notes-current/page/New_Features_and_Enhancements.htmlhttps://community.jamf.com/t5/release-info/jamf-pro-11-16-now-available/ta-p/351195

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We are performing upgrades on Jamf Cloud beginning on May 16th at 2200 UTC and running through May 17th at 0900 UTC. More information will be available on Jamf Nation here:https://learn.jamf.com/en-US/bundle/jamf-pro-release-notes-current/page/New_Features_and_Enhancements.htmlhttps://community.jamf.com/t5/release-info/jamf-pro-11-16-now-available/ta-p/351195

We are performing upgrades on Jamf Cloud beginning on May 16th 1500 UTC and running through May 16th at 2300 UTC. More information will be available on Jamf Nation here:https://learn.jamf.com/en-US/bundle/jamf-pro-release-notes-current/page/New_Features_and_Enhancements.htmlhttps://community.jamf.com/t5/release-info/jamf-pro-11-16-now-available/ta-p/351195

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We are performing upgrades on Jamf Cloud beginning on May 16th 1400 UTC and running through May 16th at 2000 UTC. More information will be available on Jamf Nation here:https://learn.jamf.com/en-US/bundle/jamf-pro-release-notes-current/page/New_Features_and_Enhancements.htmlhttps://community.jamf.com/t5/release-info/jamf-pro-11-16-now-available/ta-p/351195

Scheduled maintenance is currently in progress. We will provide updates as necessary.

**Root Cause Analysis of Jamf Pro Outage** During scheduled maintenance on a low-level component of the Jamf Pro cloud infrastructure, an update failed, resulting in an outage that affected Jamf Pro customers. The component in question is a critical part of our auto-scaling infrastructure, which enables Jamf to support millions of devices. The failure of this upgrade led to a widespread outage. * The update was not backwards-compatible, making it impossible to roll back to the previous version. * We were able to quickly restore services for some configurations, including Premium Cloud customers. * Larger clusters could not be recovered through the standard workflow and required manual intervention. We had to downsize these clusters to enable recovery. * For customers with custom domains, an additional step was needed before service could be fully restored.

At this time, we have resolved all instances in all classes. We appreciate your patience and apologize for the inconvenience they may have caused.

UPDATE: A subset of Standard Production instances with a custom URL require a restart of the service, which will cause a logout situation. This impacts all regions. We appreciate your patience and apologize for the inconvenience this has caused, we will provide an update in the next hour.

UPDATE: We have resolved all Production instances in all regions at this time. We still have some ongoing restarts in our non-production environments, including sandbox, trial, and betas. At this time, we will monitor the situation closely for the next hour before resolving the incident to ensure all systems are functional. Again, we apologize and greatly appreciate your patience during the incident.

UPDATE: We continue working through a smaller subset of our standard instances with a custom URL in each identified EU and US regions. Please check the status bar for your specific region for more information. We appreciate your patience. We will continue to provide updates in the next hour. *We have also restarted our sandbox, trial, and beta classes in all regions. No outage expected, just a logout and log back in.

UPDATE: A small subset of our standard instances in each of the identified regions in the EU and US are still impacted. Those with a custom URL service will, unfortunately, continue to be intermittent as we work through them as quickly as possible. Please check the status bar for your specific region for more information. We appreciate your patience and apologize for the inconvenience this has caused. We will provide an update in the next hour.

All Premium and APAC instances have been resolved. EU & US standard instances have been largely restored, for those with a custom URL service will unfortunately continue to be intermittent. Please check the status bar for your specific region for more information. We appreciate your patience and apologise for the inconvenience this has caused.

All Premium and APAC instances have been resolved. US and EU Standard instances are currently in progress, and some clusters have been resolved within those regions. Please check the status bar for your specific region for more information. We appreciate your patience and apologize for the inconvenience this has caused.

All Premium and APAC instances have been resolved. US and EU Standard instances are currently in progress, and some clusters have been resolved within those regions. Please check the status bar for your specific region for more information. We appreciate your patience and apologize for the inconvenience this has caused.

We are still in the process of implementing a fix and distributing it across all customer instances. While some instances have been successfully restored and are functioning as expected, the overall resolution is still in progress. We apologize for any inconvenience this may have caused.

We are still in the process of implementing a fix and distributing it across all customer instances. While some instances have been successfully restored and are functioning as expected, the overall resolution is still in progress. We apologize for any inconvenience this may have caused.

We are still in the process of implementing a fix and distributing it across all customer instances. While some instances have been successfully restored and are functioning as expected, the overall resolution is still in progress. We apologize for any inconvenience this may have caused.

An infrastructure issue has been identified and a fix is in process of being implemented and distributed to all customers. At this time we do not have an estimated time of resolution, however all teams have been engaged to address the issue. We apologize for and inconveniences this has caused.

We are continuing to roll out the fix across all standard instances. Our teams are actively monitoring progress to ensure full restoration as quickly and smoothly as possible. We appreciate your patience and understanding as we work to bring all services back to expected performance levels.

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

We are continuing to roll out the fix across all standard instances. Our teams are actively monitoring progress to ensure full restoration as quickly and smoothly as possible. We appreciate your patience and understanding as we work to bring all services back to expected performance levels.

We are continuing to roll out the fix across all standard instances. Our teams are actively monitoring progress to ensure full restoration as quickly and smoothly as possible. We appreciate your patience and understanding as we work to bring all services back to expected performance levels.

We are continuing to roll out the fix across all standard instances. Our teams are actively monitoring progress to ensure full restoration as quickly and smoothly as possible. We appreciate your patience and understanding as we work to bring all services back to expected performance levels.

All premium instances have been successfully updated. We are currently in the process of distributing the update to all standard instances. While some instances are now operational, the overall resolution is taking longer than initially expected. We apologize for any inconvenience this may have caused.

We are continuing to roll out the fix across all instances. Our teams are actively monitoring progress to ensure full restoration as quickly and smoothly as possible. We appreciate your patience and understanding as we work to bring all services back to expected performance levels.

We are still in the process of implementing a fix and distributing it across all customer instances. While some instances have been successfully restored and are functioning as expected, the overall resolution is still in progress. We apologize for any inconvenience this may have caused.

We are still in the process of implementing a fix and distributing it to all customer instances. Some instances are back and functioning, however the resolution is taking longer than anticipated. We are exploring any and all means to ensure all instances are brought up as soon as possible. We apologize for the inconvenience this may have caused.

An infrastructure issue has been identified and a fix is in process of being implemented and distributed to all customers. At this time we do not have an estimated time of resolution, however all teams have been engaged to address the issue. We apologize for and inconveniences this has caused.

An infrastructure issue has been identified and a fix is being worked on currently. At this time we do not have an estimated time of resolution, however all teams have been engaged to address the issue. We apologize for and inconveniences this has caused.

An infrastructure issue has been identified and a fix is being worked on currently. At this time we do not have an estimated time of resolution, however all teams have been engaged to address the issue. We apologize for and inconveniences this has caused.

An issue has been identified that is affecting some Jamf Pro customers. We are working to resolve and will provide next update in 45 minutes.

An infrastructure issue has been identified and a fix is in process of being implemented and distributed to all customers.At this time we do not have an estimated time of resolution, however all teams have been engaged to address the issue. We apologize for and inconveniences this has caused.

An infrastructure issue has been identified and a fix is being worked on currently. At this time we do not have an estimated time of resolution, however all teams have been engaged to address the issue. We apologize for and inconveniences this has caused.

An infrastructure issue has been identified and a fix is being worked on currently. At this time we do not have an estimated time of resolution, however all teams have been engaged to address the issue. We apologize for and inconveniences this has caused.

An issue has been identified that is affecting some Jamf Pro customers. We are working to resolve and will provide next update in 45 minutes.

This impacted the Jamf Security Cloud administration interface to not be available, the application of Jamf Security policies to not be functional, and the device status update processing was slowed down / paused. We have resolved this and Jamf Security Cloud is working as expected.

This impacted the Jamf Security Cloud administration interface to not be available, the application of Jamf Security policies to not be functional, and the device status update processing was slowed down / paused.We have resolved this and Jamf Security Cloud is working as expected.

This incident has been resolved.

An issue has been identified that is affecting some Jamf Pro customers. We are working to resolve and will provide next update in 45 minutes.

All systems are operational now.

The content filtering policy issues have been resolved, and all systems function normally. We are actively monitoring the service. There might still be some temporary impact regarding data capping as our systems process the backlog of events. These discrepancies will resolve automatically within the next few hours.

The issue causing degraded performance has been identified, and technical teams are working on implementing the fix. We will publish the next update in an hour.

Our technical teams are actively investigating the root cause and working to resolve these content filtering policy issues. We will provide another update as soon as more information becomes available.

Since 1:00 AM UTC, we have been experiencing issues with content filtering policies in Jamf Security Cloud. This may affect: - iOS on-device content filtering - Windows content filtering - Content filtering policy pages in the Jamf Security Cloud console We are investigating the issue.

This incident has been resolved.

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

An issue has been identified that is affecting some Jamf Pro customers. We are working to resolve and will provide next update in 45 minutes.

Since 1:00 AM UTC, we have been experiencing issues with content filtering policies in Jamf Security Cloud. This may affect:- iOS device content filtering- Windows content filtering- Content filtering policy pages in the Jamf Security Cloud consoleWe are investigating the issue.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We are performing upgrades on Jamf Cloud beginning on March 29th 0700 UTC and running through March 29th at 1800 UTC. More information will be available on Jamf Nation here:https://learn.jamf.com/en-US/bundle/jamf-pro-release-notes-current/page/New_Features_and_Enhancements.htmlhttps://community.jamf.com/t5/release-info/jamf-pro-11-15-now-available/ta-p/348530

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We are performing upgrades on Jamf Cloud beginning on March 29th 0400 UTC and running through March 29th at 1400 UTC. More information will be available on Jamf Nation here:https://learn.jamf.com/en-US/bundle/jamf-pro-release-notes-current/page/New_Features_and_Enhancements.htmlhttps://community.jamf.com/t5/release-info/jamf-pro-11-15-now-available/ta-p/348530

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We are performing upgrades on Jamf Cloud beginning on March 28th at 2300 UTC and running through March 29th at 1000 UTC. More information will be available on Jamf Nation here:https://learn.jamf.com/en-US/bundle/jamf-pro-release-notes-current/page/New_Features_and_Enhancements.htmlhttps://community.jamf.com/t5/release-info/jamf-pro-11-15-now-available/ta-p/348530

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We are performing upgrades on Jamf Cloud beginning on March 29th 0000 UTC and running through March 29th at 0700 UTC. More information will be available on Jamf Nation here:https://learn.jamf.com/en-US/bundle/jamf-pro-release-notes-current/page/New_Features_and_Enhancements.htmlhttps://community.jamf.com/t5/release-info/jamf-pro-11-15-now-available/ta-p/348530

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We are performing upgrades on Jamf Cloud beginning on March 28th 1500 UTC and running through March 28th at 2300 UTC. More information will be available on Jamf Nation here:https://learn.jamf.com/en-US/bundle/jamf-pro-release-notes-current/page/New_Features_and_Enhancements.htmlhttps://community.jamf.com/t5/release-info/jamf-pro-11-15-now-available/ta-p/348530

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We are performing upgrades on Jamf Cloud beginning on March 28th 1300 UTC and running through March 28th at 1900 UTC. More information will be available on Jamf Nation here:https://learn.jamf.com/en-US/bundle/jamf-pro-release-notes-current/page/New_Features_and_Enhancements.htmlhttps://community.jamf.com/t5/release-info/jamf-pro-11-15-now-available/ta-p/348530

This incident has been resolved.

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

This incident has been resolved.

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

The incident has been resolved

Jamf Account is currently inaccessible. We are investigating the issue.

The incident has been resolved

Jamf Account is currently inaccessible. We are investigating the issue.

This incident has been resolved.

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

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved.

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

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved.

An issue has been identified that is affecting some Jamf Pro customers. We are working to resolve and will provide next update in 45 minutes.

This incident has been resolved.

An issue has been identified that is affecting some Jamf Pro customers. We are working to resolve and will provide next update in 45 minutes.

The incident has been resolved.

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

There is an issue logging into Jamf Account. The issue has been identified and a fix being implemented.

The incident has been resolved.

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

This incident has been resolved.

Resolved incident

We are continuing to investigate this issue.

We are currently investigating the issue.

This incident has been resolved.

We are currently investigating this issue. Anyone with an active session in RADAR should stay connected but new logins are down.

Issue is now resolved

Fix has been deployed, for immediate resolution you can either : - Open the Jamf Trust app and pull down from the top to trigger a Status Update - Switch interfaces i.e. from Cellular to Wi-Fi and back The root cause has been identified and measures have taken place to prevent it from reoccurring

We are currently investigated an issue where devices are being treated as Roaming whilst in the Domestic zone. This is prevents the device from using Cellular data and sends out email alerts to the Admin and User.

This incident has been resolved.

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

We are currently investigating this issue.

This incident has been resolved.

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

We are currently investigating this issue.

This incident has been resolved.

Security and data policies defined in Jamf Security Cloud may not be enacted on devices immediately. This relates only to devices using on-device content filtering. The problem affects Jamf Security Cloud services customers using the European data center.

Security and data policies defined in Jamf Security Cloud may not be enacted on devices immediately. This relates to policies such as content filtering, data usage and capping, threat prevention and intelligence. This is affecting Jamf Security Cloud services customers using the European data center.

This incident had been resolved. All regions are functioning as normal.

S3 data forwarding in us-east-1 is returning to normal. Some customers may still see delays in S3 message delivery, but we anticipate a return to normal latency within the next 24 hours.

All regions are back to normal service with the exception S3 forwarding in us-east-1. This S3 queue still has a backlog. We are working on accelerating the clearing of this backlog.

All regions are back to normal service with the exception of us-east-1. Data from us-east-1 is being sent again, but there remains a backlog of data from the incident. We are working on accelerating the clearing of the backlog.

There is an issue with data forwarding to third party services from the macOS Security Portal with Jamf Protect. Data forwarding continues to be paused temporarily as we implement a fix. Data forwarding from Jamf Security Cloud is unaffected.

There is an issue with data forwarding to third party services from the macOS Security Portal with Jamf Protect. Data forwarding has been paused temporarily as we investigate a fix. Data forwarding from Jamf Security Cloud is unaffected.

Incident is now resolved - fix was rolled out. We are still performing a root cause analysis.

Temporary instability of gateway services in eu-central-1 cluster. Potential behaviours observed: DNS Resolution issues, Policies not being enforced.

The issue is fixed in the new Jamf Trust iOS version 11.39.2. If you experience the connectivity issue, please restart your device and install the newest Jamf Trust iOS version available in Apple App Store.

We have identified potential connectivity loss issue for iOS devices that are using on-device content filtering and installed the newest Jamf Trust iOS 11.39.1. The issue is intermittent and might not impact all the devices. If you experience loss of connectivity, restart of the device should temporarily fix it. We are working hard to resolve the issue.

Incident is now resolved - fix was rolled out. We are still performing a root cause analysis.

Temporary instability of gateway services in eu-central-1 cluster. Potential behaviours observed: DNS Resolution issues, Policies not being enforced.

This is fixed in the macOS 15.0.1 release

The impact of this issue is for macOS 15 devices who have both iCloud Private Relay and Network Firewall enabled, and using the Jamf Security Cloud portal or the Jamf Safe Internet portal.

The investigation revealed that the issue is caused by an update to the macOS Firewall introduced in macOS 15. We have notified Apple of the situation and are awaiting their response. Based on new information, we have identified an additional workaround to resolve the issue on affected devices. The Firewall can be disabled either through System Preferences > Network > Firewall or via MDM.

We are continuing to investigate this issue.

We are actively investigating this issue. Due to iCloud Private Relay taking precedence over Jamf's Security Cloud capabilities, resources that are only accessible via Network access may not be reachable in Safari. This may also negatively impact the enforcement of Security policies and Content controls. Here are identified workarounds for IT administrators: -Disable the firewall via Jamf Pro - If you use an alternative MDM, please consult their documentation to disable the firewall. -Disabling iCloud Private Relay via Jamf Pro - If you use an alternative MDM, please consult their documentation to disable iCloud Private Relay. -In Jamf Security Cloud, navigate to Settings → Notifications → Block Pages, and select the “Block iCloud Private Relay" option, which will notify users with a pop-up to disable iCloud Private Relay to restore Internet connectivity. Alternatively there are actions your End Users can take: -Turn off the Firewall in macOS 15. -Use an alternative browser to Safari. -Turn off iCloud Private Relay on macOS 15

Temporary instability of gateway services in eu-west-2 cluster. Potential behaviours observed: DNS Resolution issues, Policies not being enforced. Incident started around 10am (CET). Should be resolved as of 11:10am (CET).

This incident has been resolved.

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

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

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

We are currently investigating this issue.

This incident has been resolved and connectivity to JCDS packages have been restored.

We are in the process of deploying a non-user initiated fix for this issue. We anticipate that all impacted instances will have their JCDS access restored by 2000 UTC Friday September 27, 2024.

We have identified an issue related to missing packages in JCDS for a small number of instances. If you believe you are impacted by this outage, you can remediate by re-enabling your Cloud Service Connection. It may take up to 1 hour for packages to be available after this step is completed. https://learn.jamf.com/en-US/bundle/jamf-pro-documentation-current/page/Cloud_Services_Connection.html We are actively working on a non-user initiated fix for this issue. Additional details will be provided by 1900  UTC Friday September 27, 2024.

This incident has been resolved.

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

We are currently investigating this issue.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

We are continuing to monitor for any further issues.

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

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

We are currently investigating this issue.

This incident has been resolved.

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

Important information for teachers and students using the full capabilities of the Jamf School Student and Jamf Teacher apps. We are currently experiencing an outage in our app’s notification system. Users (both teachers and students) may encounter issues with the app’s functionality. This particularly affects the following features: • Raise Hand (this feature is not working correctly) Additionally, some functionalities will work but with limited capacity (e.g., notifications will not be sent). These include: • Remote class • Messages • Exams • App requests • Start lesson Our engineers have identified the cause of the problem and are working on a solution.

This incident has been resolved.

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

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

We are currently investigating this issue.

This incident has been resolved.

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

Jamf School Licensing is currently not available. We're investigating the issues.

This incident has been resolved.

An issue has been identified that is affecting some Jamf Pro customers. We are working to resolve and will provide next update in 45 minutes.

This incident has been resolved.

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

We are currently investigating this issue.

The JCDS is now operational and access to files in the JCDS has been restored. We apologize for any inconvenience this has outage may have caused.

Details: Customers may not be able to access JCDS files that were uploaded prior to an internal Jamf system change on 5 August 2024. All customer assets will be restored shortly. Current Actions: Jamf is currently working on a fix to restore access to packages, apps, and books to customers who are experiencing this issue. Impact: Packages, apps, and books that were stored in JCDS will not be able to be deployed to end user devices until resolved. Status: Ongoing Estimated resolution: 2359 UTC Tuesday, August 6, 2024

This incident has been resolved.

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

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

This incident has been resolved.

An issue has been identified that is affecting some Jamf Pro customers. We are working to resolve and will provide next update in 45 minutes.

This incident has been resolved.

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

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

We have narrowed down that the only workflow affected is trying to Add an iOS app by following these steps: Apps > Apps Inventory > Add App > Add iOS app

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

We've identified issues related to Apps & Books API, which prevent customers from adding new apps (iOS, macOS, VPP).

This incident has been resolved.

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

We are currently investigating this issue.

Incident has been resolved and all instances are back online.

We are continuing to monitor for any further issues.

Continuing to monitor, there is a very small set of customers that are affected currently in APAC regions, we don't anticipate this lasting more than an hour currently.

An issue has been identified that is affecting some Jamf Pro customers in our APAC regions, specifically the database service. We are working to resolve and will provide next update in 45 minutes.

The fix has been applied and now been propogated to all services. We apologize for the inconvenience caused.

Currently we are monitoring an ongoing JCDS issue. The fix has been implemented and we are awaiting for the propagation to apply. We will continue to keep this page upadted with new information.

Currently we are monitoring an ongoing JCDS issue, affecting the AMER region that is preventing usage. The fix has been implemented and is propagating here soon.

This incident has been resolved.

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

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

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

We've identified an issue preventing customer from signing and deploying in-house packages

This incident has been resolved.

We are currently investigating an issue where internal resources aren't accessible in the region of North America USA East as of right now.

This incident has been resolved.

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

We are continuing to investigate this issue.

We are currently investigating this issue.

This issue has been identified as Product Issue (JTWIN-3614 - internet connectivity disconnections while using ZTNA within Jamf Trust on Windows). The issue affects only Windows Jamf Trust app for devices with ZTNA capability. We are actively working on resolving the issue. We will continue to communicate directly with a small number of impacted customers. For further information or if you are experiencing any issues with ZTNA within Jamf Trust on Windows - please contact Jamf Support.

We are continuing to test viable solutions, and our team are focussed on delivering an ideal outcome as soon as possible. We will continue to communicate directly with the small number of impacted customers as we work toward identifying a permanent fix. This issue affects only the Windows Jamf Trust app for devices with ZTNA capability. No other impact has been identified. This page will be updated as more information becomes available.

We are actively investigating an issue that results in internet connectivity disconnections while using ZTNA within Jamf Trust on Windows. This often resolves itself after a few seconds. In certain circumstances it is reported that reboot is required to resolve this issue. We will continue to communicate directly with a small number of impacted customers as we work toward identifying a permanent fix. The issue affects only Windows Jamf Trust app for devices with ZTNA capability.

This incident has been resolved.

On specific version of the On-device classification (ODCF app ver. 11.29), content classification is unable to classify the host. Therefore, blocking of internet according to set up internet policy does not work on those devices. The issue has been identified and fix is in progress of being released

This incident has been resolved.

We are currently investigating this issue.

We have finished the investigation and the remediation of the issue. We continue to work directly with a small number of impacted customers. At this time we will continue to monitor the situation, thank you for everyone's patience and we apologize for any disruptions this might have caused.

We’re happy to announce a Jamf Pro 11.3.2 is now available for the issues reported. Our team has worked hard to ensure your operations can continue smoothly. Please be aware, continued outages could be due to not updating to the Jamf Pro 11.3.2. To resolve these issues, we urge all customers to upgrade immediately. We appreciate your prompt action on this and thank you for your ongoing support.

We’ve identified a potential root cause for a recent issue and are engineering team are actively working on a solution. We appreciate your patience and will provide further updates as soon as possible.

We’ve identified a potential root cause for a recent issue and are actively working on a solution in order to resolve it. We appreciate your patience and will provide further updates as soon as possible.

We’ve identified a potential root cause for a recent issue and are actively working to resolve it. We appreciate your patience and will provide further updates as soon as possible.

We are continuing to investigate this issue.

We are continuing to address a performance issue affecting some of our services. Our technical teams are actively working on measures to ensure system stability and are closely monitoring the situation. We are dedicated to minimizing any impact on our customers and are making progress toward a resolution. Further updates will be shared as they become available. We appreciate your continued patience and understanding.

We wanted to provide an update on the ongoing service interruption that began earlier today. Despite our best efforts, the issue persists, and our engineering team remains fully engaged in resolving it. Here's a brief overview of the current situation: Issue Status: There is a small amount of services have an interruption which was caused by a 503 error. Current Efforts: Our team is actively analysing system logs and performance metrics to identify and address the root cause of the problem. Progress is being made, but the issue remains unresolved at this time. Impact Reminder: Users may continue to experience difficulties accessing our services. We understand the frustration this may cause and are committed to restoring normal operations as quickly as possible. Next Steps: We are exploring all possible solutions and avenues to expedite the recovery process. Rest assured, we will keep you updated with any new developments. Thank you for your continued patience and understanding during this challenging time. We are fully dedicated to resolving this issue and minimising any further disruptions.

We wanted to provide an update on the ongoing service interruption that began earlier today. Despite our best efforts, the issue persists, and our engineering team remains fully engaged in resolving it. Here's a brief overview of the current situation: Issue Status: There is a small amount of services have an interruption which was caused by a 503 error. Current Efforts: Our team is actively analysing system logs and performance metrics to identify and address the root cause of the problem. Progress is being made, but the issue remains unresolved at this time. Impact Reminder: Users may continue to experience difficulties accessing our services. We understand the frustration this may cause and are committed to restoring normal operations as quickly as possible. Next Steps: We are exploring all possible solutions and avenues to expedite the recovery process. Rest assured, we will keep you updated with any new developments. Thank you for your continued patience and understanding during this challenging time. We are fully dedicated to resolving this issue and minimising any further disruptions.

We wanted to provide an update on the ongoing service interruption that began earlier today. Despite our best efforts, the issue persists, and our engineering team remains fully engaged in resolving it. Here's a brief overview of the current situation: Issue Status: There is a small amount of services have an interruption which was caused by a 503 error. Current Efforts: Our team is actively analysing system logs and performance metrics to identify and address the root cause of the problem. Progress is being made, but the issue remains unresolved at this time. Impact Reminder: Users may continue to experience difficulties accessing our services. We understand the frustration this may cause and are committed to restoring normal operations as quickly as possible. Next Steps: We are exploring all possible solutions and avenues to expedite the recovery process. Rest assured, we will keep you updated with any new developments. Thank you for your continued patience and understanding during this challenging time. We are fully dedicated to resolving this issue and minimising any further disruptions.

We wanted to provide an update on the ongoing service interruption that began earlier today. Despite our best efforts, the issue persists, and our engineering team remains fully engaged in resolving it. Here's a brief overview of the current situation: Issue Status: The service interruption caused by a 503 error is ongoing. Current Efforts: Our team is actively analysing system logs and performance metrics to identify and address the root cause of the problem. Progress is being made, but the issue remains unresolved at this time. Impact Reminder: Users may continue to experience difficulties accessing our services. We understand the frustration this may cause and are committed to restoring normal operations as quickly as possible. Next Steps: We are exploring all possible solutions and avenues to expedite the recovery process. Rest assured, we will keep you updated with any new developments. Thank you for your continued patience and understanding during this challenging time. We are fully dedicated to resolving this issue and minimising any further disruptions.

Issue Status: Ongoing Update: It’s been over two hours since we first reported the service interruption caused by a 503 error. Our engineering team is fully committed to resolving the underlying issues. Current Efforts: Analysis of system logs and performance metrics is ongoing, with our team working tirelessly to find and implement a fix. Progress is being made, though the issue remains unresolved. Impact Reminder: Users may still experience difficulties accessing our services. We are aware of the inconvenience this causes and are focused on restoring normal operations as quickly as possible. Next Steps: We are continuing to pursue all avenues to speed up the recovery process and will provide updates as soon as new information becomes available. Thank you for your continued patience and understanding. Our team is dedicated to resolving this issue as swiftly as possible.

Service Update We are continuing to work diligently to resolve the service interruptions currently impacting our customers. Our team is fully engaged and focused on rectifying the issue as swiftly as possible. Ongoing Actions: Our investigation is still in progress, with all efforts aimed at identifying and implementing a solution promptly. We have mobilized additional resources to ensure a rapid resolution. Staying Informed: We are committed to providing you with the latest updates as our work progresses. Another update will be provided in about 2 hours. Thank you for your continued patience and understanding.

Details: We’re currently addressing an issue marked by a 503 error, affecting access to our platform. Technical challenges are impacting our ability to process requests. Current Actions: Our engineering team is actively working on identifying and resolving the issue. We’re analyzing system logs and performance to quickly restore service. Impact: Users may experience an inability to login and may see failures around self-service connections and enrollments. Status: Ongoing. We’re dedicated to minimizing disruption and restoring full functionality. We appreciate your patience and are committed to resolving this as swiftly as possible

An issue has been identified that is affecting some Jamf Pro customers. We are working to resolve and will provide next update in 45 minutes. Currently this seems to be related to communication with APNS.

This incident has been resolved.

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

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

There is an issue which is blocking all macOS enrollments and any iOS/iPadOS enrollments which require authentication.

This incident has been resolved.

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

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

We have identified a problem with our user service communication in the Jamf Security Cloud and Jamf Safe Internet environments, we are working on a resolution. Services impacted may include: User service affecting administrator access to the JSC portal, - Enrolment services - resolution implemented - Reporting services - pending resolution - Policy services - resolution implemented We are still working on the reporting services and will post updates as soon as we have more information.

This incident has been resolved.

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

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

We are continuing to investigate the issue. Following workflows have been impacted: - downloading CSR token used for generating new and renewing APNs certificate - Installing AppStore Apps

We are currently investigating this issue.