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 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 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 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.

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 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 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.

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 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.

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

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.

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 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.

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.

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.

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.

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.

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: 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: 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.

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

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.

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.

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

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

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.

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.

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.

The fix has been applied and now been propogated to all services. We apologize for the inconvenience 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. Currently this seems to be related to communication with APNS.

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

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.

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.

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.

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 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 are continuing to investigate this issue.

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’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 are continuing to work on a fix for this issue.

We’re happy to announce a hotfix 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 version with the hotfix. 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.

auto-closed

We are currently investigating this issue.

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

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

An issue has been identified that is affecting some Jamf Pro Premium Cloud customers hosted in the us-east-1 region. We are working to resolve and will provide next update in 45 minutes.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue that is affecting some Jamf Pro Premium Cloud customers hosted in the us-east-1 region. We will provide an update ASAP.

We are continuing to investigate this issue.

We have finished the investigation and the remediation of the issue. 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.

This incident has been resolved.

An issue has been identified affecting Jamf Pro Cloud: - instance creations, updates, and deletes may fail - some instances may see SSL errors Engineers have identified the issue and are working to resolve it as soon as possible

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

We continue to work towards a resolution of this issue.

We have a team dedicated to finding the root source of the issue. We are close to identifying the source and will implement a fix as soon as possible. We apologize for the inconvenience this caused over the last few days.

Our team is actively working to resolve the issue and restore normal service as quickly as possible. We apologize for the inconvenience.

Our team is actively working to resolve the issue and restore normal service as quickly as possible. We have completed ap-northeast-1, we will update this thread as regions complete. We apologize for the inconvenience.

While we continue to work to resolve this issue, we also have identified a small number of instances that may be temporarily unavailable in the regions marked as "partial outage"

We understand the critical role our cloud services play in your operations and sincerely apologize for the current inconvenience. Please be assured that we are fully committed to swiftly resolving this issue by deploying all necessary resources. Thank you for your understanding and patience.

We recognize the significant impact this outage may have on your operations and sincerely apologize for the inconvenience. Please be assured that our team is fully committed and working tirelessly to resolve this issue promptly. We anticipate the current disruptions may continue well into the weekend, but we are making every effort to restore services to full capacity as quickly as possible. Your understanding and patience are greatly appreciated during this time.

We have completed ap-southeast-2, eu-central-1, eu-west-2, us-east-1 regions. We are continuing to resolve issues in us-west-2, ap-northeast-1. Thank you for your patience.

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

We have completed applying the fix in the ap-southeast-2 region. We are continuing to resolve issues in us-west-2, ap-northeast-1. Thank you for your patience.

We have completed applying the fix in the ap-northeast-1 and us-west-2 regions. We are continuing to monitor for additional issues. Thank you for your patience.

The incident affecting our cloud servers has been successfully resolved. We have conducted a thorough review of our systems and will be conducting an internal investigation of the incident. We understand the importance of our cloud services to your business operations, and we apologize again for any inconvenience this incident may have caused.

We are currently investigating this issue.

This incident has been resolved.

We are currently investigating this issue.

We are continuing to investigate this issue.

This incident has been resolved.