NinjaOne Outage History

NinjaOne is up right now

There were 14 NinjaOne outages since February 5, 2026 totaling 412h 8m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.ninjaone.com

Minor May 1, 2026

Investigating intermittent UI issues

Detected by Pingoru
May 01, 2026, 03:53 PM UTC
Resolved
May 01, 2026, 05:43 PM UTC
Duration
1h 50m
Affected: Federal (Moderate)
Timeline · 5 updates
  1. investigating May 01, 2026, 03:53 PM UTC

    We are currently investigating this issue.

  2. identified May 01, 2026, 04:28 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring May 01, 2026, 04:28 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring May 01, 2026, 05:34 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved May 01, 2026, 05:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 29, 2026

US2 - MDM Service - Performance Degraded

Detected by Pingoru
Apr 29, 2026, 09:21 PM UTC
Resolved
Apr 29, 2026, 09:45 PM UTC
Duration
24m
Affected: United States (US2)
Timeline · 4 updates
  1. investigating Apr 29, 2026, 09:21 PM UTC

    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.

  2. identified Apr 29, 2026, 09:25 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Apr 29, 2026, 09:27 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Apr 29, 2026, 09:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 16, 2026

Service Issue - Performance Degraded

Detected by Pingoru
Apr 16, 2026, 02:17 PM UTC
Resolved
Apr 16, 2026, 05:28 PM UTC
Duration
3h 11m
Affected: United States (US)Europe (EU)Australia (OC)Canada (CA)
Timeline · 2 updates
  1. investigating Apr 16, 2026, 02:17 PM UTC

    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.

  2. resolved Apr 16, 2026, 05:28 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 16, 2026

Public API endpoint issue: devices-detailed

Detected by Pingoru
Apr 16, 2026, 12:35 PM UTC
Resolved
Apr 16, 2026, 08:27 PM UTC
Duration
7h 52m
Affected: Europe (EU)Australia (OC)Canada (CA)United States (US2)
Timeline · 5 updates
  1. investigating Apr 16, 2026, 12:35 PM UTC

    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.

  2. identified Apr 16, 2026, 03:23 PM UTC

    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

  3. monitoring Apr 16, 2026, 04:42 PM UTC

    A hotfix has been deployed and we are currently validating the change.

  4. monitoring Apr 16, 2026, 06:14 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Apr 16, 2026, 08:27 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 8, 2026

EU - Agents reporting Offline

Detected by Pingoru
Apr 08, 2026, 09:21 AM UTC
Resolved
Apr 08, 2026, 10:38 AM UTC
Duration
1h 16m
Affected: Europe (EU)
Timeline · 5 updates
  1. investigating Apr 08, 2026, 09:21 AM UTC

    EU - Agents reporting Offline

  2. identified Apr 08, 2026, 09:52 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring Apr 08, 2026, 09:52 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Apr 08, 2026, 09:53 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Apr 08, 2026, 10:38 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 1, 2026

CA - Web Portal Login Issues

Detected by Pingoru
Apr 01, 2026, 08:45 AM UTC
Resolved
Apr 01, 2026, 04:35 PM UTC
Duration
7h 49m
Affected: Canada (CA)
Timeline · 7 updates
  1. investigating Apr 01, 2026, 08:45 AM UTC

    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].

  2. investigating Apr 01, 2026, 09:22 AM UTC

    We are continuing to investigate this issue.

  3. identified Apr 01, 2026, 09:41 AM UTC

    The issue has been identified and a fix is being implemented.

  4. monitoring Apr 01, 2026, 10:07 AM UTC

    A fix has been implemented and we are monitoring the results.

  5. monitoring Apr 01, 2026, 11:52 AM UTC

    We are continuing to monitor for any further issues.

  6. monitoring Apr 01, 2026, 02:19 PM UTC

    We are continuing to monitor for any further issues.

  7. resolved Apr 01, 2026, 04:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 12, 2026

NinjaOne Remote Degradation

