Hi juga,
Sorry for the delayed response.
On 2020-08-18 10:05, juga wrote:
thanks for reporting this issue. Replying inline:
No problem.
Tor bandwidth scanners and directory authorities not necessarily run in
the same machine/IP and it's the case of longclaw's bandwidth scanner,
which is
ere
https://metrics.torproject.org/rs.html#details/29BBD80A1702C7FDEF6557C492F44E9EBAB2854A
_Sent from my T-Mobile 4G LTE device_
-- Original message--
From: Eddie
Date: Wed, Aug 19, 2020 6:40 PM
To: tor-relays@lists.torproject.org;
Cc:
Subject:Re: [tor-relays] Tor bandwidth scanner "
Same
herehttps://metrics.torproject.org/rs.html#details/29BBD80A1702C7FDEF6557C492F44E9EBAB2854ASent
from my T-Mobile 4G LTE device-- Original message--From: EddieDate:
Wed, Aug 19, 2020 6:40 PMTo: tor-relays@lists.torproject.org;Cc: Subject:Re:
[tor-relays] Tor bandwidth scanner
Not sure if my relay is similar, but I've been seeing a slow fall in
consensus weight and advertised bandwidth over the past few months even
though absolutely nothing has changed at my end. Well, apart from me
*increasing* the RelayBandwidth settings.
Also before I shut my relay down for a
Hi,
Am 16.08.2020 um 02:41 schrieb Neel Chauhan:
Hi,
I believe the Tor bandwidth scanner nicknamed "longclaw" is measuring
relays in the US West Coast worse than other bandwidth scanners in North
America. This happens on multiple ISPs, both ones I have and ones I don't.
The plots below can
Hi,
thanks for reporting this issue. Replying inline:
Neel Chauhan:
> Hi,
>
> I believe the Tor bandwidth scanner nicknamed "longclaw" is measuring
> relays in the US West Coast worse than other bandwidth scanners in North
> America. This happens on multiple ISPs, both ones I have and ones I
Hi,
I believe the Tor bandwidth scanner nicknamed "longclaw" is measuring
relays in the US West Coast worse than other bandwidth scanners in North
America. This happens on multiple ISPs, both ones I have and ones I
don't.
This includes two Tor exit instances on a dedicated server hosted in
