Your node now finds the first router on your ISP's network
TL;DR: From v0.0.117 onward, your node looks for the first router on your ISP's network, at most once an hour, and reports it when it checks in. We use it only to see which nodes share a point of failure, never for rankings or earnings.
From v0.0.117 onward, your node looks for the first router outside your home network: the first one that belongs to your ISP. Nodes behind the same router go offline together if it fails, and knowing which ones share it helps us see that.
Since 17 October, we group nodes that report the same router. The grouping is internal only. It is never used to decide eligibility, rankings or earnings, or where sites are placed or how requests are routed.
How it works
- Only when asked, at most once an hour. Your node is asked after it starts, when its last result is more than six hours old, and when its public address moves to another network.
- In the background, never during a visitor’s request. It sends a short trace towards 1.1.1.1, then 8.8.8.8, then 9.9.9.9 if needed. IPv4 only.
- A small report. It sends the first hop that isn’t on your home network, about 120 bytes, with its next check-in.
- No special permissions. It works on Linux, macOS and Windows without administrator rights, in Docker with default networking, and in the Home Assistant add-on.
If it can’t measure
A node that can’t measure sends nothing and works exactly as before. If a measurement fails, the last good result is kept.
What you need to do
Nothing.