“Datto RMM Device Online/Offline Status”
Autotask PSA Datto RMM Datto Backup Microsoft 365 SmileBack HubSpot IT Glue All reports
AI-GENERATED REPORT
You searched for:

Datto RMM Device Online/Offline Status

Analysis and reporting on device online/offline status for managed service providers.

Built from: Datto RMM
How this report was made
1
Autotask PSA
Multiple data sources combined
2
Proxuma Power BI
Pre-built MSP semantic model, 50+ measures
3
AI via MCP
Claude or ChatGPT writes DAX queries, executes them, formats output
4
This Report
KPIs, breakdowns, trends, recommendations
Ready in < 15 min

Datto RMM Device Online/Offline Status

Analysis and reporting on device online/offline status for managed service providers.

The data covers the full scope of Autotask PSA records relevant to this analysis, broken down by the key dimensions your team needs for day-to-day decisions and client reporting.

Who should use this: NOC teams, asset managers, and service delivery leads

How often: Weekly for fleet reviews, monthly for lifecycle planning, quarterly for budgeting

Time saved
Device audits from RMM consoles require clicking through hundreds of screens. This report consolidates everything.
Fleet visibility
Ghost devices, storage issues, and uptime problems across the entire fleet in one view.
Lifecycle planning
Data for hardware refresh cycles, warranty tracking, and capacity planning.
Report categoryDevice & Endpoint Management
Data sourceAutotask PSA · Datto RMM · Datto Backup · Microsoft 365 · SmileBack · HubSpot · IT Glue
RefreshReal-time via Power BI
Generation timeUnder 15 minutes
AI requiredClaude, ChatGPT or Copilot
AudienceNOC teams, asset managers
Where to find this in Proxuma
Power BI › Devices › Datto RMM Device Online/Offline Status
What you can measure in this report
Fleet Health at a Glance
Online Rate by Client
What is Causing Offline Devices?
Six-Month Trend
Server vs Workstation Split
Ghost Agents
Key Findings
Strategic Recommendations
Frequently Asked Questions
Total Managed Devices
Online Now
Offline
AI-Generated Power BI Report
Datto RMM Device Online/Offline Status

Analysis and reporting on device online/offline status for managed service providers.

Demo Report: This report uses synthetic data to demonstrate AI-generated insights from Proxuma Power BI. The structure, DAX queries, and analysis reflect real MSP data patterns.
1.0 Fleet Health at a Glance
93.7% ONLINE

Out of 3,847 managed devices across 12 clients, 3,604 are currently online and reporting to Datto RMM. The remaining 243 devices (6.3%) are unreachable. 38 of those have been dark for over 30 days and are likely decommissioned hardware still carrying active agent licenses.

Total Managed Devices
6,953
3,410 online (49.0%)
Online Now
4,439
43.5% online
Offline
1,372
51.9% online
Stale (30+ Days)
38
Likely decommissioned
View DAX Query - Fleet Health Summary
EVALUATE TOPN(10, SUMMARIZECOLUMNS('BI_Datto_Rmm_Devices'[Type], "DeviceCount", COUNTROWS('BI_Datto_Rmm_Devices'), "Online", CALCULATE(COUNTROWS('BI_Datto_Rmm_Devices'), 'BI_Datto_Rmm_Devices'[Online] = TRUE())), [DeviceCount], DESC)
What are these DAX queries? DAX (Data Analysis Expressions) is the formula language used by Power BI to query data. Each “View DAX Query” section shows the exact query the AI wrote and executed. You can copy any query and run it in Power BI Desktop against your own dataset.
2.0 Online Rate by Client

All 12 clients ranked by device online rate. The spread runs from 98.2% down to 83.7% -- a 14.5 percentage-point gap between the best and worst performers.

Apex IT Solutions
98.2%
Summit Networks
98.0%
Meridian Group
97.4%
Horizon MSP
97.1%
Frontier IT
96.4%
Eclipse Digital
95.7%
Pinnacle Tech
94.4%
Vanguard Tech
92.4%
Cobalt Systems
89.9%
Redstone IT
88.9%
NovaTech Solutions
86.2%
Ironclad Services
83.7%

The top six clients all sit above 95%, which is the threshold for healthy fleet management. Below that line, things deteriorate quickly. The bottom four -- Cobalt Systems, Redstone IT, NovaTech Solutions, and Ironclad Services -- all fall under 90%, and together they contribute 93 of the 243 offline devices (38.3% of all offline endpoints from just 33.3% of clients). Ironclad Services at 83.7% means roughly 1 in 6 of their devices is unreachable at any given time.

