Is NinjaOne Trust Down?

This incident has been resolved. --- [2026-08-04T13:19:44.518-05:00] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-08-04T12:15:35.997-05:00] (identified) We are continuing to work on a fix for this issue. --- [2026-08-04T11:10:15.048-05:00] (identified) The issue has been identified and a fix is being implemented. --- [2026-08-04T11:08:49.042-05:00] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-08-04T10:23:04.119-05:00] (identified) 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 support@ninjaone.com. We have applied a mitigation and are monitoring recovery.

This incident has been resolved. --- [2026-07-30T16:36:01.978-05:00] (monitoring) We are continuing to monitor for any further issues. --- [2026-07-30T15:59:14.925-05:00] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-07-30T12:45:17.849-05:00] (identified) 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. --- [2026-07-30T11:46:38.219-05:00] (identified) The issue has been identified and a fix is being implemented. --- [2026-07-30T10:26:05.117-05:00] (investigating) 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.

This incident has been resolved. --- [2026-07-24T15:10:37.526-05:00] (monitoring) Mitigation efforts have shown positive results and we are seeing agents reporting status correctly at this time. We are continuing to monitor the incident. --- [2026-07-24T13:21:44.592-05:00] (monitoring) 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. --- [2026-07-24T10:38:47.748-05:00] (monitoring) 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 --- [2026-07-24T09:54:22.079-05:00] (monitoring) We are continuing to monitor for any further issues. --- [2026-07-24T08:08:09.481-05:00] (monitoring) 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. --- [2026-07-24T07:10:09.045-05:00] (identified) 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. --- [2026-07-24T06:38:55.542-05:00] (investigating) We are currently investigating this issue.