Detected by Pingoru
Mar 12, 2026, 12:08 PM UTC
Resolved
Mar 16, 2026, 04:03 PM UTC
Duration
4d 3h
Affected: Europe (EU)
Timeline · 12 updates
  1. investigating Mar 12, 2026, 12:08 PM UTC

    NinjaOne has identified a service issue that may affect customer performance in the following areas of the portal: - NinjaOne Remote We are continuing our investigation and will provide regular status updates. Please contact Support for additional assistance at [email protected].

  2. investigating Mar 12, 2026, 01:43 PM UTC

    We are continuing to investigate this issue.

  3. identified Mar 12, 2026, 03:44 PM UTC

    The issue has been identified and a fix is being implemented.

  4. identified Mar 12, 2026, 05:26 PM UTC

    We are continuing to work on a fix for this issue.

  5. identified Mar 12, 2026, 08:25 PM UTC

    We are continuing to work on a fix for this issue.

  6. identified Mar 12, 2026, 09:28 PM UTC

    We are continuing to work on a fix for this issue.

  7. identified Mar 12, 2026, 10:26 PM UTC

    We are continuing to work on a fix for this issue.

  8. monitoring Mar 12, 2026, 10:31 PM UTC

    A fix has been implemented and we are monitoring the results.

  9. monitoring Mar 13, 2026, 08:46 AM UTC

    We are continuing to monitor for any further issues.

  10. monitoring Mar 13, 2026, 10:03 AM UTC

    We are continuing to monitor for any further issues.

  11. monitoring Mar 13, 2026, 10:16 AM UTC

    We are continuing to monitor for any further issues.

  12. resolved Mar 16, 2026, 04:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 11, 2026

Portal service degradation for Apple MDM devices

Detected by Pingoru
Mar 11, 2026, 02:50 PM UTC
Resolved
Mar 11, 2026, 03:53 PM UTC
Duration
1h 3m
Affected: Canada (CA)United States (US2)
Timeline · 5 updates
  1. investigating Mar 11, 2026, 02:50 PM UTC

    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].

  2. investigating Mar 11, 2026, 03:10 PM UTC

    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.

  3. identified Mar 11, 2026, 03:16 PM UTC

    The issue has been identified and a fix is being implemented.

  4. monitoring Mar 11, 2026, 03:25 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Mar 11, 2026, 03:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 2, 2026

EU - Performance Degraded

Detected by Pingoru
Mar 02, 2026, 08:08 AM UTC
Resolved
Mar 09, 2026, 03:25 PM UTC
Duration
7d 7h
Affected: United States (US)Europe (EU)Australia (OC)Canada (CA)
Timeline · 15 updates
  1. investigating Mar 02, 2026, 08:08 AM UTC

    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.

  2. investigating Mar 02, 2026, 09:10 AM UTC

    We are continuing to investigate this issue.

  3. investigating Mar 02, 2026, 10:35 AM UTC

    We are seeing Ninja Remote metrics indicate the service is returning to a healthy state, however we are continuing to experience page load timeouts and intermittent delays in the UI. We are working on stabilizing these components currently.

  4. investigating Mar 02, 2026, 11:56 AM UTC

    We have temporarily disabled Full Text Search in our Ticketing service. We don't believe this to be root cause, but is contributing to increased load on the database. We plan to re-enable after we continuing working to mitigate the broader stability issues.

  5. investigating Mar 02, 2026, 07:55 PM UTC

    In response to the evolving situation, we are performing maintenance on our database backend systems that support our Agent Reporting Services. As we perform that maintenance, Agents will be disconnected for approximately 10 mins and will automatically reconnect at the end of the maintenance. As a reminder, your data is locally saved during this time and all data will be sent once your connection is reestablished. These changes are one part of overall improvements we are making to address the current stability issues in the region. Thank you for your continued patience. We will update you again soon.

  6. investigating Mar 02, 2026, 09:18 PM UTC

    The Maintenance is still in progress. We will send continued updates on progress and upon completion. Thank you.

  7. investigating Mar 02, 2026, 10:07 PM UTC

    We are continuing the final phases and validating the changes made with this maintenance. We will continue to provide updates accordingly. Thank you.

  8. investigating Mar 03, 2026, 12:02 AM UTC

    We are currently verifying the results of this maintenance. We continue to monitor the situation in the region accordingly. thank you.

  9. monitoring Mar 03, 2026, 02:42 AM UTC

    We've completed maintenance and will continue to monitor. Thank you for your patience.

  10. monitoring Mar 03, 2026, 07:00 AM UTC

    NinjaOne is aware that service issues continue to affect customer performance. We are continuing our investigation and will provide regular status updates. Please contact Support for additional assistance at [email protected]

  11. monitoring Mar 04, 2026, 08:05 PM UTC

    We will be performing maintenance in this region to bring online additional capacity for our Agent services. As part of this work, we need to restart all Agent endpoints at the conclusion of the maintenance. Ninja Agents will disconnect and reconnect automatically during this restart, and any data local agent collected during the disruption will be stored locally and resent when the agent reconnects to our servers. We will continue to provide updates accordingly. Thank You

  12. monitoring Mar 04, 2026, 10:56 PM UTC

    We've completed maintenance and will continue to monitor. Thank you for your patience.

  13. monitoring Mar 04, 2026, 10:56 PM UTC

    NinjaOne is aware that service issues continue to affect customer performance. We are continuing our investigation and will provide regular status updates. Please contact Support for additional assistance at [email protected]

  14. resolved Mar 09, 2026, 03:25 PM UTC

    This incident has been resolved.

  15. postmortem Mar 19, 2026, 08:13 PM UTC

    During operating hours in EU, we experienced a larger than normal volume of NinjaOne Remote session traffic. This increase caused a backlog in our session validation processing that our system struggled to keep up with. The delay in session validation caused NinjaOne Remote to invalidate sessions to ensure our customers’ security, resulting in a failure to stay connected to devices during the outage. To provide immediate relief, NinjaOne began scaling up infrastructure services and identified further mitigations that are included in the 12.1.0 release. In addition to the NinjaOne Remote incident, NinjaOne also experienced significant performance degradation on several backend databases due to capacity saturation. These databases all exhibited different patterns, exacerbating the complexity of debugging with several concurrent, unique issues. Customers mostly experienced this as page load timeouts, delays in agent data processing, and slow console page loads. NinjaOne upscaled database capacity and rebalanced customers between different database clusters to bring performance back to normal levels and resolve the incident. The incident stretched across multiple days since active troubleshooting could only happen at peak load during EU business hours. We are actively taking all metrics and patterns observed to continue improving monitoring while addressing specific contributing issues with 12.0.30 and 12.1.0.

