View public MeshCore observations, explore our Northern Michigan reporting regions, and learn what network maps can—and cannot—tell you about real radio coverage. Meshtastic and MeshCore are separate protocols, so their maps and reports should not be treated as interchangeable.
MESHCORE • PUBLIC OBSERVATION DASHBOARD
CoreScope
Our CoreScope endpoint brings together MeshCore observer reports for exploring which packets and nodes contributing observers have heard. It is an Internet-connected view of observations—not a guarantee of direct over-the-air communication or uninterrupted coverage at every location.
View our county-based reference map for the seven reporting regions: GDW, CAD, TVC, APN, CIU, MQT and CMX. The region codes help organize observer reports. They are not exclusive territories or MeshCore radio forwarding rules.
We are not publishing a MeshMonitor dashboard at this time. Meshtastic radio messaging and optional MQTT reporting are distinct choices. Our guides explain position reports, telemetry and MQTT integration without requiring anyone to use a particular MQTT broker or public map.
If you have a compatible MeshCore MQTT observer, you can learn how to send observations to the Northern Michigan Mesh broker. The setup guide includes the complete TLS server URL, public observer account, and a county selector to choose the correct reporting code.
Node and observer maps can reveal approximate station locations. Before sharing data, review your device's GPS, fixed-position and reporting options. Do not publish someone else's precise equipment location without permission. These maps are useful tools for exploring observations, but they should not be used as a promise of emergency coverage or as a substitute for a controlled, radio-only field test.