Jamf Outage History

An incident in Jamf's US-East-1 region disrupted Jamf School and Jamf Protect, causing data processing and alerting to be impaired. Users in this region experienced outages affecting Jamf School and the telemetry/alerts pipelines feeding Jamf Cloud, with ULogs and telemetry delayed or unavailable. The disruption began at Oct 20, 2025 3:14 PM UTC and persisted for about 21 hours and 55 minutes, with services gradually returning to normal and Jamf School reporting a return to normal status in us-east-1 by Oct 21, 2025 1:09 PM UTC.

Jamf experienced a regional disruption beginning at 9:56 AM UTC that briefly affected Jamf Insights in US-East-1, where Jamf Insights Standard and Service Enabled components went offline. In EU-West-2, Jamf Insights Standard and the Service Enabled status were degraded during the incident, indicating partial disruption for users in that region. The outage impacted access to Jamf Insights features and reporting in the affected regions.

Over about 38 minutes, Jamf issued 3 status updates documenting the incident. The US-East-1 components recovered by 10:34 AM UTC, and EU-West-2 components were restored by the same time. In total, four Jamf Insights components across two regions were affected. The incident was regional in scope, not global.

The outage affected Jamf Now in the US-East-1 region as part of a broader disruption impacting Jamf products following an AWS incident. The issue began at Oct 20, 2025 9:48 AM UTC and resolved about five minutes later at Oct 20, 2025 9:53 AM UTC. Jamf Now was listed as down during the incident, with users experiencing temporary service unavailability.

Jamf School in the US-East-1 region experienced degraded performance beginning at Oct 14, 2025 8:29 PM UTC, with the Admin UI and API impacted. Jamf's status page indicated the issue had been identified and that a fix was in progress. The incident lasted about 11 hours and 50 minutes, ending at Oct 15, 2025 8:19 AM UTC when the service was reported as restored. The Jamf status page published two updates during the event, detailing the degradation and remediation steps.

The incident began on 5:04 PM UTC with Jamf reporting degraded performance across Jamf Insights in multiple regions, including us-east-1 and eu-west-2. Users experienced issues such as mobile device data not displaying correctly and delays in activation processing across Threat Defense, Private Access and Data Policy. The Tokyo region also reported DNS latency affecting device enrollments. The Jamf status page provided regular updates over the following weeks, with the last affected components restoring to normal by Oct 13, 2025 3:24 PM UTC. The outage spanned roughly three weeks and impacted several Jamf services in multiple regions.

The Jamf School service in the eu-central-1 region experienced a brief outage beginning at Sep 24, 2025 8:44 AM UTC and ending at Sep 24, 2025 8:54 AM UTC, lasting about 10 minutes. This localized incident affected users accessing Jamf School from Europe, with the impact limited to the eu-central-1 data center. The outage interrupted access to Jamf School features for a short period while the region recovered.

Jamf School in the eu-central-1 region experienced a brief outage beginning at Sep 24, 2025 8:43 AM UTC with users reporting 504 Gateway Timeout errors when accessing the service. Jamf acknowledged the issue at Sep 24, 2025 8:44 AM UTC and said they were investigating. StatusGator detected an Early Warning Signal with 504 errors starting at Sep 24, 2025 8:36 AM UTC and ending at Sep 24, 2025 8:47 AM UTC. The outage appeared isolated to Jamf School in eu-central-1 while other regions remained unaffected.

The Jamf School service in the eu-central-1 region experienced degraded performance with slower loading times beginning at Sep 18, 2025 8:14 AM UTC. The Jamf status page indicated an investigation as the issue was investigated and a degradation was noted. The service returned to normal at Sep 18, 2025 10:39 AM UTC, lasting approximately 2 hours and 25 minutes. The incident affected a single component: Jamf School in eu-central-1, with two updates posted on the Jamf status page during the event.

A degraded service state affected Jamf Cloud Connector for Jamf Self Hosting customers integrating with the US Government sovereign cloud Device Compliance. The issue began at 2:14 PM UTC and was resolved by 4:04 PM UTC. The provider issued 2 status updates during the incident, noting that the issue had been identified and a fix was being implemented. The incident impacted a single component (Jamf Cloud Connector) and was resolved once status returned to up.

Jamf School in the EU-Central region experienced degraded performance for about 50 minutes, impacting users attempting to access Jamf School in eu-central-1. Reports described issues with loading and sessions being terminated, with affected users including those in Belgium and the United Kingdom. The Jamf status page first indicated investigation around Sep 4, 2025 11:44 AM UTC and then moved to a degraded state at Sep 4, 2025 11:49 AM UTC, with the incident resolving and the service returning to normal by Sep 4, 2025 12:39 PM UTC. The provider posted two status updates during the incident, acknowledging degraded performance and subsequent restoration. The issues appeared regional to EU-Central rather than global, and there was a small number of user reports of login/loading problems.