Read the full incident report →

Minor February 25, 2026

Ninja Remote Intermittent Connections issues - Federal

Detected by Pingoru
Feb 25, 2026, 10:18 PM UTC
Resolved
Feb 26, 2026, 01:56 AM UTC
Duration
3h 38m
Affected: Federal (Moderate)
Timeline · 5 updates
  1. investigating Feb 25, 2026, 10:18 PM UTC

    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.

  2. identified Feb 25, 2026, 11:03 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Feb 25, 2026, 11:23 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Feb 25, 2026, 11:25 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Feb 26, 2026, 01:56 AM UTC

    This incident has been resolved.

Read the full incident report →

Major February 24, 2026

EU - Ninja Remote and UI/Page Load timeouts due to performance degradation

Detected by Pingoru
Feb 24, 2026, 08:15 AM UTC
Resolved
Feb 27, 2026, 10:46 PM UTC
Duration
3d 14h
Affected: United States (US)Europe (EU)Australia (OC)Canada (CA)
Timeline · 26 updates
  1. investigating Feb 24, 2026, 08:15 AM UTC

    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.

  2. investigating Feb 24, 2026, 09:48 AM UTC

    We are continuing to investigate this issue.

  3. investigating Feb 24, 2026, 10:38 AM UTC

    We are continuing to investigate this issue.

  4. identified Feb 24, 2026, 11:22 AM UTC

    The issue has been identified and a fix is being implemented.

  5. identified Feb 24, 2026, 11:28 AM UTC

    We are currently experiencing extremely high load on several backend databases. We are actively working to relieve the pressure and restore services.

  6. identified Feb 24, 2026, 12:39 PM UTC

    We are seeing a positive improvement in overall performance, however we are continuing to debug a handful of load issues as we work to stabilize the environment.

  7. monitoring Feb 24, 2026, 01:45 PM UTC

    We are seeing stable performance metrics at the moment. We are continuing to monitor the environment before considering this resolved.

  8. monitoring Feb 24, 2026, 04:56 PM UTC

    We are continuing to monitor the environment and out of an abundance of caution are leaving the Status Page incident open. At this time monitoring indicates no known performance bottlenecks or other unhealthy signal. There is planned maintenance this evening, and additional fixes and tuning will be performed during this period to reduce customer impact.

  9. investigating Feb 25, 2026, 09:13 AM UTC

    We are encountering DB load once again on several backend databases. We are actively triaging to bring stability to the environment. Some customers are experiencing delays in page load times or timeouts when using Ninja Remote.

  10. investigating Feb 25, 2026, 10:50 AM UTC

    We are continuing to triage and debug the issue. There is continued impact to the NinjaOne console and Ninja Remote at this time.

  11. investigating Feb 25, 2026, 12:19 PM UTC

    We have addressed the performance issues affecting Ninja Remote, and are seeing healthy throughput and internal testing has confirmed consistent connections over the last few minutes.

  12. investigating Feb 25, 2026, 12:53 PM UTC

    We are continuing to investigate this issue.

  13. investigating Feb 25, 2026, 03:02 PM UTC

    We are continuing to investigate this issue.

  14. investigating Feb 25, 2026, 04:01 PM UTC

    We are continuing to investigate this issue.

  15. investigating Feb 25, 2026, 05:16 PM UTC

    We are continuing to investigate this issue.

  16. monitoring Feb 26, 2026, 12:48 AM UTC

    Update – EU Instance Performance Degradation We are continuing to investigate performance degradation affecting portions of our EU region. Currently Impacted Services: RMM/Endpoint Management, Ticketing/PSA, Reporting, Patching, Mobile App, Custom Fields, Documentation, NMS, Web Portal, and Reporting may experience intermittent performance degradation. Services Operating Normally: NinjaRemote, MDM, Backup, CrowdStrike and SentinelOne integrations, File Transfer Service (FTS), and Realtime Tools remain fully operational. Overall performance has shown steady improvements following adjustments made earlier this week. Our engineering team will continue active monitoring and investigation to determine the root cause and will provide an update once that is available

  17. monitoring Feb 26, 2026, 09:09 AM UTC

    We are continuing to closely monitor the environment this morning as customers come online. As of right now current metrics indicate services are operating within expected performance ranges. We will continue to monitor this throughout the day and provide updates periodically should any potential impact be expected.

  18. monitoring Feb 26, 2026, 11:02 AM UTC

    We are continuing to monitor for any further issues.

  19. monitoring Feb 26, 2026, 12:29 PM UTC

    We are continuing to monitor for any further issues.

  20. monitoring Feb 26, 2026, 01:49 PM UTC

    We are continuing to monitor for any further issues.

  21. monitoring Feb 26, 2026, 03:23 PM UTC

    We are continuing to monitor for any further issues.

  22. monitoring Feb 26, 2026, 05:09 PM UTC

    We are continuing to monitor for any further issues.

  23. monitoring Feb 27, 2026, 12:06 AM UTC

    We are continuing to monitor for any further issues.

  24. monitoring Feb 27, 2026, 09:34 AM UTC

    We are continuing to monitor for any further issues.

  25. monitoring Feb 27, 2026, 02:24 PM UTC

    We are continuing to monitor for any further issues.

  26. resolved Feb 27, 2026, 10:46 PM UTC

    We will publish a post-mortem in the coming days detailing the issues and our remediation steps.

