Jamf Status

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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