NinjaOne had 55 outages in the last 2 years totaling 458h 34m of downtime — averaging 2.3 incidents per month.
There were 55 NinjaOne outages since October 6, 2025 totaling 458h 34m of downtime. Each is summarised below — incident details, duration, and resolution information.
A fix has been implemented and we are monitoring results.
We have confirmed the issue has been resolved. Thank you for your patience during the process.
Our team has identified an issue sending SMS messages to Austrian phone numbers. We are working with our third-party SMS service provider to resolve the issue. We appreciate your patience and will provide further updates as the situation progresses.
Our team have identified the issue with our third party provider, we have a remediation, and we are contacting customers who have been affected.
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.
Our team has identified an issue affecting the availability of PDF generation capabilities for some users. We are actively working to implement a fix and restore full functionality as quickly as possible. We appreciate your patience and will provide further updates as the situation progresses.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're investigating an issue in the EU environment where devices found during a Network Discovery scan aren't appearing under Devices > Discovered, despite the scan completing successfully.
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 investigating an issue affecting the creation and renewal of Apple APNs certificates in the EU region. Existing certificate functionality may remain available, but customers with expired or expiring certificates may be impacted. Our engineering team is investigating
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 is aware of an issue impacting device monitoring data, where some customers may see missing device metrics within the dashboard. We are actively investigating and working to restore normal service.
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 where some endpoints are incorrectly reporting as "Offline" within the NinjaOne dashboard
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 experiencing issues with outgoing emails from the ticketing portion of our platform in CA. We're working to correct the issue.
This issue has been identified and resolved. The impacted service is now operational.
We're experiencing an elevated level of remote tool connection errors in OC and are currently looking into the issue.
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 have identified an issue preventing customers from submitting support tickets through the NinjaOne Console Helpcenter. Customers can continue submitting support requests through DOJO or by emailing [email protected]. We have applied a mitigation and are monitoring recovery.
A fix has been implemented and we are monitoring the results.
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 investigating an issue where users may see error messages when accessing certain areas of the NinjaOne web interface in newly created tenants. This issue does not impact product functionality, but may result in unexpected error notifications being displayed. Our engineering teams are actively investigating.
The issue has been identified and a fix is being implemented.
Our team has confirmed the issue is limited to the user interface and does not impact any underlying platform functionality or service availability. A fix has been identified and our team is deploying an update to all regions today at 15:00 CDT / 20:00 UTC to resolve the 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 this issue.
We have identified a broader connectivity issue within our cloud provider's infrastructure that is causing intermittent service disruptions for some customers, and we are actively monitoring recovery efforts.
We have identified a broader connectivity issue within our cloud provider's infrastructure that is causing intermittent service disruptions for some customers. Recovery efforts are ongoing and service stability has improved, though some impact may persist while restoration work continues.
We are continuing to monitor for any further issues.
During the AWS Outage, Ninja Agents attempted and failed to reconnect to our backend services. This automatically triggers a backoff/retry mechanism in our agents that is designed to prevent traffic flooding or thundering herd behavior during significant outages. Agents are slowly reconnecting, but will randomize their reconnection attempts until successful. Additionally the service that was responsible for processing device status was struggling with the volume of agent status changes. We have scaled that capacity out and are seeing healthy metrics. Over the last hour we have seen our connected devices increase by over 150k devices, but recovery will likely be slow while the agents attempt to gracefully reestablish service
To help mitigate some agents still showing offline we are restarting our frontend web systems. Some users may see a slight increase in response time during this process.
Mitigation efforts have shown positive results and we are seeing agents reporting status correctly at this time. We are continuing to monitor the incident.
This incident has been resolved.
We are aware of intermittent issues with connecting to devices via Ninja Remote. We are currently investigating this issue
We have noted that this behavior is also seen in the US2 region. We are continuing to investigate the issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We will be undergoing scheduled maintenance.
We are continuing to investigate this issue.
We will be undergoing scheduled maintenance.
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.