[tor-consensus-health] Consensus issues

Tom Ritter tom at ritter.vg
Mon May 8 06:33:41 UTC 2017

On 8 May 2017 at 01:20, Mirimir <mirimir at riseup.net> wrote:
> On 05/07/2017 06:52 PM, Tom Ritter wrote:
>> We're awaiting provisioning of a new host that we'll use as the bwauth
>> for maatuska. The network is, of course, designed to be resilient in
>> the face of a dirauth or bwauth going down; so it's expected that
>> things keep chugging along.
>> For some relays, their measured speeds may adjust down, but the (new)
>> bwauth graphs at https://consensus-health.torproject.org/graphs.html
>> actually imply that maatuska was voting low on a majority of relays,
>> so on the whole, measured speeds may have gone up. (This is not hard
>> data/analysis, but that what it implies to me.)
>> -tom
> Thanks :)
> So basically, lack of data from maatuska just affected a few relays, and
> only transiently. Right?

I don't know if I'd say that. If affected, to some degree, every
relay. But that doesn't mean it affected every relay by moving their
measured bandwidth _down_ (some it moved up).

The more bwauths we have, the more accurate the resulting measured
bandwidth for every relay is (we hope). So missing maatuska hurts in
that regard, just like only having 5 bwauths instead of 9 hurts.


More information about the tor-consensus-health mailing list