Relay topology

Mesh

The MeshCore mesh as a topology map.

no key required CORS-open

Nodes/api/v1/events?layer=mesh, colored by role · links/api/v1/mesh/links, each advert's relay path rolled up into a durable weighted edge list — links fade by recency (a quiet-but-recent link is dim, not gone) and thicken with traffic, and the window trades currency for history · coverage is deliberately wide, Bay Area → Sierra · a sparse map is not an all-clear — a node is drawn only once we have heard it advertise a location

Nodes heard

node · type · monitor · snr / rssi · hops · heard

Node	Type	Monitor	SNR / RSSI	Hops	Heard
Loading nodes…

Ambient state

Mesh presence is INFO: excluded from a place's totalActive, its severity counts, its top events and its area mode. A busy mesh does not raise an alert level, and a quiet one does not lower it.

Monitor: a second source

Everything else on this page is what a node broadcast. The Monitor column is what an operator-run monitor read by logging into the node — battery, temperature, and the fact that it could be reached at all — pushed to /api/v1/ingest/mesh.repeater.

not monitored is the common state and means nobody is watching, not that the node is down. A mesh has no goodbye packet, so silence is ambiguous — a monitor that logged in and failed is not, which is why UNREACHABLE is worth its own ring on the map. Open a node for its full telemetry.

Telemetry is volatile

SNR, RSSI, hop count and everything a monitor reports are deliberately excluded from the content hash, so they never mint a revision — only a node's identity, location, status or reachability does.

Missing telemetry renders as —, never 0.

Which clock

To ask when a node last spoke, read the event's observedAt — not telemetry.lastAdvertAt, which the node stamps from its own unsynchronized clock.