Is NinjaOne Down?

No — NinjaOne is up

Reachable from all 8 checked regions

Average response time: 201ms

Last checked 4 hours ago · checks run every 6 hours

Official status page: https://status.ninjaone.com

Components the vendor reports as affected: Australia (OC) Under Maintenance

A component listed here does not necessarily mean a full outage — large providers routinely report maintenance on individual locations. It only affects the verdict above when the vendor marks it major or critical and our own checks also saw NinjaOne fail from enough regions to rule out probe noise.

NinjaOne uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

222ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 21 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

21-day clean streak

Sep 14 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

dfw

205ms

DNS 116ms TCP 1ms TLS 14ms TTFB 194ms

ewr

168ms

DNS 118ms TCP 2ms TLS 10ms TTFB 153ms

fra

296ms

DNS 246ms TCP 2ms TLS 10ms TTFB 284ms

gru

313ms

DNS 250ms TCP 2ms TLS 13ms TTFB 302ms

iad

135ms

DNS 67ms TCP 1ms TLS 26ms TTFB 123ms

jnb

137ms

DNS 80ms TCP 1ms TLS 11ms TTFB 127ms

lax

237ms

DNS 169ms TCP 1ms TLS 11ms TTFB 219ms

lhr

121ms

DNS 56ms TCP 2ms TLS 11ms TTFB 104ms

What NinjaOne does

NinjaOne is remote monitoring and management software that IT departments and managed service providers use to patch, monitor, script against and remotely control the computers and servers they look after. It is the console technicians live in all day, so an incident stops routine maintenance and can hide real alerts from the fleet it watches.

What an outage looks like

The console does not load or signs technicians out. Devices show as offline even though users are working normally. Scheduled patching and scripts do not run at their window. Remote control sessions fail to connect. Alerts stop arriving, which is the dangerous part: a quiet console during an incident looks exactly like a healthy fleet.

What to do about it

Check status.ninjaone.com, which reports each hosting region separately: United States (US and US2), Europe, Australia, Canada, Japan and Federal. Find the region your tenant is on. The page also posts scheduled release maintenance by region, so check that list before treating a short interruption as an incident. Keep another remote access route for critical machines.

Is it down for everyone, or just you?

If this page says NinjaOne is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

NinjaOne outage FAQ

Is NinjaOne down for my region only?

Very often. NinjaOne reports US, US2, EU, OC, CA, JP and Federal as separate rows, and an incident on one leaves the others unaffected. An MSP colleague on a different instance signing in fine tells you nothing about yours. Your region is the one in your console address; check that row.

Why do my devices show offline in NinjaOne?

During a regional incident, the console can lose track of agents that are running normally. Confirm with a user before assuming a machine is down. If the region row on the status page is degraded, the offline markers are likely a symptom of the incident rather than a real outage across your clients.

Will missed patches and scripts run after recovery?

Do not assume they will. Scheduled jobs that fell inside an incident window may be skipped rather than queued, depending on how the policy is configured. After recovery, check the activity log for the affected window and rerun anything critical, especially security patches with a deadline.

Is it an incident or scheduled maintenance?

Check the maintenance list on the status page first. NinjaOne posts release windows per region, for example the same release scheduled for OC and US2 at different times. A short interruption during a posted window is expected. Outside one, and with the region row degraded, it is an incident.

Can I still reach client machines during a NinjaOne outage?

Only through another route. Remote control in NinjaOne depends on the platform, so sessions fail while your region is degraded. MSPs usually keep a second remote access tool or direct VPN access for critical servers for this reason. Document which clients have a fallback before you need it.

How we measure this

We request NinjaOne's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where NinjaOne publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when NinjaOne goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required