| household | exit address | status | tier | health | uptime | handshake | line | v6 | consent | DNS | device | machine | place | used by | config | note | connect |
|---|
One token runs this page. It lists households, and it also drives Connect — which mints a working tunnel into the exit network and revokes that household's client's previous config, cutting off whoever holds it. It still cannot revoke a household, pause one, or run a job: those stay on the control API, on loopback. Treat this token as a credential that changes things, not a viewing pass.
uptime is SAMPLED, not logged. This origin reads each household’s tunnel state on a fixed cadence and counts the reads; nothing here observes a transition. An interruption shorter than the blind window named in that column’s tooltip leaves no trace at all, so the figure is a ceiling on availability rather than a measurement of it. There are two records. The 24-hour strip lives in this origin process and starts empty at every restart, and any stretch the sampler did not run is reported as unwatched rather than counted as up or down. The figure beside it is the stored record, read from the database: it survives restarts, prints no ratio until it holds a day of observed hours, and is shown even when the 24-hour strip is empty.
Pagekind's aggregate counts, shown as reported: each card is one count over its own window, start included and end excluded, and nothing here adds them together, compares them or turns them into anything else. No data means the count was not measured, which is not a count of zero. Hover a card for what it does and does not count.
Connect on a household row is the normal way in — it works out which client is pinned to that household and mints for it. The box below is only needed when a household has SEVERAL clients pinned to it, where nothing can tell which one you meant. Either way, minting revokes that client's previous config: a WireGuard key admits one session, so whoever is using the old one is cut off at once.
Scan with the WireGuard app. The QR carries a shortened config: a QR code holds 2,953 bytes and the full one is about 4,400, so every warning above is omitted from it.