User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
ninjaone.com · Cloud & developer
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Device Local Time Schedules Not Running in Parts of Canada
Source: the vendor's status page · We are not affiliated with NinjaOne Trust.
Estimated fix: Not enough NinjaOne Trust history yet; similar Cloud & developer outages lasted 2 h (median, typically 48 min–7.5 h; 87 outages).
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Reachable from all 4 regions we check from.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 20 ms.
Minor incident
Device Local Time Schedules Not Running in Parts of Canada Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 07 | 0 | 0.0 | 69 ms | 0 |
| Tue 09 | 0 | 0.0 | 65 ms | 0 |
| Tue 11 | 0 | 0.0 | 21 ms | 0 |
| Tue 14 | 0 | 0.0 | 57 ms | 0 |
| Tue 16 | 0 | 0.0 | 66 ms | 0 |
| Tue 18 | 0 | 0.0 | 91 ms | 0 |
| Tue 20 | 0 | 0.0 | 112 ms | 0 |
| Tue 23 | 0 | 0.0 | 102 ms | 0 |
| Wed 01 | 0 | 0.0 | 48 ms | 0 |
| Wed 03 | 0 | 0.0 | 54 ms | 0 |
| Wed 05 | 0 | 0.0 | 112 ms | 0 |
| Wed 08 | 0 | 0.0 | 90 ms | 0 |
| Wed 10 | 0 | 0.0 | 76 ms | 0 |
| Wed 12 | 0 | 0.0 | 20 ms | 0 |
| Wed 14 | 0 | 0.0 | 51 ms | 0 |
| Wed 16 | 0 | 0.0 | 73 ms | 0 |
| Wed 18 | 0 | 0.0 | 53 ms | 0 |
| Wed 21 | 0 | 0.0 | 110 ms | 0 |
| Wed 23 | 0 | 0.0 | 184 ms | 0 |
| Thu 01 | 0 | 0.0 | 46 ms | 0 |
| Thu 03 | 0 | 0.0 | 191 ms | 0 |
| Thu 05 | 0 | 0.0 | 271 ms | 0 |
| Thu 07 | 0 | 0.0 | 115 ms | 0 |
| Thu 09 | 0 | 0.0 | 64 ms | 0 |
| Thu 11 | 0 | 0.0 | 141 ms | 0 |
| Thu 13 | 0 | 0.0 | 109 ms | 0 |
| Thu 16 | 0 | 0.0 | 70 ms | 0 |
| Thu 18 | 0 | 0.0 | 43 ms | 0 |
| Thu 20 | 0 | 0.0 | 76 ms | 0 |
| Thu 21 | 0 | 0.0 | 32 ms | 0 |
| Thu 23 | 0 | 0.0 | 72 ms | 0 |
| Fri 01 | 0 | 0.0 | 20 ms | 0 |
| Fri 04 | 0 | 0.0 | 76 ms | 0 |
| Fri 06 | 0 | 0.0 | 74 ms | 0 |
| Fri 08 | 0 | 0.0 | 55 ms | 0 |
| Fri 10 | 0 | 0.0 | 73 ms | 0 |
| Fri 12 | 0 | 0.0 | 58 ms | 0 |
| Fri 14 | 0 | 0.0 | 23 ms | 0 |
| Fri 16 | 0 | 0.0 | 30 ms | 0 |
| Fri 18 | 0 | 0.0 | 92 ms | 0 |
| Fri 20 | 0 | 0.0 | 102 ms | 0 |
| Fri 22 | 0 | 0.0 | 63 ms | 0 |
| Sat 00 | 0 | 0.0 | 48 ms | 0 |
| Sat 02 | 0 | 0.0 | 109 ms | 0 |
| Sat 04 | 0 | 0.0 | 69 ms | 0 |
| Sat 06 | 0 | 0.0 | 37 ms | 0 |
| Sat 07 | 0 | 0.0 | 42 ms | 0 |
| Sat 09 | 0 | 0.0 | 20 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 9 days of data so far, so the 90-day numbers fill in over time.
Infrastructure Maintenance - US2
We will be performing scheduled maintenance on our backend infrastructure as part of our ongoing infrastructure updates. During this maintenance window, customers may experience brief service interruptions.
Infrastructure Maintenance - NA
We will be undergoing scheduled maintenance during this time.
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
No outages on record for NinjaOne Trust yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when NinjaOne Trust goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send NinjaOne Trust alerts to Slack, Discord or a webhook — free.
NinjaOne Trust, at ninjaone.com, is one of the Cloud & developer services we monitor. NinjaOne is the unified IT operations platform for endpoint management, autonomous patching, backup, and remote access. Trusted by IT teams and MSPs worldwide.
NinjaOne Trust publishes an official status page at status.ninjaone.com; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 58 ms average, 20–109 ms range across 12 successful checks.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Device Local Time Schedules Not Running in Parts of Canada
We have not recorded a public NinjaOne Trust incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
58 ms on average over the last 24 hours (20–109 ms). Latest regional checks: US East 27 ms, US West 25 ms, Europe 47 ms, Asia-Pacific 35 ms.
Yes, at https://status.ninjaone.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report NinjaOne Trust here at once, the problem is on NinjaOne Trust's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with NinjaOne Trust. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.