PacketTrends Mesh a public map of nodes that asked to be on one map stations

jaxmesh.com demo node

!ceab1e82 · updates every minute

91% 4.07 V · 3 days ago — telemetry is far patchier than position (only about a quarter of nodes send it at all), so an old reading here is ordinary rather than a sign of trouble.

This node advertises a name but no position, so it has no pin on the map. That is an ordinary state rather than a fault — a node broadcasts its identity on one schedule and its location only if its owner enabled that, and most of the mesh never does.

History

Silent for 3d 12h Oct 5 to Nov 11 · 4 active days · 16 RF frames · 7 gateways

Oct 5 Nov 15

Most recent

BenClient 5063m

Who heard it

Last 24 hours, plus 1 direct link(s) heard earlier.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
BenClient 2 RF — 3.8 dB … 1.5 — 3d 12h ago
Reading the hop budget. Every Meshtastic frame carries a hop limit that each relay decrements. A reception showing 0 left is one that arrived with nothing to spare — one more relay in the path and it would not have arrived at all. That is the closest this data comes to explaining a loss, and it is still not a loss: a frame that was dropped is exactly the one that never reached a gateway to be counted here.