DllamaNet OpenHopRepeaterObserver
How this repeater scores
CoreScope · relative to this mesh- Bridgeweight 0.300.02 × 0.30 = 0.005
How much of the mesh has to pass through it. A chokepoint between two halves of a network scores high. Traffic has other ways round. Not a fault - it means the area is well connected.
- Coverageweight 0.250.46 × 0.25 = 0.115
How much of the mesh it can reach, weighted so near neighbours count more than distant ones.
- Redundancyweight 0.250.06 × 0.25 = 0.014
What breaks if it vanishes. High means nothing else covers its job. Something else already covers what it does, so losing it would not split the mesh.
- Trafficweight 0.200.02 × 0.20 = 0.005
How much it actually relayed, measured rather than inferred from the map. It is carrying little traffic compared with the busiest repeater here.
What would actually change this
A low grade on a repeater that works fine usually means the area is well served, not that the machine is bad. Over half the weight — Bridge and Redundancy — describes where it sits among its neighbours, and neither is yours to move.
- About typical for the area
Coverage of 0.46 against an average of 0.44 across 16 repeaters within 25 miles.
- A low Bridge is not a fault
Bridge measures how much traffic has no choice but to pass through this node. It falls when neighbours put up repeaters that cover the same ground — so it can drop without anything changing here at all. There is nothing to tune.
- Reachable, but not on anyone's path
It can hear plenty and is relaying little, which usually means traffic has shorter routes. That follows from where the people are, and tends to change on its own as the mesh grows.
Every axis is scored against the other repeaters this analyzer can see, so 1.00 means “the best of these” rather than perfect, and a grade here is not comparable with one from another mesh. CoreScope’s own note on the bands is that they are a first cut, not tuned against real data — so treat the letter as a rough impression and the number as the real answer.
History
48 samples · last 30 daysHistory starts from today. Readings were only ever stored as a single latest value before now, so there is nothing earlier to show — trends will fill in as the mesh is sampled.