NinjaOne had 49 outages in the last 2 years totaling 439h 40m of downtime — averaging 2 incidents per month.
There were 49 NinjaOne outages since July 22, 2025 totaling 439h 40m of downtime. Each is summarised below — incident details, duration, and resolution information.
We will be undergoing scheduled maintenance.
We are continuing to investigate this issue.
We will be undergoing scheduled maintenance.
We are currently experiencing a delay in processing of scheduled tasks for multiple products. We are investigating and will update as soon as we have more information.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating reports of degraded performance affecting some users in the EU region. Other regions may experience intermittent impact. Our team is actively working on a resolution. We will provide updates as more information becomes available.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are aware of and investigating reports of customers experiencing dashboard-wide errors and slowness, primarily affecting the backup module (backup loading errors, missing backup tab, "error fetching bucket lists") and vulnerability reporting (blank vulnerability details showing only total devices impacted).
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating this issue.
We have identified the issue and are verifying the fix.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating reports of RDP connections failing for customers on the EU instance. Users may be unable to establish RDP sessions via NinjaOne.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We’re currently investigating problems with scheduled reports.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue with Apple Push Notifications.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue with locations not populating for some organizations in the agent installer generator pop-up in the NinjaOne web console.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are aware of an issue accessing the NinjaOne user portal for a period of about 10 minutes from approximately 19:30 to 19:40 UTC today. We are investigating these reports. All services are fully operational at this time.
We are continuing to investigate this issue. All services continue to be fully operational at this time.
This incident has been resolved.
At 19:31 UTC on Monday, May 18, 2026, we experienced a container lifecycle event that led to a brief performance impact of around 10 minutes where the user portal was inaccessible.
We are currently investigating this issue.
No identified disruptions; the previously reported connectivity issues appear isolated to local internet routing in specific localities.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
NinjaOne has identified a service issue that may affect customer performance with the Apple MDM product. We are currently investigating and will provide regular status updates. Any customers having issues with the Ninja Application can contact Support for assistance at [email protected]. Thank you for your patience.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
NinjaOne has identified a service issue that may affect customer performance. We are currently investigating and will provide regular status updates. Any customers having issues with the Ninja Application can contact Support for assistance at [email protected]. Thank you for your patience.
This incident has been resolved.
Known issue with the devices-detailed Public API endpoint now requiring pagination. We are working on rolling back this change. Until it is fixed customers can access all devices using the pageSize and after query parameters.
We expect to have a hotfix ready and deployed within the next two hours. This will result in a brief disruption of the API while we apply the hotfix, but it is expected to be brief
A hotfix has been deployed and we are currently validating the change.
We are continuing to monitor for any further issues.
This incident has been resolved.
EU - Agents reporting Offline
A fix has been implemented and we are monitoring the results.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
NinjaOne is aware of service issues affecting web portal login. We are continuing our investigation and will provide regular status updates. Please contact Support for additional assistance at [email protected].
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
We are continuing to monitor for any further issues.
This incident has been resolved.
NinjaOne has identified a service issue that may affect customer performance in the following areas of the portal: - Apps - MDM Apple - Permission - MDM connections - Device Dashboard - Overview tab (loading APN info for Apple devices) We are currently investigating and will provide regular status updates. Any customers having issues with the Ninja Application can contact Support for assistance at [email protected].
We are continuing to investigate the issue. We are updating the scope to note we are seeing similar behavior in the US2 region as well.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Some clients are experiencing Intermittent issues with establishing NinjaRemote connections due to their Agent Offline status. We are investigating the cause of this issue and wil report back soon.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating issues with branded domains in OC
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
The current issue is only affecting the branded domains. As an alternative, the non-branded domain of oc.ninjarmm.com remains fully operational and can be accessed by all customers, regardless of branding usage. We are continuing to work on restoring service.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Service Issue - Response Time High - Degraded Performance
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.