Major incident

NinjaOne Trust: US - Service Availability Issue

Affected: United States (US)

Current status of NinjaOne Trust: Operational — live NinjaOne Trust status

Timeline

1. Jul 24, 2026, 11:38 UTC
   investigating
   We are currently investigating this issue.
2. Jul 24, 2026, 12:10 UTC
   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.
3. Jul 24, 2026, 13:08 UTC
   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.
4. Jul 24, 2026, 14:54 UTC
   monitoring
   We are continuing to monitor for any further issues.
5. Jul 24, 2026, 15:38 UTC
   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
6. Jul 24, 2026, 18:21 UTC
   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.
7. Jul 24, 2026, 20:10 UTC
   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.
8. Jul 24, 2026, 21:28 UTC
   resolved
   This incident has been resolved.

Updates as published by NinjaOne Trust (original).