Jamf incident
Intermittent authentication failures across Jamf services
Jamf experienced a notice incident on November 16, 2025 affecting Jamf Account and Jamf ID, lasting 8m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- monitoring Nov 16, 2025, 08:53 PM UTC
Some customers experienced a temporary inability to authenticate via OIDC when accessing services with Jamf ID or their IdP configured in Jamf Account, due to an upstream issue with our IDaaS provider. Affected Services: All Jamf services relying on Jamf ID / OIDC authentication Affected Regions: Global Business Impact: Temporary service interruption; users unable to log in Estimated Users Impacted: Unknown; global authentication flow Actions: Jamf identified upstream authentication errors beginning at 2025-11-16 20:04 UTC. Services began recovering at 2025-11-16 20:14 UTC after stabilisation of the IDaaS provider. We are monitoring authentication performance as the provider continues their investigation. A support ticket remains open with the vendor for further detail. Workaround / Customer Actions: No customer action required at this time.
- resolved Nov 16, 2025, 09:01 PM UTC
Our IDaaS provider has taken the necessary remediation steps and we are now observing full recovery. We are continuing to monitor this issue, however all symptoms have resolved.