Jamf incident

Jamf Pro - GCC High Device Compliance Issue

Major Resolved View vendor source →

Jamf experienced a major incident on March 26, 2026 affecting us-west-2: Jamf Pro - Standard and us-west-2: Jamf Pro - Premium and 1 more component, lasting 2h 9m. The incident has been resolved; the full update timeline is below.

Started
Mar 26, 2026, 01:42 PM UTC
Resolved
Mar 26, 2026, 03:52 PM UTC
Duration
2h 9m
Detected by Pingoru
Mar 26, 2026, 01:42 PM UTC

Affected components

us-west-2: Jamf Pro - Standardus-west-2: Jamf Pro - Premiumus-east-2: Jamf Pro - Standardus-east-2: Jamf Pro - Premium

Update timeline

  1. investigating Mar 26, 2026, 01:42 PM UTC

    The Jamf Pro integration with GCC High Device Compliance is currently not working. New integrations and new registrations are not possible and device compliance state is not sent. We have identified the cause and we are currently working towards a resolution.

  2. identified Mar 26, 2026, 01:44 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Mar 26, 2026, 02:20 PM UTC

    The GCC High Device Compliance for Jamf Pro - Standard and Premium is restored, we are continuing to work towards restoring service for Jamf Pro - Premium Cloud Plus.

  4. monitoring Mar 26, 2026, 03:29 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Mar 26, 2026, 03:52 PM UTC

    This incident has been resolved.