Jamf Outage History

An outage affected Jamf Account, rendering the Jamf Account page and related authentication features inaccessible for about 40 minutes. The incident began at Mar 19, 2025 5:09 PM UTC when the Jamf Account component transitioned from up to down, and it was resolved at Mar 19, 2025 5:49 PM UTC when the component returned to normal. The Jamf status page documented the outage and provided a brief investigation update, followed by restoration of the Jamf Account. In total, the provider issued 2 status updates during the incident. The issue appeared to be limited to the Jamf Account component, with no other Jamf services indicated affected.

Jamf School in the eu-central-1 region experienced a brief outage with temporary unavailability for regional users. The outage began at 9:49 AM UTC and was resolved by 11:44 AM UTC, lasting approximately 1 hour and 55 minutes. The issue appeared isolated to Jamf School in eu-central-1 and did not involve a global outage. User reports were limited during the incident.

Jamf Pro experienced a partial outage affecting some customers in the EU-west-2 region. The issue, identified by Jamf, impacted Jamf Pro - Standard in eu-west-2 and caused degraded access for about 35 minutes. The outage began at 2:39 PM UTC and was resolved by 3:14 PM UTC. Jamf issued two status updates during the incident, noting that they were working to resolve the problem. User reports from Europe (including the United Kingdom) corroborated the disruption during the window.

Jamf School in the EU-Central-1 region underwent a scheduled maintenance window from 10:04 PM UTC to 12:04 AM UTC. The Jamf status page indicated the maintenance was in progress during this period, with normal operation expected to resume after the window. Users in this region may have experienced limited access to Jamf School features while maintenance was in effect. The status updates show the component transitioned from up to maintenance and back to up, marking the end of the window.

Jamf School in the us-east-1 region underwent a scheduled maintenance window that temporarily affected the service. The maintenance began at 7:34 AM UTC and was completed by 9:34 AM UTC, lasting about 2 hours.

Jamf School in the ap-northeast-1 region experienced a brief service interruption during scheduled maintenance. The incident began at 12:00 PM UTC and was resolved by 2:04 PM UTC, lasting about 2 hours and 4 minutes. The provider issued 2 status updates during the outage, confirming the maintenance and subsequent recovery. The impact was limited to Jamf School in the ap-northeast-1 region.

Jamf reported an authentication issue affecting Jamf Account logins, preventing users from signing into Jamf ID. The incident began around 6:28 PM UTC when the issue was identified, and the Jamf Account component moved to a degraded state by 6:34 PM UTC. The problem persisted until 8:59 PM UTC when login access was restored. The Jamf status page provided updates describing the identification of the problem and that a fix was being implemented, followed by restoration of normal service. User reports during the window described login failures from multiple locations, indicating a brief but noticeable impact.

Jamf Account experienced an outage that affected access to the Jamf Account component for about 30 minutes. The incident impacted Jamf Account features used for authentication and account management. According to Jamf's status page, the outage began when Jamf Account moved to the down state at Feb 26, 2025 7:39 AM UTC. The page noted that the issue had been identified and a fix was in progress at Feb 26, 2025 7:37 AM UTC. The service was restored by Feb 26, 2025 8:09 AM UTC, and the provider issued two status updates during the incident.

Jamf Account was briefly unavailable due to a short outage affecting the Jamf Account component. The incident began at 6:24 PM UTC and was resolved by 6:34 PM UTC, lasting about 10 minutes. The Jamf status page reported an outage and ongoing investigation, followed by a restoration update confirming the Jamf Account component was back online. Users attempting to access Jamf Account features may have experienced temporary login or account-related disruptions during the window. The incident involved two official status updates from Jamf during the event.

Jamf experienced a TLS certificate misconfiguration impacting a subset of core services, causing new login attempts to fail while existing sessions remained connected. Active RADAR sessions were expected to stay connected, but new logins were unavailable during the incident. The impact spanned six components within Jamf Threat Defense, Jamf Private Access and Jamf Data Policy, including Authentication and Admin Management, Device Management, and Reporting.

The outage began at 3:55 PM UTC and was resolved by 4:29 PM UTC, lasting about 34 minutes. Jamf issued two status updates during the incident to communicate ongoing investigation and eventual restoration of services.