Mirimir mirimir@riseup.net wrote Fri, 5 May 2017 20:15:31 -1100:

On 05/05/2017 08:06 PM, atagar@torproject.org wrote:

...

NOTICE: The certificate of the following directory authority expires within the next three weeks: gabelmoo (2017-05-27 06-19-24) NOTICE: The following directory authorities are not reporting bandwidth scanner results: maatuska

So what's the prognosis for maatuska?

(Adding tjr@ who might know more.)

There is no ETA ATM AFAIK.

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

On 7 May 2017 at 21:46, Mirimir mirimir@riseup.net wrote:

On 05/07/2017 08:26 AM, Linus Nordberg wrote:

...

Mirimir mirimir@riseup.net wrote Fri, 5 May 2017 20:15:31 -1100:

...

On 05/05/2017 08:06 PM, atagar@torproject.org wrote:

...

NOTICE: The certificate of the following directory authority expires within the next three weeks: gabelmoo (2017-05-27 06-19-24) NOTICE: The following directory authorities are not reporting bandwidth scanner results: maatuska

So what's the prognosis for maatuska?

(Adding tjr@ who might know more.)

There is no ETA ATM AFAIK.

Thanks. I haven't seen anything on tor-dev or tor-relays since 21 April, and nothing in Tor Project blog. But I also haven't seen more questions about relay throughput collapse. So has the network adjusted to maatuska's absence?

On 8 May 2017 at 01:20, Mirimir mirimir@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.

-tom