Jamf incident

On-device Content Controls Experiencing Degraded Performance

Minor Resolved View vendor source →

Jamf experienced a minor incident on April 1, 2025 affecting Data Policy, lasting 6h 45m. The incident has been resolved; the full update timeline is below.

Started
Apr 01, 2025, 07:32 AM UTC
Resolved
Apr 01, 2025, 02:17 PM UTC
Duration
6h 45m
Detected by Pingoru
Apr 01, 2025, 07:32 AM UTC

Affected components

Data Policy

Update timeline

  1. investigating Apr 01, 2025, 07:32 AM UTC

    Since 1:00 AM UTC, we have been experiencing issues with content filtering policies in Jamf Security Cloud. This may affect: - iOS on-device content filtering - Windows content filtering - Content filtering policy pages in the Jamf Security Cloud console We are investigating the issue.

  2. investigating Apr 01, 2025, 08:29 AM UTC

    Our technical teams are actively investigating the root cause and working to resolve these content filtering policy issues. We will provide another update as soon as more information becomes available.

  3. identified Apr 01, 2025, 09:26 AM UTC

    The issue causing degraded performance has been identified, and technical teams are working on implementing the fix. We will publish the next update in an hour.

  4. monitoring Apr 01, 2025, 10:56 AM UTC

    The content filtering policy issues have been resolved, and all systems function normally. We are actively monitoring the service. There might still be some temporary impact regarding data capping as our systems process the backlog of events. These discrepancies will resolve automatically within the next few hours.

  5. resolved Apr 01, 2025, 02:17 PM UTC

    All systems are operational now.