[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-talk] improvements torstatus.blutmagie.de

Olaf Selke:
> Hello,
> https://torstatus.blutmagie.de is still alive now with five additional
> columns:
> "FirstSeen"
> ===========
> Date when router's fingerprint was first seen starting 10/27/15. All
> routers alive before are dated 2000-01-01 simply meaning I have no clue
> about the past. The summary table on page bottom displays the total
> number of routers first seen after 10/27/2015.
> "ASName"
> ========
> The IPv4 AS Name based on info from whois.cymru.com.
> "ASNumber"
> ==========
> The IPv4 AS Number based on info from whois.cymru.com.
> "ConsensusBandwidth"
> ====================
> The "w" SP "Bandwidth=" microdescriptors as defined on line 1890
> https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt
> "OrAddress"
> ===========
> The "or-address" element from server descriptor as defined on line 1318
> https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt
> The "CSV List of Current Result Set" download should work as well.
> Please drop me a note in case something is shown wrong.

Great stuff Olaf.

Some questions:

I'm aware of the "Last Published Descriptor (GMT)" field, but why is
there such a consistent gap in "observed bandwidth" between Blutmagie
and Rueckgr.at, which is the only other operational TorStatus I'm aware
of?  Is this a question for the Rueckgr.at admin?

Is there another way to check observed bandwidth? Atlas. seems to only
look at advertised bandwidth.

Thanks for your work on this.  I have personally found it enormously
useful for years.  Now we're playing with quick queries like this:



5F77 765E 40D6 5340 A0F5 3401 4997 FF11 A86F 44E2
tor-talk mailing list - tor-talk@xxxxxxxxxxxxxxxxxxxx
To unsubscribe or change other settings go to