NinjaOne experienced a major incident on July 24, 2026 affecting United States (US), lasting 9h 49m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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.