Statusfield LogoStatusfield
NinjaOne Trust logo and current status indicator

NinjaOne Trust Incident History

Operational

ninjaone.com ↗7 components

checked Sep 10, 2026 11:49 PM UTC · NinjaOne Trust's official status page

NinjaOne Trust is up and running.

NinjaOne Trust is currently operational with all systems functioning normally.

All components operational

Email only. No password. No card.
NinjaOne Trust status

Be the first to know

Statusfield watches NinjaOne Trust alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.

Email only. No password. Free.

NinjaOne Trust incident history

5 reports published by NinjaOne Trust in the last 30 days

When NinjaOne Trust breaks, it is typically resolved in 4h 8m — median across 15 resolved incidents over 90 days.

September 10, 2026

Device Monitoring Data Issues

Last update

  1. resolvedSep 10 · 05:22 UTC

    This incident has been resolved.

Reported by NinjaOne Trust on their status page.

September 2, 2026

EU - Agents reporting Offline

Last update

  1. resolvedSep 2 · 12:30 UTC

    This incident has been resolved.

Reported by NinjaOne Trust on their status page.

August 27, 2026

Ticketing E-Mail Notification Issue

Last update

  1. resolvedAug 27 · 13:47 UTC

    This issue has been identified and resolved. The impacted service is now operational.

Reported by NinjaOne Trust on their status page.

August 26, 2026

Remote Tools connection issues - OC

Last update

  1. resolvedAug 26 · 00:56 UTC

    This incident has been resolved.

Reported by NinjaOne Trust on their status page.

August 12, 2026

Automations and Scripting — Degraded

Last update

  1. postmortemAug 12 · 17:51 UTC

    Following our v14 release, we identified an issue that prevented some devices from processing triggered actions. The impact was limited to devices set up as NMS \(Network Management System\) delegates, which represent fewer than 1% of devices in any environment. A change introduced in v14 related to our NMS functionality caused triggered actions for those devices to be routed incorrectly and not processed. To provide immediate relief, we deployed a targeted fix to the most affected customers, confirmed it restored normal processing, and then rolled the fix out across all affected regions to fully resolve the issue. We are taking action to prevent this same issue from occurring in the future.

Reported by NinjaOne Trust on their status page.