Jamf Outage History

Jamf Protect experienced degraded performance for 21.4 hours, affecting console performance and causing delays in alerting and insights functionality. The issue was identified and a fix was implemented, restoring console performance while the system processed the accumulated backlog. The incident was fully resolved with all services returning to normal operation.

Jamf School experienced degraded performance for 8.2 hours affecting users in both US East and EU Central regions. The issue was identified and a fix was implemented, with monitoring confirming full resolution.

Jamf Pro experienced a 7-hour issue with Blueprints functionality that affected customers running versions 11.24 and below across multiple regions including Premium service tiers. The problem impacted Jamf Pro Premium services in six regions: ap-northeast-1, ap-southeast-1, eu-central-1, eu-west-2, us-east-1, and us-west-2. A fix was implemented and monitored before the incident was fully resolved.

Jamf Pro's integration with GCC High Device Compliance failed for 2.2 hours, preventing new integrations, device registrations, and compliance state reporting for Standard and Premium tiers in the us-west-2 region. The issue was identified and resolved with a fix that restored service functionality.

Jamf experienced a 4.1-hour partial outage affecting Blueprints, Compliance Benchmarks, and Volume Purchasing Services across multiple regions including Jamf Pro and Jamf School instances. The outage impacted services in ap-northeast-1, ap-southeast-2, ap-southeast-1, eu-central-1, eu-west-2, and us-east-1 regions. The issue was identified and resolved with a fix that was monitored before full resolution.

Jamf Pro experienced degraded performance in the US West 2 region for 3.3 hours, affecting the Standard service tier. The issue was identified and a fix was implemented, with the incident fully resolved after a monitoring period.

Jamf Pro experienced performance issues in the US West 2 region, affecting the Standard service component. The incident lasted 7 minutes while the team actively investigated and resolved the performance degradation.

Jamf Pro 11.25 experienced an issue where Smart Groups generated invalid membership lists when using criteria for Device Ownership Type and Personal Device Profiles, affecting all standard Pro instances across multiple regions. The problem caused Smart Groups with invalid Device Ownership Type values to incorrectly include Institutional devices in their membership. The issue was resolved after 43 hours with the deployment of Jamf Pro 11.25.2 to all affected instances.

Jamf School experienced a major outage affecting their emailing service, preventing outbound emails from being delivered across all regions (ap-northeast-1, eu-central-1, and us-east-1). The incident lasted 4.1 hours before a fix was implemented and service was restored. The team monitored the fix for approximately 24 minutes before confirming full resolution.