authority bandwidth measurements and latency
Hello! I operate 94DEAD24492D6D01E3DE614E8BE6B4035329A4D7 and I've seen various changes in the measured bandwidth in atlas. At the beginning, more than 10 MB/s were measured, now below 3. The machine itself didn't change, I can reach high up- and download rates if I transfer stuff via HTTP/FTP etc. I see that latency isn't that low (50ms https://atlas.ripe.net/measurements/116107380/results) and want to ask if that might be part of this situation. I dunno about the TCP settings of the authority bandwidth testing machines. Can anybody give some hints what's going on? -- Gruß Marco Send unsolicited bulk mail to 1751988041muell@stinkedores.dorfdsl.de
Marco Moock via tor-relays:
Hello!
I operate 94DEAD24492D6D01E3DE614E8BE6B4035329A4D7 and I've seen various changes in the measured bandwidth in atlas.
At the beginning, more than 10 MB/s were measured, now below 3. The machine itself didn't change, I can reach high up- and download rates if I transfer stuff via HTTP/FTP etc.
Where did you look when you say "10 MB/s were measured, now below 3"?
I see that latency isn't that low (50ms https://atlas.ripe.net/measurements/116107380/results) and want to ask if that might be part of this situation.
I dunno about the TCP settings of the authority bandwidth testing machines. Can anybody give some hints what's going on?
Georg
Am 19.08.2025 um 13:02:37 Uhr schrieb Georg Koppen via tor-relays:
Marco Moock via tor-relays:
Hello!
I operate 94DEAD24492D6D01E3DE614E8BE6B4035329A4D7 and I've seen various changes in the measured bandwidth in atlas.
At the beginning, more than 10 MB/s were measured, now below 3. The machine itself didn't change, I can reach high up- and download rates if I transfer stuff via HTTP/FTP etc.
Where did you look when you say "10 MB/s were measured, now below 3"?
TOR Metrics --> Advertised Bandwidth -- Gruß Marco Send unsolicited bulk mail to 1755601357muell@cartoonies.org
Marco Moock via tor-relays:
Am 19.08.2025 um 13:02:37 Uhr schrieb Georg Koppen via tor-relays:
Marco Moock via tor-relays:
Hello!
I operate 94DEAD24492D6D01E3DE614E8BE6B4035329A4D7 and I've seen various changes in the measured bandwidth in atlas.
At the beginning, more than 10 MB/s were measured, now below 3. The machine itself didn't change, I can reach high up- and download rates if I transfer stuff via HTTP/FTP etc.
Where did you look when you say "10 MB/s were measured, now below 3"?
TOR Metrics --> Advertised Bandwidth
Right. But that's not what bandwidth authorities measure. If you hover over that value you'll likely see that the MiB/s shown comes from the observed bandwidth, which is something your relay is self-reporting. The question boils then down to why the relay is not carrying so much traffic anymore as it has been at the beginning. That's not an easy one to answer: maybe the bandwidth authorities have trouble measuring your relay properly or maybe they are able to measure other relays better than yours now shifting more traffic to them etc. There are many potential causes. If you want to investigate the bandwidth measurement part of the puzzle then you could have a look at the votes/bandwidth files and check in them how your relay is doing over time. We have the archived: https://collector.torproject.org/archive/relay-descriptors/bandwidths/ https://collector.torproject.org/archive/relay-descriptors/votes/ Georg
On Wed, 20 Aug 2025, kerem the secondary via tor-relays wrote:
[warn] Your server has not managed to confirm reachability for its ORPort(s) at 31.223.44.45:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
hello my relay doesnt work, firewall is not running, my isp did not block port 443, i have tried the official torrc file in the techincal setup page (only changed the log, contact and relay name) which did not work. I have not included the entire notices.log file because its 4 megabytes of the same error message. I have no idea what i did wrong please help. Thanks in advance
I cannot reach port 443 on 31.223.44.45: %time telnet 31.223.44.45 443 Trying 31.223.44.45... telnet: connect to address 31.223.44.45: Operation timed out telnet: Unable to connect to remote host 0.000u 0.002s 1:15.00 0.0% 0+0k 0+0io 0pf+0w Possible causes include: * You have a firewall that is blocking the traffic. * Your ISP is blocking the traffic, due to NAT or something else. * The IP you have reported doesn't point to your server.
participants (3)
-
Georg Koppen -
Marco Moock -
toroperlist＠jrobin.ephemeron.org