View DAX Query - Online Rate by Client
EVALUATE
ADDCOLUMNS(
    SUMMARIZECOLUMNS(
        BI_Datto_RMM_Devices[company_name],
        "Total Devices", COUNTROWS(BI_Datto_RMM_Devices),
        "Online", CALCULATE(COUNTROWS(BI_Datto_RMM_Devices), BI_Datto_RMM_Devices[status] = "Online"),
        "Offline", CALCULATE(COUNTROWS(BI_Datto_RMM_Devices), BI_Datto_RMM_Devices[status] = "Offline")
    ),
    "Online Rate", DIVIDE([Online], [Total Devices])
)
ORDER BY [Online Rate] DESC
3.0 What is Causing Offline Devices?

Of the 243 offline devices, how long have they been unreachable? Short outages are routine. Anything over 7 days is a problem.

42
58
47
41
17
38
<1h 1-4h 4-24h 1-7d 7-30d 30+d

The bulk of offline devices (100 out of 243, or 41.2%) have been unreachable for less than 4 hours. This is normal churn: reboots, end-of-day shutdowns, brief network drops. These devices will almost certainly come back online without intervention.

The real concern sits on the right side of the chart. 55 devices (22.6%) have been dark for over 7 days. Of those, 38 have not checked in for 30+ days. These stale devices inflate your managed device count without providing any monitoring value. Each one is a billing line item with zero return, and each one drags down your online rate by roughly 0.01 percentage points.

View DAX Query - Offline Duration Buckets
EVALUATE
ADDCOLUMNS(
    SUMMARIZECOLUMNS(
        "Duration Bucket", SWITCH(
            TRUE(),
            DATEDIFF(BI_Datto_RMM_Devices[last_seen], TODAY(), HOUR) < 1, "<1 hour",
            DATEDIFF(BI_Datto_RMM_Devices[last_seen], TODAY(), HOUR) < 4, "1-4 hours",
            DATEDIFF(BI_Datto_RMM_Devices[last_seen], TODAY(), HOUR) < 24, "4-24 hours",
            DATEDIFF(BI_Datto_RMM_Devices[last_seen], TODAY(), DAY) < 7, "1-7 days",
            DATEDIFF(BI_Datto_RMM_Devices[last_seen], TODAY(), DAY) < 30, "7-30 days",
            "30+ days"
        ),
        BI_Datto_RMM_Devices[status] = "Offline",
        "Device Count", COUNTROWS(BI_Datto_RMM_Devices)
    ),
    "Pct of Offline", DIVIDE(
        [Device Count],
        CALCULATE(COUNTROWS(BI_Datto_RMM_Devices), BI_Datto_RMM_Devices[status] = "Offline")
    )
)
4.0 Six-Month Trend

Online rate from November 2025 through April 2026, showing a steady climb from 91.2% to 93.7% while the fleet grew 12.7%.

90% 93% 96% 91.2% 91.8% 92.4% 92.9% 93.4% 93.7% Nov Dec Jan Feb Mar Apr
Rate Improvement
+2.5pp
91.2% to 93.7%
Fleet Growth
+12.7%
435 new devices
MTTR Reduction
-29.2%
4.8h down to 3.4h
Offline Count
-57
300 down to 243

The fleet grew from 3,412 to 3,847 devices over six months while online rates climbed steadily. That is a 2.5 percentage-point improvement despite onboarding 435 new endpoints. Mean time to recovery (MTTR) dropped from 4.8 hours to 3.4 hours -- a 29.2% improvement driven by alerting policy changes introduced in January and faster agent response workflows. The consistent upward slope shows these operational gains are compounding, not plateauing.

5.0 Server vs Workstation Split

The 5.1 percentage-point gap between server and workstation online rates tells a clear story about where the problem sits.

97.5% ONLINE
Servers
794 of 814 online
92.4% ONLINE
Workstations
2,631 of 2,846 online
95.7% ONLINE
Network Devices
179 of 187 online

Servers are performing well at 97.5%, in line with the industry target of 97%+ during business hours. They live in controlled environments with stable power, hardwired networking, and enterprise-grade UPS. The 20 offline servers are still a concern because each one represents a potential business-critical outage your team cannot see. The critical alert rate for servers (4.2%) is double that of workstations (1.8%), confirming that server downtime carries outsized operational impact.

Workstations at 92.4% are the main drag on the portfolio average. The 215 offline workstations include a mix of normal user behavior (shutdowns, travel, VPN disconnects) and genuinely problematic endpoints hidden in the noise. Separating one from the other requires looking at the duration data in section 3.0.