Read the full incident report →

Major February 19, 2026

OC branded domain access issues

Detected by Pingoru
Feb 19, 2026, 07:57 PM UTC
Resolved
Feb 20, 2026, 02:04 AM UTC
Duration
6h 7m
Affected: Australia (OC)
Timeline · 7 updates
  1. investigating Feb 19, 2026, 07:57 PM UTC

    We are currently investigating issues with branded domains in OC

  2. investigating Feb 19, 2026, 09:14 PM UTC

    We are continuing to investigate this issue.

  3. identified Feb 19, 2026, 10:24 PM UTC

    The issue has been identified and a fix is being implemented.

  4. identified Feb 19, 2026, 10:33 PM UTC

    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.

  5. identified Feb 20, 2026, 12:26 AM UTC

    We are continuing to work on a fix for this issue.

  6. monitoring Feb 20, 2026, 01:02 AM UTC

    A fix has been implemented and we are monitoring the results.

  7. resolved Feb 20, 2026, 02:04 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 11, 2026

3rd Party SMS MFA Tool: degraded performance globally

Detected by Pingoru
Feb 11, 2026, 12:11 PM UTC
Resolved
Feb 11, 2026, 06:17 PM UTC
Duration
6h 6m
Affected: United States (US)Europe (EU)Australia (OC)Canada (CA)United States (US2)
Timeline · 9 updates
  1. investigating Feb 11, 2026, 12:11 PM UTC

    3rd Party SMS MFA Tool: degraded performance globally

  2. investigating Feb 11, 2026, 12:21 PM UTC

    We are continuing to investigate this issue.

  3. investigating Feb 11, 2026, 02:51 PM UTC

    3rd Party SMS MFA Tool: degraded performance globally

  4. investigating Feb 11, 2026, 02:51 PM UTC

    We are continuing to investigate this issue.

  5. investigating Feb 11, 2026, 02:55 PM UTC

    We are continuing to investigate this issue.

  6. investigating Feb 11, 2026, 02:55 PM UTC

    We are continuing to investigate this issue.

  7. identified Feb 11, 2026, 04:05 PM UTC

    The issue has been identified and a fix is being implemented.

  8. monitoring Feb 11, 2026, 05:31 PM UTC

    A fix has been implemented and we are monitoring the results.

  9. resolved Feb 11, 2026, 06:17 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 5, 2026

Service Issue - Response Time High

Detected by Pingoru
Feb 05, 2026, 09:52 AM UTC
Resolved
Feb 05, 2026, 08:59 PM UTC
Duration
11h 6m
Affected: Europe (EU)
Timeline · 4 updates
  1. investigating Feb 05, 2026, 09:52 AM UTC

    Service Issue - Response Time High - Degraded Performance

  2. identified Feb 05, 2026, 05:06 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Feb 05, 2026, 05:06 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Feb 05, 2026, 08:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Looking to track NinjaOne downtime and outages?

Pingoru polls NinjaOne's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when NinjaOne reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track NinjaOne alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring NinjaOne for free

5 free monitors · No credit card required