Jamf incident
Degraded Performance – DNS Requests and Device Enrollments in Tokyo Region
Resolved after 1 hour 13 minutes, affecting Threat Defense and Data Policy, on October 2, 2025.
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.
Affected components
Update timeline
- 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.
- 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.
Your product runs on more than Jamf
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services