Read-only demo. A simulated multi-vendor fleet. Detection and fixes are illustrative; nothing here touches a real network.
Fault Board
criticalFix proposedUniFiConnectivity

Connectivity loss on mtnview-udm-pro

mtnview-udm-pro dropped off the UniFi controller 11 min ago.

Mountain View Office · mtnview-udm-pro (UDM-Pro) · 5/29/2026, 8:55:44 PM

Root-cause analysis
Diagnosed cause

Upstream uplink/WAN link down or device hardware unresponsive

RCA confidence84%

Above the 70% threshold — a fix can be pre-formed.

Reasoning

The device has been unreachable from the cloud for over ten minutes with no telemetry, consistent with a downed uplink or a hung device rather than a transient blip.

Generated by heuristic
Evidence trail
device_unreachableDevice unreachable: yes

Device is not responding to the Meraki cloud at all.

uplink_downUplink down for: 11min

Uplink has been down long enough to rule out a transient flap.

packet_lossWAN packet loss: 100%

Elevated packet loss preceded the outage, pointing upstream.

Normalized telemetry (3)
Device unreachableyes
Uplink down for11min
WAN packet loss100%
Proposed fix

Restart device and confirm WAN failover

Restart the unreachable UniFi device through the controller, then confirm the gateway failed over to the secondary WAN before closing the fault.

risk: mediumunifi.connectivity.restart_and_failover
Exact calls that will run
1. Restart device f4:e2:c6:10:22:01 via the controller
POST /api/s/site_mtnview/cmd/devmgr
2. Confirm WAN failover and uplink health
GET /api/s/site_mtnview/stat/health

Approving is disabled in the read-only demo.