NinjaOne experienced a minor incident on July 16, 2026 affecting Europe (EU) and Australia (OC) and 1 more component, lasting 13d 8h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 16, 2026, 05:16 PM UTC
Some customers may experience automations, scripts, and scheduled tasks remaining in a queued state and not executing. Affected devices will otherwise appear online and healthy. We have identified the cause and a fix is in progress. Further updates will follow as deployment timing is confirmed.
- investigating Jul 16, 2026, 05:17 PM UTC
We are continuing to investigate this issue.
- investigating Jul 16, 2026, 05:18 PM UTC
We are continuing to investigate this issue.
- investigating Jul 16, 2026, 05:19 PM UTC
We are continuing to investigate this issue.
- investigating Jul 16, 2026, 06:17 PM UTC
We are continuing to investigate this issue.
- identified Jul 16, 2026, 08:19 PM UTC
We have identified that the issue is only affecting NMS delegates. To identify NMS delegates navigate to the Devices page, select the More Filters button in the top bar and select NMS Delegate.
- identified Jul 16, 2026, 10:34 PM UTC
We are preparing to deploy a targeted hotfix for the customers who are currently affected by this issue in our EU region. There will be a brief disruption of API and Web portal access for a subset of customers while we push the change.
- identified Jul 16, 2026, 11:49 PM UTC
We have successfully deployed the hotfix to the affected customers in EU. We are validating the fix is working as expected.
- identified Jul 17, 2026, 12:10 AM UTC
Our testing indicates the issue is remediated within EU. We are assessing the scope of customers affected in our other regions so we can hotfix as necessary to minimize impact to all customers. More updates to come as we progress through those remediation steps.
- identified Jul 17, 2026, 09:51 PM UTC
The issue causing automations, scripts, and scheduled tasks to remain queued on NMS delegates has been resolved for affected customers in the EU region following a successful targeted hotfix, which we have confirmed through testing. To fully address this across all regions, we will be rolling out the same fix via scheduled maintenance plans next week. Each affected region will receive advance notice of its specific maintenance window through this status page. No action is required from customers in the meantime. We appreciate your patience and apologize for any disruption this may have caused.
- resolved Jul 30, 2026, 01:58 AM UTC
This incident has been resolved.
- postmortem Aug 12, 2026, 05:51 PM UTC
Following our v14 release, we identified an issue that prevented some devices from processing triggered actions. The impact was limited to devices set up as NMS \(Network Management System\) delegates, which represent fewer than 1% of devices in any environment. A change introduced in v14 related to our NMS functionality caused triggered actions for those devices to be routed incorrectly and not processed. To provide immediate relief, we deployed a targeted fix to the most affected customers, confirmed it restored normal processing, and then rolled the fix out across all affected regions to fully resolve the issue. We are taking action to prevent this same issue from occurring in the future.