Details about Consensus Health

The Consensus Health gives you an overview about the network by looking at a recent consensus.

You see:

Known Flags – Which flags are known to which authority and which flags made it into the consensus

Numbers of relays voted about – How many relays each authority has voted about and how many were running

Consensus method – Consensus methods supported by each authority and which method was used for the consensus

Recommended versions – Which versions are recommended by the responsible authorities and what’s in the consensus

Consensus parameters – Which parameters each authority was using and what made it into the consensus

Authority keys – when each authority’s keys expire

Bandwidth scanner status – How many measurement each responsible authority made

Authority version – Which Tor version each authority runs

Please note that “Tonga” is the bridge authority and does not participate on the consensus.

Consensus download statistics – Download times in milliseconds over the last 7 days for each authority

Relay flags – List of relays voted about, what each authority voted and what’s in the consensus

For the flags please note that every flag written in black made it into consensus, when the relay had the running flag.
Consensus and vote match. (Relays that are not running don’t make it into the consensus anymore)
Flags in red mean that the authority voted for this flag, but not enough authorities agreed so it’s not in the consensus.
Consensus and votes don’t match. (Not enough votes for a specific flag)
Flags in gray and struck through mean that this authority did not vote for this flag (although it could), but this flag is in the consensus, because enough authorities voted for this flag.
Consensus and votes don’t match. (Authority didn’t gave a specific flag, but enough others did)
Flags in blue and listed under consensus are the flags which made it into the consensus.

“CircuitPriorityHalflifeMsec” — the halflife parameter used when weighting which circuit will send the next cell.
“UseOptimisticData” — If set to zero, clients by default shouldn’t try to send data to servers until they have received a RELAY_CONNECTED cell.