[tor-relays] Re: Relay suddenly stopped relaying traffic but is still in the consensus

[forest via tor-relays <tor-relays@xxxxxxxxxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2026-10-05 03:11, Roger Dingledine via tor-relays wrote:
> Not getting the Fast flag is because your consensus weight is quite
> low, which in turn is because the bwauths think you are
> underperforming compared to other relays that advertise a similar
> speed:
> 
> $ grep -A5 103.174.51.65 v3-status-votes|grep ^w
> w Bandwidth=698 Measured=230
> w Bandwidth=698
> w Bandwidth=698
> w Bandwidth=698
> w Bandwidth=698 Measured=81
> w Bandwidth=698
> w Bandwidth=698 Measured=120
> w Bandwidth=698 Measured=64
> w Bandwidth=698 Measured=72
> 
> So, I don't know why it might have dropped off a cliff all at once,
> but that would certainly explain a drop over the course of an hour.
> 
> Since you're right around the threshold for Fast, I wouldn't be
> surprised if you wobble back and forth between being Fast (and getting
> some traffic) and not being Fast (and getting basically no traffic).

You're right, that was the issue.

I know it's in SEA and that's pretty far from any bwauth, but it should
not be estimating mere kB/s when the international connectivity is good:

iperf3 Network Speed Tests (IPv4):
- ---------------------------------
Provider        | Location (Link)           | Send Speed      | Recv
Speed      | Ping
- -----           | -----                     | ----            | ----  
         | ----
Clouvider       | London, UK (10G)          | busy            | busy    
       | 172 ms
Eranium         | Amsterdam, NL (100G)      | 86.8 Mbits/sec  | 159
Mbits/sec   | 175 ms
Uztelecom       | Tashkent, UZ (10G)        | 109 Mbits/sec   | 106
Mbits/sec   | 170 ms
Leaseweb        | Singapore, SG (10G)       | 169 Mbits/sec   | 152
Mbits/sec   | 47.6 ms
Clouvider       | Los Angeles, CA, US (10G) | 103 Mbits/sec   | 112
Mbits/sec   | 234 ms
Leaseweb        | NYC, NY, US (10G)         | 74.2 Mbits/sec  | 113
Mbits/sec   | 286 ms
Edgoo           | Sao Paulo, BR (1G)        | 57.4 Mbits/sec  | 64.3
Mbits/sec  | 314 ms

What could be causing such a large discrepency between measurements from
bwauths and any other measurement from the same location? I'm aware that
the bwauths are mostly centered in Eastern USA and Western Europe and so
will be biased against distant locations, but what the bwauths report is
not even accurate, even when accounting for the distance. Why would each
bwauth in Germany show under 3 Mbps but an iperf3 server just 20 ms away
in the Netherlands shows 159 Mbps?

The international connectivity is really not _that_ bad. So what's going
wrong here and how to I fix it?

Regards,
forest
-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQQtr8ZXhq/o01Qf/pow+TRLM+X4xgUCasx1BQAKCRAw+TRLM+X4
xuYDAQCikkvYQ4Je79xCVSdOZj4ukD7UmLVngehH96gXqqd6LwD/VIkbo6z6OVT5
LveuLcZigbIn3Cdz4BaVNRucYBZulwA=
=xpdJ
-----END PGP SIGNATURE-----
_______________________________________________
tor-relays mailing list -- tor-relays@xxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to tor-relays-leave@xxxxxxxxxxxxxxxxxxxx