Tor Metrics (Onionoo and CollecTor)

Tor Metrics (Onionoo and CollecTor)

Tor Metrics publishes measurement data about the public Tor network. Onionoo is a keyless JSON web service for relays and bridges that are currently running ("Onionoo is a web-based protocol to learn about currently running Tor relays and bridges."), and CollecTor archives the network's own descriptor and status documents ("CollecTor fetches data from various nodes and services in the public Tor network and makes it available to the world.").

Coverage

Onionoo serves summary, details, bandwidth, weights, clients and uptime documents for relays and bridges; "By default, all relays and bridges are included that have been running in the past week." CollecTor carries relay server descriptors, extra-info descriptors, network status consensuses and votes, microdescriptors, bridge descriptors and other document types: "recent descriptors that were published in the last 72 hours are available as plain text, and archived descriptors covering many years of Tor network history are available as compressed tarballs". Records describe relays and bridges, including the IP addresses, nicknames and contact strings their operators publish to the public Tor directory.

Verdict

Network-measurement data on the public Tor network: live relay and bridge status as keyless JSON (Onionoo) and archived descriptor and consensus files (CollecTor). The site's footer sets two different licences, and only the first covers the data: "Data on this site is freely available under a CC0 no copyright declaration: To the extent possible under law, the Tor Project has waived all copyright and related or neighboring rights in the data. Graphs are licensed under a Creative Commons Attribution 3.0 United States License." So the data is CC0 (recorded here) and the site's graphs are CC BY 3.0 US. The content is relay and bridge directory information that operators themselves publish to the public Tor directory, not onion-service content. Rate limits: Not stated; Onionoo asks that "Clients should include an \"Accept-Encoding: gzip\" header in their requests and handle gzip-compressed responses." and that "Clients should make use of the \"Last-Modified\" header of responses and include that timestamp in a \"If-Modified-Since\" header of subsequent requests." Signal Lab links only.