Is NinjaOne down?
Last checked 7m agoNo incidents right now.
NinjaOne is operational right now. Last checked 7m ago; the most recent incident resolved 1h ago.
Real-time NinjaOne status, recent outages, and incident history — pulled directly from NinjaOne's official status page at https://status.ninjaone.com every 5 minutes. Pingoru tracks 7 NinjaOne services and has captured 88 incidents in the last 90 days (95.40% uptime). Get email, Slack, Discord, or webhook alerts the moment NinjaOne reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- United States (US)Europe (EU)Australia (OC)Canada (CA)United States (US2)Japan (JP)
Timeline · 6 updates
- investigating · Jul 30, 2026, 03:26 PM UTC
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.
- identified · Jul 30, 2026, 04:46 PM UTC
The issue has been identified and a fix is being implemented.
- identified · Jul 30, 2026, 05:45 PM UTC
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.
- monitoring · Jul 30, 2026, 08:59 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring · Jul 30, 2026, 09:36 PM UTC
We are continuing to monitor for any further issues.
- resolved · Jul 30, 2026, 10:14 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- United States (US)
Timeline · 8 updates
- investigating · Jul 24, 2026, 11:38 AM UTC
We are currently investigating this issue.
- identified · Jul 24, 2026, 12:10 PM UTC
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.
- monitoring · Jul 24, 2026, 01:08 PM UTC
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.
- monitoring · Jul 24, 2026, 02:54 PM UTC
We are continuing to monitor for any further issues.
- monitoring · Jul 24, 2026, 03:38 PM UTC
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
- monitoring · Jul 24, 2026, 06:21 PM UTC
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.
- monitoring · Jul 24, 2026, 08:10 PM UTC
Mitigation efforts have shown positive results and we are seeing agents reporting status correctly at this time. We are continuing to monitor the incident.
- resolved · Jul 24, 2026, 09:28 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Europe (EU)United States (US2)
Timeline · 4 updates
- investigating · Jul 22, 2026, 07:03 PM UTC
We are aware of intermittent issues with connecting to devices via Ninja Remote. We are currently investigating this issue
- investigating · Jul 22, 2026, 07:59 PM UTC
We have noted that this behavior is also seen in the US2 region. We are continuing to investigate the issue.
- monitoring · Jul 22, 2026, 09:00 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved · Jul 22, 2026, 09:31 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Europe (EU)Australia (OC)Canada (CA)United States (US2)Japan (JP)
Timeline · 11 updates
- 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.
Latest: This incident has been resolved.
-
- United States (US2)
Timeline · 3 updates
- investigating · Jul 14, 2026, 02:25 PM UTC
We will be undergoing scheduled maintenance.
- investigating · Jul 14, 2026, 02:28 PM UTC
We are continuing to investigate this issue.
- investigating · Jul 14, 2026, 02:29 PM UTC
We will be undergoing scheduled maintenance.
Latest: We will be undergoing scheduled maintenance.
-
See the full NinjaOne outage history
11 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse NinjaOne outage history →Or sign up free to get alerts when NinjaOne breaks · 10 free monitors · No credit card
- Dashboard - New Tenant UI Errors ResolvedStarted Jul 30, 2026, 03:26 PM UTC · Resolved Jul 30, 2026, 10:14 PM UTC · 6h 48m
- US - Service Availability Issue ResolvedStarted Jul 24, 2026, 11:38 AM UTC · Resolved Jul 24, 2026, 09:28 PM UTC · 9h 49m
- Started Jul 22, 2026, 07:03 PM UTC · Resolved Jul 22, 2026, 09:31 PM UTC · 2h 27m
- Automations and Scripting — Degraded ResolvedStarted Jul 16, 2026, 05:16 PM UTC · Resolved Jul 30, 2026, 01:58 AM UTC · 13d 8h
- Release US2 - 14.1.0 ResolvedStarted Jul 14, 2026, 02:25 PM UTC · Resolved Jul 14, 2026, 02:59 PM UTC · 33m
- Started Jul 13, 2026, 09:23 AM UTC · Resolved Jul 15, 2026, 05:05 PM UTC · 2d 7h
- Started Jul 10, 2026, 05:56 AM UTC · Resolved Jul 10, 2026, 09:08 AM UTC · 3h 11m
- Started Jul 09, 2026, 05:37 PM UTC · Resolved Jul 09, 2026, 09:31 PM UTC · 3h 54m