6.0 Ghost Agents

Six devices with Datto RMM agents installed that have stopped reporting entirely. Four are servers.

ClientDevice NameTypeLast SeenAgent VersionDays SilentAction
Ironclad ServicesSRV-DC-02Server2025-11-18v2.0.4 (outdated)138
Cobalt SystemsSRV-APP-03Server2025-12-01v2.0.8 (outdated)125
NovaTech SolutionsWS-ACCT-14Workstation2026-01-22v2.1.8 (outdated)73
Redstone ITWS-SALES-07Workstation2026-02-10v2.2.0 (outdated)54
Vanguard TechSRV-DB-01Server2026-02-14v2.1.4 (outdated)50
Redstone ITSRV-MAIL-01ServerNeverv2.2.0 (outdated)--

These six ghost agents span five clients and share a common trait: all are running outdated agent versions. Ironclad Services has a domain controller (SRV-DC-02) that has not reported in 138 days on agent version 2.0.4. Redstone IT has a mail server (SRV-MAIL-01) that has never successfully checked in, pointing to a failed deployment. Each ghost agent inflates the managed device count, which affects per-device pricing, SLA calculations, and every metric in this report. Removing or reinstalling these six endpoints would immediately improve the online rate by roughly 0.1%.

7.0
Key Findings
!

Performance Gap Requires Attention

The gap between top and bottom performers is wider than expected. The bottom 20% scores more than 25 percentage points below the portfolio average, indicating structural issues that require targeted intervention.

!

Declining Trend in Moderate Risk Group

Entities in the moderate risk category show a declining trend over the past quarter. Without intervention, 3-4 of these entities may shift to the high-risk category within 60 days.

Top Performers Remain Consistent

The top 30% of the portfolio maintains stable performance above target, indicating current best practices are effective and can serve as a model for the rest.

8.0
Strategic Recommendations

1. Conduct a targeted review of all high-risk entities within 2 weeks. Document the root cause for each entity and create a remediation plan with clear deadlines and accountable owners.

2. Implement automated monitoring for the moderate-risk group. Set thresholds that trigger an alert when performance drops 5 percentage points below target, enabling early intervention before entities slip into high risk.

3. Schedule this report monthly as part of the QBR process. Use the trend data to verify that improvement initiatives are delivering measurable results across multiple quarters.

9.0
Frequently Asked Questions
What constitutes an “offline” device in Datto RMM?

A device is marked offline when its Datto RMM agent fails to check in with the platform for more than 30 minutes. This can be caused by network outages, device shutdowns, agent crashes, firewall blocks, or VPN disconnects. The status updates automatically when the agent resumes communication.

How quickly should we investigate an offline device?

Servers should be investigated within 15 minutes during business hours. Workstations should be reviewed within 4 hours if the user has reported an issue, or within 24 hours for routine checks. After-hours, focus on servers and business-critical infrastructure only. Devices offline for more than 7 days should be flagged for manual follow-up regardless of type.

Should we alert clients when their devices go offline?

Yes, but be selective. Alert clients about server downtime and business-critical workstations. Sending offline alerts for employee laptops that shut down at 5 PM creates noise and erodes your credibility. Build a tiered notification policy: immediate for servers, daily digest for workstations, weekly summary for the full fleet.

What is a healthy online rate for an MSP portfolio?

During business hours, aim for 97%+ for servers and 92%+ for workstations. A blended portfolio rate above 95% is considered strong. Below 90% on any device type signals systemic issues with agent health, network reliability, or device lifecycle management. This portfolio sits at 93.7% blended, which is acceptable but leaves room for improvement at the bottom-tier clients.

How do ghost agents affect our reporting accuracy?

Ghost agents inflate total device count, pulling down online rate percentages and skewing per-device cost calculations. A device that has not reported in 90+ days should be decommissioned or reinstalled. Leaving ghost agents in place means billing for and reporting on devices with zero visibility. Removing the 38 stale devices in this portfolio would immediately bump the online rate from 93.7% to roughly 94.6%.

How can we reduce false offline readings from laptops?

Configure Datto RMM policies to extend the offline threshold for laptop device types from 30 minutes to 2 hours. This filters out normal sleep/hibernate cycles and VPN reconnects. For remote workers, consider a separate monitoring policy that only flags devices offline for more than 8 business hours. This reduces alert noise without sacrificing visibility into genuinely problematic devices.

Generate this report from your own data

Connect Proxuma Power BI to your PSA, RMM, and M365 environment, use an MCP-compatible AI to ask questions, and generate custom reports - in minutes, not days.

See more reports Get started