Jamf Outage History

Jamf School experienced a partial outage in its outbound emailing service, preventing outbound emails from being delivered for users across three regions: ap-northeast-1, eu-central-1, and us-east-1. The incident began at Feb 23, 2026 6:59 AM UTC and prompted Jamf School to list the issue as an Emailing Outage. The affected components spanned the three regions, and users likely did not receive automatic or notification emails during the outage. Jamf issued emails and status updates indicating the problem and ongoing investigation.

Jamf School in the eu-central-1 region had a brief maintenance window. The status page shows the service transitioning from normal operation to maintenance at 5:09 AM UTC and back to normal at 5:14 AM UTC, lasting about 5 minutes.

Jamf School in the eu-central-1 region entered a maintenance window starting at Feb 21, 2026 2:04 AM UTC and was restored at Feb 21, 2026 5:04 AM UTC. The Jamf School component in eu-central-1 was listed as under maintenance during this period, with services temporarily affected in that region. The maintenance lasted about 3 hours.

The Jamf status page posted two official updates during the incident, documenting the maintenance and the restoration of service. The impact was regional to eu-central-1 with no indications of broader impact.

The Jamf School service in the ap-northeast-1 region entered maintenance at 12:04 PM UTC and returned to normal at 2:04 PM UTC, lasting about two hours. This was a planned maintenance window; the Jamf status page issued two updates during the period. No broad outages were reported, and the impact was limited to Jamf School in ap-northeast-1.

Jamf School in the ap-northeast-1 region underwent a scheduled maintenance window. The service transitioned to maintenance mode from Feb 18, 2026 12:04 PM UTC to Feb 18, 2026 2:04 PM UTC, a duration of about 2 hours. The Jamf status page posted two updates during the window, and service returned to normal after the maintenance window. The maintenance affected only the Jamf School component in ap-northeast-1.

Jamf School in the ap-northeast-1 region underwent a scheduled maintenance window that briefly impacted service. The maintenance began at Feb 17, 2026 12:04 PM UTC and ended at Feb 17, 2026 2:04 PM UTC, lasting about 2 hours. The Jamf status page indicated Jamf School transitioned from maintenance back to normal operation once the window concluded, with services restored after the period.

Jamf School in the ap-northeast-1 region entered a maintenance state starting at Feb 16, 2026 12:09 PM UTC and returned to normal at Feb 16, 2026 3:04 PM UTC, for a duration of approximately 2 hours and 55 minutes. The Jamf status page showed the service transitioning from up to maintenance and back to up, with two status updates issued during the incident.

The Jamf School service in us-east-1 entered a scheduled maintenance window starting at 8:04 AM UTC and ending at 11:04 AM UTC, with users potentially experiencing access during that period. The maintenance activity caused a temporary disruption for the duration of the window, and the status page indicated Jamf School transitioning to maintenance before returning to normal once the window closed, lasting about 3 hours.

The Jamf Status Page published two updates confirming the maintenance and the subsequent restoration, marking the incident as resolved when the service returned to normal.

Jamf Security Cloud experienced a degraded notification flow related to App Store apps flagged as sideloaded. The issue began at Feb 3, 2026 10:24 PM UTC and was resolved by Feb 4, 2026 4:24 PM UTC, lasting about 18 hours. During this period, threat-detection alerts may have been delayed or inconsistent, and device risk state updates used by Access policies could have been affected.

Jamf issued an advisory that devices running iOS/iPadOS 26.1 with On-Device Content Filtering enabled may lose network connectivity if Jamf Trust is updated to version 11.47.0 or later on unstable networks. In some cases the update could hang and require a factory reset. The issue affects any app that uses the On-Device Content Filtering extension on iOS and is not limited to Jamf Trust. The impact appeared as degraded connectivity for affected users during updates. The Jamf status page shows the issue began when it transitioned from up to degraded at Feb 1, 2026 9:39 PM UTC, remained degraded through Feb 3, 2026 5:59 PM UTC, and was resolved back to up at Feb 3, 2026 8:11 PM UTC. Apple resolved the underlying issue in iOS/iPadOS 26.2 and Jamf recommended updating devices to iOS 26.2 before updating Jamf Trust, or ensuring devices are on a stable network during updates. A report from Windsor, Vermont, highlights the real-world connectivity impact. The incident spanned about two days from the initial advisory to resolution.