Version 97 (modified by karsten, 9 months ago) (diff)

Update burndown chart.

Metrics Team


Welcome to the Metrics Team page. The Metrics Team is a group of Tor people who care about measuring and analyzing things in the public Tor network. There are currently three other teams in Tor: the Network Team writes the software to keep the Tor network running, the Applications Team produces usable applications for end users, and the Community Team focuses on the non-technical aspects of growing a healthy Tor community. But if you're interested in measurements and analyses, the Metrics Team is what you're looking for. Welcome!


The Metrics Team currently consists of between half a dozen and a dozen developers, depending on how and when you count. We're not listing names here to keep the team open to everyone. You're on the team if you're participating in discussions and development, and you're not part of the team anymore if you decide you want to move on (which we hope won't happen).


Our synchronous medium of communication is IRC meetings that happen every Thursday at 14:30 UTC in #tor-dev on OFTC.

If you want to reach someone from the team between these meetings to ask a development-related question, just go to #tor-dev and mention the magic word "metrics", and somebody from the team might either be around or appear later and get back to you.

Our asynchronous medium of communication is the metrics-team@ mailing list. This list is public in the sense that anyone can subscribe and read archives. But it's moderated on first post, meaning that your first post will be reviewed to make sure it's not spam and on topic and all further posts will go directly to the list. Feel free to subscribe and just listen if you want, and feel free to post if you have a question that you think is on topic.


The Metrics Team is not selling any products, don't worry.

Product is a codebase of software maintained by the Team. Not all products of the Metrics Team are mentioned in this section (for a more complete list see roadmap draft). Instead, we list some long-term products here that are or will be released in way that a third party can decide to run a mirror of this type of service.

Here some links to these products' pages (in alphabetical order):

  • CollecTor the friendly data collecting service. A wiki subsection for CollecTor mirror operators mirror operating wiki.
  • ExoneraTor helps to find out whether that address was used as a Tor relay.
  • Metrics the primary place to learn interesting facts about the Tor network.
  • metrics-lib a Java library that fetches and parses Tor descriptors.
  • Onionoo is a web-based protocol to learn about currently running Tor relays and bridges. A wiki subsection for Onionoo mirror operators mirror operating wiki

Releases and Milestones


December 20, 2017 Onionoo 5.0-1.9.0, cf. announcement downloads
November 28, 2017 Onionoo 4.4-1.8.0, cf. announcement downloads
November 20, 2017 Onionoo 4.3-1.7.1, cf. announcement, preparing major version jump downloads
October 27, 2017 Joint release of milestones CollecTor 1.4.1, Onionoo 4.2-1.6.1, cf. announcement downloads
October 10, 2017 Joint release of milestones CollecTor 1.4.0, metrics-lib 2.1.1, Onionoo 4.2-1.6.0, cf. announcement downloads
September 15, 2017 Joint release of milestones CollecTor 1.3.0, metrics-lib 2.1.0, Onionoo 4.1-1.5.0, cf. announcement downloads
August 31, 2017 milestone Onionoo 4.1-1.4.0 and 4.1-1.4.1 announcement download Onionoo 4.1-1.4.1
August 18, 2017 announcement download CollecTor 1.2.1
August 8, 2017 milestone Onionoo 4.0-1.3.0 download Onionoo 4.0-1.3.0
July 13, 2017 milestone CollecTor 1.2.0 download CollecTor 1.2.0

older Metrics releases

Planned Milestones

CollecTor 1.5.0 CollecTor 2.0.0
metrics-lib 2.2.0 metrics-lib 3.0.0
ExoneraTor 1.0.0 ExoneraTor 2.0.0
MetricsWeb 1.0.0 MetricsWeb 2.0.0
Onionoo 2.0.0 Onionoo 2.1.0


An FAQ by and about the Metrics Team. If something you want to know is not answered yet, check back in a few days. Or address your question directly to us via the communication channels listed in the previous section.

The 32C3 State of the Onion talk covered work of the Metrics Team by giving example of how bad relays are detected, investigated, and excluded from the Tor network. The entire talk is worth watching, but if you're short on time, be sure to watch minutes 20 to 28.

More documentation

Censorship Watch

MetricsTimeline lists incidents that might help in interpreting metrics graphs.

Here's a table with tickets related to censorship incidents:

Results (1 - 7 of 9)

1 2
Ticket Summary Status Priority Severity Reporter Modified
#29855 TOR was blocked by my company. needs_information Medium Normal wanje 4 weeks ago
#27435 Poland, PLAY operator and OBFS4 new High Normal VeryVeryBadUser 8 weeks ago
#20348 Allot Communications blocking of vanilla Tor, obfs4, and meek in Kazakhstan, starting 2016-06 reopened Medium Normal dcf 3 months ago
#27723 Obfs4 stopped working 16 Sept 18 new Medium Normal mwolfe 4 months ago
#28898 Huge drop of users in UAE new Medium Normal anadahz 4 months ago
#28748 Казахстан new Medium Normal Ridvanz 5 months ago
#26807 Venezuela blocks access to the Tor network new Medium Normal ptdetector 9 months ago
1 2

Roadmap from October 2017 to September 2018

We put together a roadmap for 2017/18 in Berlin in September 2017, refined it at the Tor meeting in Montreal in October 2017, and updated it at a team-internal meeting in Aberdeen in April 2018. The following contains a very short version of goals for the time until September 2018 and will be updated over time:

Short-term goals (Q4/2017)

  1. Update all code to use Java 8 features (M; 30% of 30% done, deferred)
  2. Switch ExoneraTor and metrics-web from Tomcat to embedded Jetty, and harmonize directory structures (M; 100% done)
  1. Deploy better notification system for operational issues (M; 30% of 30% done, deferred)
  2. Make sure that each service has at least two operators (M; 30% done)
  1. Add web server logs as new data source (M; 100% done)
  1. Provide metrics timeline events as both a table on Tor Metrics pages and as an RSS/Atom feed that is also syndicated via Twitter to increase community engagement (M; 60% done)
  1. Make Atlas part of the Tor Metrics website (M; 100% done)
  2. Make Compass part of Atlas in order to provide aggregated search results and details pages on Atlas and to finally shut down Compass (M; 100% done)
  3. Resolve ExoneraTor database slowness (M; 25% of 25% done, deferred)
  1. Extend Onionoo to use JNDI for rDNS lookups (M; 80% done)

  1. Add OONI graphs to Tor Metrics based on pre-aggregated data from vanilla Tor test and bridge reachability test (M; 40% done)
  2. Add IPv6 relay graphs to Tor Metrics based on existing descriptor contents (M; 100% done)
  3. Add a few more performance graphs based on existing OnionPerf data (M; 100% done)
  1. Rename Tor Metrics components to make them easier to understand for people outside of the team (M; 45% of 45% done, deferred)

Medium-term goals (until Q3/2018)

  1. Document aggregated statistics files better (Sponsor 13) (8/5 L; 50% of 80% done)
  2. Put external research data on the website, including Rob's phantomtrain OnionPerf data and Yixin's BGP monitoring data (M; 30% done)
  1. Re-process bridge descriptor tarballs to retain “contact” lines in server descriptors and “fingerprint” lines in statuses (M; 25% of 25% done, deferred)
  2. Support PrivCount development and integrate its data as successor to statistics reported by relays and bridges (M; 80% done)
  3. Help the Core Tor and Tor Browser teams with ongoing measurements (M; 80% done)
  1. Document the Tor Metrics system/pipeline, including explicitly writing down our requirements (Sponsor 13) (4/5 L; 10% of 80% done)

Burndown Chart

Open Tickets

The following table lists all open tickets, from recently modified to not touched in years, of products that are maintained by Metrics Team people or otherwise related. Not all of these products are actively maintained, so be sure to reach out to the team before starting to hack on any of these and also take a look at the Volunteer's Guide. Also note that not all metrics-related tools use Tor's Trac as their bug tracker, so you might also want to ask for bug trackers of other metrics tools.

Results (1 - 20 of 310)

1 2 3 4 5 6 7 8 9 10 11
Ticket Summary Component Status Owner Priority Severity Created Modified Reporter
#30260 Default date picker to latest available date Metrics/ExoneraTor new metrics-team Medium Normal 12 hours ago 12 hours ago cypherpunks
#26597 Investigate and document additional overhead for first hop when not using guards Metrics/Onionperf assigned metrics-team Medium Normal 10 months ago 12 hours ago irl
#29374 Analysis files sometimes present negative numbers in the payload_progress field Metrics/Onionperf new metrics-team Medium Normal 2 months ago 13 hours ago irl
#29624 New version of exit list format Metrics/Exit Scanner needs_revision irl Medium Normal 8 weeks ago 13 hours ago irl
#30218 Add bandwidth files archiving to CollecTor Metrics/CollecTor new metrics-team Medium Normal 6 days ago 13 hours ago irl
#29366 Persistent Onion service address Metrics/Onionperf assigned metrics-team Medium Normal 2 months ago 16 hours ago irl
#30217 Extend CollecTor filesystem protocol for bandwidth files Metrics/CollecTor new metrics-team Medium Normal 6 days ago 26 hours ago irl
#30216 Add bandwidth file parser to metrics-lib Metrics/Library needs_review karsten High Normal 6 days ago 3 days ago irl
#29787 Enumerate possible failure cases and include failure information in .tpf output Metrics/Onionperf new metrics-team Medium Normal 6 weeks ago 5 days ago karsten
#30238 OnionPerf json analysis file is different than the one recreated from logs Metrics/Onionperf new metrics-team Medium Normal 5 days ago 5 days ago acute
#21378 Archive bwauth bandwidth files Metrics/CollecTor assigned metrics-team Medium Normal 2 years ago 6 days ago tom
#29772 Plot nearly worst-case bandwidth when downloading from [public|onion] server Metrics/Website needs_review metrics-team Medium Normal 6 weeks ago 6 days ago karsten
#30219 Add Tom's bandwidth file archive to CollecTor Metrics/CollecTor new metrics-team Medium Normal 6 days ago 6 days ago irl
#28403 Link to bandwidth files from Consensus Health Metrics/Consensus Health new tom Medium Normal 5 months ago 7 days ago teor
#29315 Write down guidelines for adding new stats Metrics/Website needs_revision karsten Very High Normal 3 months ago 8 days ago karsten
#29773 Plot nearly worst-case circuit round-trip latencies to [public|onion] server Metrics/Website needs_revision metrics-team Medium Normal 6 weeks ago 8 days ago karsten
#29425 Write integration tests for data-processing modules Metrics/Statistics needs_revision karsten Medium Normal 2 months ago 8 days ago karsten
#21087 Separate truncated descriptor(s) from next complete descriptor Metrics/CollecTor accepted wulder Medium Normal 2 years ago 13 days ago atagar
#30096 rougmnvswfsmd4dq.onion connects subressources from non .onion Metrics/Relay Search new metrics-team Very Low Trivial 2 weeks ago 13 days ago cypherpunks
#29837 Include Tor Browser data from Google Play Metrics/Website new metrics-team Medium Normal 5 weeks ago 2 weeks ago sysrqb
1 2 3 4 5 6 7 8 9 10 11

Attachments (12)

Download all attachments as: .zip