72084

Everything on this page comes from what the node itself reported to the registrar. The status pill reflects whether its last check-in is inside the one-hundred-and-eighty-second heartbeat window, the registered IP and protocol are whatever the last successful registration arrived with, and the connected node list is the set of links the node advertised at that moment rather than a static configuration.

The thirty-day chart counts registrations per UTC day, which is the clearest way to spot a node that has been quietly restarting: a day with only a handful of check-ins looks very different from a day with the expected fourteen hundred. Below it, the outage timeline turns the same log into plain downtime windows, flagging any gap longer than five minutes and marking an unresolved gap as ongoing.

Traffic history is built from PTT reports. Nodes that include the transmit flag in their check-in get hourly transmission counts, total airtime and a ranked list of the callsigns doing the talking, which makes it easy to see whether a link is genuinely busy or simply idle and online.

Owners can edit the callsign, description, location, frequency, CTCSS tone and coordinates shown here from their dashboard, and can publish this node's live status badge on their own website.