- Detected by Pingoru
- Jun 15, 2026, 01:32 PM UTC
- Resolved
- Jun 15, 2026, 05:02 PM UTC
- Duration
- 3h 30m
Affected: Region: eu-west-2: Jamf Insights StandardRegion: eu-west-2 Service Enabled
Timeline · 6 updates
-
investigating Jun 15, 2026, 01:32 PM UTC
Symptoms: Customers using the European cluster of Jamf Insights are experiencing a partial service degradation — device data is not updating and MDM commands are not functional. US region is unaffected. Customer Impact: Affected Services: Jamf Insights (EU cluster) — device data refresh, extension attribute visibility, MDM command delivery Affected Regions: European cluster only; US region verified healthy Business Impact: Service degradation — device management data is stale; MDM commands not executing through Insights Estimated Users Impacted: Up to ~5,500 EU tenants Workaround/Customer Actions: MSPs with direct Jamf Pro access can manage their customers via Jamf Pro until the fix is in place. All other customers — no additional action required at this time.
-
investigating Jun 15, 2026, 01:33 PM UTC
We are continuing to investigate this issue.
-
identified Jun 15, 2026, 02:18 PM UTC
We have identified the issue and are currently verifying the fix. Once the fix is confirmed effective, the team will continue working to fully restore the service.
-
monitoring Jun 15, 2026, 02:46 PM UTC
A fix has been applied and the service should now be restored. We are running verification and will continue to monitor the situation closely. We expect to know more within approximately one hour and will provide a further update then.
-
monitoring Jun 15, 2026, 04:19 PM UTC
We are continuing to run validation to confirm the service has been fully restored for all customers. We will provide a further update once this is complete.
-
resolved Jun 15, 2026, 05:02 PM UTC
The service interruption with Jamf Insights (EU) has been restored. An issue with the credential rotation process prevented Jamf Insights from authenticating to customers' Jamf Pro instances. We apologize for any inconvenience. We will publish an analysis of this incident once we have completed our internal investigation. Customer Impact: Up to 900 EU tenants were affected. During the interruption, affected customers were unable to issue MDM commands or refresh device data (including extension attributes) through Jamf Insights.
Read the full incident report →
- Detected by Pingoru
- May 18, 2026, 10:13 AM UTC
- Resolved
- May 18, 2026, 05:50 PM UTC
- Duration
- 7h 37m
Affected: eu-central-1: Jamf School
Timeline · 4 updates
-
investigating May 18, 2026, 10:13 AM UTC
We are currently investigating this issue.
-
identified May 18, 2026, 10:53 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring May 18, 2026, 02:45 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved May 18, 2026, 05:50 PM UTC
This issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 21, 2026, 02:15 AM UTC
- Resolved
- Apr 21, 2026, 03:03 AM UTC
- Duration
- 47m
Affected: Private Access
Timeline · 4 updates
-
investigating Apr 21, 2026, 02:15 AM UTC
Customers using Jamf Trust on macOS and iOS/iPadOS are experiencing connectivity failures. Devices are unable to establish a stable tunnel connection and are cycling between bypass mode and tunnel recovery. General internet access remains unaffected, but ZTNA and Private Access functionality is disrupted. Our engineering team is actively investigating the root cause. This is being treated as a critical incident and is our top priority. We appreciate your patience and are committed to resolving this as swiftly as possible.
-
identified Apr 21, 2026, 02:36 AM UTC
We have identified that VPN load balancer infrastructure in the APAC region (apse2) experienced an unexpected restart due to resource constraints. Infrastructure has been scaled up and services are being restored. No action is required from customers at this stage, and we will update here once connectivity is restored.
-
monitoring Apr 21, 2026, 02:45 AM UTC
Infrastructure has been successfully scaled up. Services are being monitored to confirm stability. No action is required from customers and Jamf Trust should reconnect automatically.
-
resolved Apr 21, 2026, 03:03 AM UTC
Full service has been restored, and we will conduct a post-incident review. We appreciate your patience and apologise for any disruption caused.
Read the full incident report →
- Detected by Pingoru
- Apr 06, 2026, 03:41 PM UTC
- Resolved
- Apr 07, 2026, 01:06 PM UTC
- Duration
- 21h 24m
Affected: us-west-2: Jamf Protect
Timeline · 5 updates
-
investigating Apr 06, 2026, 03:41 PM UTC
We are currently investigating this issue.
-
investigating Apr 06, 2026, 04:37 PM UTC
We are continuing to investigate this issue.
-
identified Apr 06, 2026, 05:51 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Apr 06, 2026, 08:04 PM UTC
A fix has been implemented and we are monitoring the results. Jamf Protect Console performance is restored. Alerting and Insights may continue to see some delays as the backlog processes.
-
resolved Apr 07, 2026, 01:06 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 02, 2026, 12:53 PM UTC
- Resolved
- Apr 02, 2026, 09:07 PM UTC
- Duration
- 8h 14m
Affected: eu-central-1: Jamf Schoolus-east-1: Jamf School
Timeline · 5 updates
-
identified Apr 02, 2026, 12:53 PM UTC
The issue has been identified and a fix is being implemented.
-
identified Apr 02, 2026, 01:03 PM UTC
We are continuing to work on a fix for this issue.
-
identified Apr 02, 2026, 01:56 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring Apr 02, 2026, 03:37 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 02, 2026, 09:07 PM UTC
Monitoring complete. No additional issues.
Read the full incident report →
- Detected by Pingoru
- Mar 26, 2026, 02:05 PM UTC
- Resolved
- Mar 26, 2026, 09:03 PM UTC
- Duration
- 6h 58m
Affected: ap-northeast-1: Jamf Pro - Premiumap-southeast-2: Jamf Pro - Premiumeu-central-1: Jamf Pro - Premiumeu-west-2: Jamf Pro - Premiumus-east-1: Jamf Pro - Premiumus-west-2: Jamf Pro - Premiumus-east-2: Jamf Pro - Premium
Timeline · 3 updates
-
identified Mar 26, 2026, 02:05 PM UTC
We are investigating an issue around Blueprints affecting customers running versions of Jamf Pro 11.24 and lower.
-
monitoring Mar 26, 2026, 03:00 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 26, 2026, 09:03 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 26, 2026, 01:42 PM UTC
- Resolved
- Mar 26, 2026, 03:52 PM UTC
- Duration
- 2h 9m
Affected: us-west-2: Jamf Pro - Standardus-west-2: Jamf Pro - Premiumus-east-2: Jamf Pro - Standardus-east-2: Jamf Pro - Premium
Timeline · 5 updates
-
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.
-
identified Mar 26, 2026, 01:44 PM UTC
The issue has been identified and a fix is being implemented.
-
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.
-
monitoring Mar 26, 2026, 03:29 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 26, 2026, 03:52 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 11, 2026, 03:45 PM UTC
- Resolved
- Mar 11, 2026, 07:46 PM UTC
- Duration
- 4h 1m
Affected: ap-northeast-1: Jamf Pro - Standardap-northeast-1: Jamf Schoolap-northeast-1: Jamf Pro - Premiumap-southeast-2: Jamf Pro - Standardeu-central-1: Jamf Schoolap-southeast-2: Jamf Pro - Premiumeu-central-1: Jamf Pro - Standardeu-central-1: Jamf Pro - Premiumus-east-1: Jamf Schooleu-west-2: Jamf Pro - Standardeu-west-2: Jamf Pro - Premium
Timeline · 4 updates
-
investigating Mar 11, 2026, 03:45 PM UTC
We are currently investigating this issue.
-
identified Mar 11, 2026, 04:06 PM UTC
The issue has been identified and a fix is being pursued.
-
monitoring Mar 11, 2026, 04:36 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 11, 2026, 07:46 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 09, 2026, 01:58 PM UTC
- Resolved
- Mar 09, 2026, 05:16 PM UTC
- Duration
- 3h 17m
Affected: us-west-2: Jamf Pro - Standard
Timeline · 5 updates
-
investigating Mar 09, 2026, 01:58 PM UTC
We are experiencing performance issues within the US West 2 Region. We are actively investigating this issue.
-
identified Mar 09, 2026, 03:17 PM UTC
The issue has been identified and we are working on resolution.
-
identified Mar 09, 2026, 04:21 PM UTC
We continue to work on a fix for this issue.
-
monitoring Mar 09, 2026, 04:39 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 09, 2026, 05:16 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 07, 2026, 06:39 PM UTC
- Resolved
- Mar 09, 2026, 01:32 PM UTC
- Duration
- 1d 18h
Affected: ap-northeast-1: Jamf Pro - Standardap-southeast-2: Jamf Pro - Standardeu-central-1: Jamf Pro - Standardeu-west-2: Jamf Pro - Standardus-east-1: Jamf Pro - Standardus-west-2: Jamf Pro - Standardus-east-2: Jamf Pro - Standard
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Feb 23, 2026, 06:55 AM UTC
- Resolved
- Feb 23, 2026, 11:01 AM UTC
- Duration
- 4h 5m
Affected: ap-northeast-1: Jamf Schooleu-central-1: Jamf Schoolus-east-1: Jamf School
Timeline · 3 updates
-
identified Feb 23, 2026, 06:55 AM UTC
We are currently experiencing an issue with our emailing service that is preventing outbound emails from being delivered. Our team is actively investigating and working to restore full functionality as soon as possible. We apologize for any inconvenience this may cause and will provide an update once the issue is resolved.
-
monitoring Feb 23, 2026, 10:37 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 23, 2026, 11:01 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 03, 2026, 10:21 PM UTC
- Resolved
- Feb 04, 2026, 04:21 PM UTC
- Duration
- 17h 59m
Affected: Threat Defense
Timeline · 2 updates
-
monitoring Feb 03, 2026, 10:21 PM UTC
Actions: A fix has been applied for notifications of App Store app flagging as sideloaded. Customer Action Required: UEM Synchronization To remediate the side-loaded app events identified during this incident, please perform a UEM sync between Jamf Security Cloud and your MDM solution. This sync will also update device risk state used by Access policies. To synchronize: Navigate to Jamf Security Cloud > Integrations > UEM Connection > Settings > Actions > Synchronize If you have questions or need assistance, please contact Jamf Support. We apologize for any inconvenience.
-
resolved Feb 04, 2026, 04:21 PM UTC
This incident has been resolved. Actions: A fix has been applied for notifications of App Store app flagging as sideloaded. Customer Action Required: UEM Synchronization To remediate the side-loaded app events identified during this incident, please perform a UEM sync between Jamf Security Cloud and your MDM solution. This sync will also update device risk state used by Access policies. To synchronize: Navigate to Jamf Security Cloud > Integrations > UEM Connection > Settings > Actions > Synchronize If a UEM sync was previously performed and alerts still persist, please perform a full sync again. The issue has now been fully resolved and syncing will remediate the false positive events. Alternatively, you can manually archive the specific threat in Radar > Threats view. To synchronize: Navigate to Jamf Security Cloud > Integrations > UEM Connection > Settings > Actions > Synchronize If you have questions or need assistance, please contact Jamf Support.
Read the full incident report →
- Detected by Pingoru
- Feb 01, 2026, 09:39 PM UTC
- Resolved
- Feb 03, 2026, 08:04 PM UTC
- Duration
- 1d 22h
Affected: Threat DefenseData Policy
Timeline · 4 updates
-
monitoring Feb 01, 2026, 09:39 PM UTC
Devices running iOS/iPadOS 26.1 with On-Device Content Filtering enabled may experience loss of network connectivity if Jamf Trust is updated to version 11.47.0 or later while on an unstable network. In some cases, the update may hang and require a factory reset to recover. This issue affects any app implementing the On-Device Content Filtering extension on iOS and is not specific to Jamf Trust. Recommended action: Update devices to iOS/iPadOS 26.2 before updating Jamf Trust. Apple resolved the underlying issue in 26.2. If this is not yet possible, ensure devices are on a stable network during updates. No service disruption is currently ongoing. Jamf Nation Post: https://community.jamf.com/general-discussions-2/jamf-trust-app-updates-on-ios-ipados-26-1-connectivity-issue-57586
-
monitoring Feb 03, 2026, 05:55 PM UTC
Apple resolved the underlying issue in 26.2. Customers are advised to update devices to iOS/iPadOS 26.2 before updating Jamf Trust. If this is not yet possible, ensure devices are on a stable network during updates.
-
monitoring Feb 03, 2026, 05:59 PM UTC
We are continuing to monitor for any further issues.
-
resolved Feb 03, 2026, 08:04 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 06, 2026, 05:59 PM UTC
- Resolved
- Jan 06, 2026, 06:26 PM UTC
- Duration
- 26m
Affected: Reporting
Timeline · 2 updates
-
investigating Jan 06, 2026, 05:59 PM UTC
We are currently experiencing degraded data loading in Jamf Security Cloud Console. Some pages and widgets may not load properly. As a temporary workaround, refreshing the page may resolve loading issues in some cases. Our team is actively investigating the root cause and will provide updates as more information becomes available.
-
resolved Jan 06, 2026, 06:26 PM UTC
The engineering team has investigated the issue, identified the root cause, and implemented a fix. The degradation should now be resolved and all systems should be fully operational.
Read the full incident report →
- Detected by Pingoru
- Dec 10, 2025, 01:53 AM UTC
- Resolved
- Dec 10, 2025, 03:37 AM UTC
- Duration
- 1h 43m
Affected: Threat DefenseData Policy
Timeline · 3 updates
-
investigating Dec 10, 2025, 01:53 AM UTC
Date/Time: 2025-12-10 01:30 UTC We are investigating increased latency in SecureDNS policy evaluation for Jamf Security Cloud and Jamf Safe Internet in the APAC region. Customers may experience intermittent delays in DNS resolution. Customer Impact: Partial service degradation; browsing or connectivity may be slower for affected users. Affected Services: SecureDNS (Jamf Security Cloud / Jamf Safe Internet) Affected Regions: APAC (ap-northeast-1) Jamf Engineering is investigating and monitoring performance. Updates to follow. No customer action required at this time.
-
monitoring Dec 10, 2025, 03:20 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Dec 10, 2025, 03:37 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 08, 2025, 12:14 PM UTC
- Resolved
- Dec 09, 2025, 03:24 PM UTC
- Duration
- 1d 3h
Affected: CDN
Timeline · 3 updates
-
investigating Dec 08, 2025, 12:14 PM UTC
We have been notified of an intermittent issue affecting retrieving the JWT for Jamf Auto Update. This is currently under investigation.
-
monitoring Dec 08, 2025, 03:00 PM UTC
The issue has been identified, and a fix has been rolled out. We will keep monitoring.
-
resolved Dec 09, 2025, 03:24 PM UTC
Actions: The intermittent outage with Jamf Auto Update has been restored. .Scaling issues identified during the course of that interruption were identified and remediated. We apologize for any inconvenience. We will publish an analysis of this incident once we have completed our internal investigation. Customer Impact: There should be no ongoing impact.
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 04:09 PM UTC
- Resolved
- Nov 18, 2025, 04:36 PM UTC
- Duration
- 27m
Affected: ap-northeast-1: Jamf Protectap-southeast-2: Jamf Protecteu-central-1: Jamf Protecteu-west-2: Jamf Protectus-east-1: Jamf Protectus-west-2: Jamf Protect
Timeline · 4 updates
-
investigating Nov 18, 2025, 04:09 PM UTC
Some customers are experiencing an inability to authenticate via OIDC when accessing the Jamf Protect Admin Console with Jamf ID or their IdP configured in Jamf Account, due to an upstream issue with our IDaaS provider.
-
monitoring Nov 18, 2025, 04:31 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.
-
monitoring Nov 18, 2025, 04:33 PM UTC
We are continuing to monitor for any further issues.
-
resolved Nov 18, 2025, 04:36 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 16, 2025, 08:53 PM UTC
- Resolved
- Nov 16, 2025, 09:01 PM UTC
- Duration
- 8m
Affected: Jamf AccountJamf ID
Timeline · 2 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Nov 05, 2025, 11:25 PM UTC
- Resolved
- Nov 06, 2025, 02:25 PM UTC
- Duration
- 14h 59m
Timeline · 7 updates
Read the full incident report →
- Detected by Pingoru
- Nov 04, 2025, 09:03 AM UTC
- Resolved
- Nov 04, 2025, 09:35 AM UTC
- Duration
- 31m
Affected: eu-central-1: Jamf School
Timeline · 4 updates
-
investigating Nov 04, 2025, 09:03 AM UTC
We are currently investigating this issue.
-
identified Nov 04, 2025, 09:16 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Nov 04, 2025, 09:29 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Nov 04, 2025, 09:35 AM UTC
This incident has been resolved.
Read the full incident report →
Critical October 20, 2025 - Detected by Pingoru
- Oct 20, 2025, 09:47 AM UTC
- Resolved
- Oct 20, 2025, 09:42 PM UTC
- Duration
- 11h 55m
Affected: us-east-1: Jamf Protect
Timeline · 15 updates
Read the full incident report →
- Detected by Pingoru
- Oct 14, 2025, 08:24 PM UTC
- Resolved
- Oct 15, 2025, 09:51 AM UTC
- Duration
- 13h 26m
Affected: us-east-1: Jamf School
Timeline · 6 updates
-
investigating Oct 14, 2025, 08:24 PM UTC
We are currently investigating this issue.
-
identified Oct 14, 2025, 08:28 PM UTC
We have identified the issue, and are working on a solution. Impacted areas are performance of the Admin UI and API.
-
identified Oct 14, 2025, 09:30 PM UTC
We are continuing to investigate this issue. Impact remains unchanged.
-
identified Oct 14, 2025, 10:19 PM UTC
We are continuing to investigate the root cause of this issue. Performance has stabilized. We will update again tomorrow.
-
monitoring Oct 15, 2025, 08:15 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Oct 15, 2025, 09:51 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 10, 2025, 01:17 PM UTC
- Resolved
- Oct 10, 2025, 01:54 PM UTC
- Duration
- 37m
Affected: Data Policy
Timeline · 4 updates
-
investigating Oct 10, 2025, 01:17 PM UTC
We are currently investigating this issue.
-
identified Oct 10, 2025, 01:17 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Oct 10, 2025, 01:28 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Oct 10, 2025, 01:54 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 02, 2025, 06:19 PM UTC
- Resolved
- Sep 19, 2025, 10:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Oct 02, 2025, 06:19 PM UTC
Between Wed, Sept 10, 22:05 UTC and Fri, Sept 19, 22:05 UTC, customers may have experienced unreported service degradation for Jamf Protect's reporting and forwarding capabilities via JamfCloud. The impacts to the degraded service were not fully understood until now. We're improving monitoring to better detect and surface hidden impacts going forward. During this time window, affected customers may have experienced a lower volume of reported events and telemetry. On-device protections including Threat Prevention, Advanced Threat Controls, Device Controls, and Tamper Prevention remained effective during this time. The underlying issue was resolved, and the service has been stable since Fri, Sept 19, 22:05 UTC.
Read the full incident report →
- Detected by Pingoru
- Oct 02, 2025, 04:14 AM UTC
- Resolved
- Oct 02, 2025, 05:28 AM UTC
- Duration
- 1h 13m
Affected: Threat DefenseData Policy
Timeline · 2 updates
-
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.
Read the full incident report →
