Jamf Outage History

Jamf School in the eu-central-1 region underwent a scheduled maintenance window starting at 5:04 PM UTC and concluding at 11:04 PM UTC. The six-hour maintenance affected Jamf School services in that region, resulting in user-facing unavailability or degraded access during the maintenance period.

Jamf communicated the maintenance via its status page, posting two updates: one noting the start of maintenance and another confirming restoration once the window ended. The impact was regional to eu-central-1, with services returning to normal after the maintenance completed.

Jamf School in the us-east-1 region underwent a scheduled maintenance window, briefly affecting access while updates were applied. The maintenance began at 7:04 AM UTC and concluded at 10:04 AM UTC, lasting about 3 hours. The incident was limited to the Jamf School component in us-east-1.

The provider issued two status updates during the incident: one announcing the start of maintenance and another confirming the service had returned to normal in us-east-1.

Jamf School in the ap-northeast-1 region underwent scheduled maintenance from 12:00 PM UTC to 3:04 PM UTC. The status page showed the window as in progress and issued 2 updates during the incident. The service returned to the up state at 3:04 PM UTC.

Jamf School experienced a brief degradation in the ability to add or remove devices from groups, affecting two regions: eu-central-1 and us-east-1. Users could encounter failures when managing group memberships, with the incident lasting about 45 minutes from 10:44 AM UTC to 11:29 AM UTC.

Jamf School's status page indicated an investigation began at 10:39 AM UTC, with the affected components resuming normal operation by 11:29 AM UTC. The provider posted 2 status updates during the incident.

Impact was limited to Jamf School in eu-central-1 and us-east-1, with no broader regional impact indicated.

Jamf Security Cloud experienced an outage when secure DNS services failed due to an incorrect certificate, impacting three components: Jamf Threat Defense, Jamf Private Access, and Jamf Data Policy / Private Access. End users attempting to access or authenticate through these services faced connectivity and access issues. The outage began at 3:04 AM UTC and was resolved by 4:34 AM UTC, lasting about 1 hour and 30 minutes. The incident was reflected on the Jamf status page as an ongoing investigation during the event, with gradual updates as engineers worked to restore services. Two status updates were posted during the incident.

Jamf Pro customers across APAC, EU, and US experienced a partial outage starting around 8:44 PM UTC. The incident affected Jamf Pro Standard and Premium instances, leading to portal access failures and enrollment problems for many users. Reports described 504 gateway timeouts and related errors when loading the Jamf Pro console and enrolling devices. The outage impacted a broad set of regions, with many services intermittently unavailable while a fix was being implemented.

The Jamf status page issued seven official updates as teams investigated an infrastructure issue and worked to deploy a fix. By 3:04 PM UTC the status indicated all Premium and APAC instances had been resolved and EU and US standard instances were largely restored, though some custom URL configurations remained intermittent. Over the next several hours, standard instances continued to recover, with us-east-1, eu-central-1, us-west-2, and us-east-2 moving from down to up by 6:09 PM UTC. The outage lasted about 22 hours in total and affected a large portion of Jamf Pro deployments.

The Jamf Pro service experienced a partial outage beginning at Apr 15, 2025 9:07 PM UTC, affecting both Jamf Pro Standard and Premium instances across APAC, EU, and US regions. An Early Warning Signal appeared first in the eu-central-1 region, with StatusGator detecting issues at Apr 15, 2025 8:33 PM UTC, about 11 minutes before Jamf acknowledged the problem at Apr 15, 2025 8:44 PM UTC. Users reported widespread access problems, including 504 gateway timeouts and difficulties enrolling devices or managing the Jamf Pro portal. The issue originated in eu-central-1 and spread to additional regions, leading to degraded performance and partial outages for many customers.

Jamf Pro - Standard in the ap-northeast-1 region experienced a partial outage affecting some Jamf Pro customers. The Jamf status page stated that an issue had been identified and that the team would provide the next update in about 45 minutes. The incident began at Apr 15, 2025 8:29 AM UTC and was resolved by Apr 15, 2025 8:59 AM UTC, lasting roughly 30 minutes. The provider issued two status updates during the incident before restoring normal service.

Jamf reported a partial outage affecting Jamf Pro Standard in the EU-West-2 region, with on-device content controls showing degraded performance. Since around 1:00 AM UTC, customers reported issues with iOS and Windows content filtering and with content filtering policy pages in the Jamf Security Cloud console. The impact covered four components across Jamf Pro Standard eu-west-2 and Jamf Security Cloud services.

Jamf issued four status updates during the incident. Jamf Pro Standard in eu-west-2 returned to normal by 7:44 AM UTC, while the broader on-device content controls degradation affected Jamf Threat Defense, Jamf Private Access and Jamf Data Policy / Data Policy. Those components recovered to up by 2:19 PM UTC. The incident lasted from around 1:00 AM UTC to 2:19 PM UTC, roughly 13 hours 19 minutes.

Jamf Safe Internet experienced a brief regional incident affecting US data residency handling, where requests were not being classified and blocked as expected. This impacted Jamf Threat Defense, Jamf Private Access, and Jamf Data Policy components, potentially allowing unclassified traffic during the window. A fix was implemented at Mar 20, 2025 2:04 PM UTC and Jamf began monitoring the results; the status moved to warning at Mar 20, 2025 2:09 PM UTC and was restored to up by Mar 20, 2025 2:19 PM UTC. The Jamf status page posted two updates during the incident, reflecting the quick containment and resolution. The impact was regional to US residency workloads.