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

Connectivity loss on hq-mx-01

hq-mx-01 stopped responding to the Meraki cloud 18 min ago.

HQ - Floor 2 · hq-mx-01 (MX68) · 5/29/2026, 8:48: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: 18min

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

packet_lossUplink packet loss: 12%

Elevated packet loss preceded the outage, pointing upstream.

Normalized telemetry (3)
Device unreachableyes
Uplink down for18min
Uplink packet loss12%
Proposed fix

Reboot device and re-verify uplink

Power-cycle the unreachable device via the Dashboard API, then re-poll its uplink status to confirm recovery before closing the fault.

risk: mediummeraki.connectivity.reboot_and_recheck
Exact calls that will run
1. Reboot device Q2XX-AAAA-1111
POST /devices/Q2XX-AAAA-1111/reboot
2. Re-poll uplink status to confirm the device is back online
GET /devices/Q2XX-AAAA-1111/lossAndLatencyHistory

Approving is disabled in the read-only demo.