Jamf incident

Degraded Performance – DNS Requests and Device Enrollments in Tokyo Region

Minor Resolved View vendor source →

Jamf experienced a minor incident on October 2, 2025 affecting Threat Defense and Data Policy, lasting 1h 13m. The incident has been resolved; the full update timeline is below.

Started
Oct 02, 2025, 04:14 AM UTC
Resolved
Oct 02, 2025, 05:28 AM UTC
Duration
1h 13m
Detected by Pingoru
Oct 02, 2025, 04:14 AM UTC

Affected components

Threat DefenseData Policy

Update timeline

  1. investigating Oct 02, 2025, 04:14 AM UTC

    We are currently investigating increased latency affecting DNS requests in the ap-northeast-1 (Tokyo) region. All other JSC regions are operating normally. Our Secure Connectivity engineering team is actively working on the issue, but we do not have an estimated time for resolution at this stage.

  2. resolved Oct 02, 2025, 05:28 AM UTC

    The earlier issue causing increased latency for DNS requests in the ap-northeast-1 (Tokyo) region has been resolved. Performance has returned to normal and all services are operating as expected. We will continue to monitor closely. Thank you for your patience.