• Home
• Sources
• Statistics

Statistics files used on this website #

This page contains specifications of statistics files used on this website.

Parameters

All per-graph statistics files are available for download via an URL of the form:

https://metrics.torproject.org/identifier.csv

These URLs all support a set of optional parameters that can be used to further customize their content. Typically, these are start and end plus additional parameters as specified below. Including a parameter in a URL typically filters the resulting statistics file by the given parameter value. In reverse, omitting a parameter produces a larger statistics file that is not filtered by that parameter.

Columns

Each per-graph statistics file starts with a comment section, followed by a header line and then the actual data lines. Columns are pre-defined and specified further down below. The rule of thumb for columns is that neither the choice of parameters nor availability of data should affect the set of columns, but that only a code change can add, change, or remove a column. This rule of thumb is not yet implemented for all per-graph statistics files.

Applications must not rely on the order of columns, as this order may change when columns are removed. Instead, applications should refer to columns by their name. Applications should be able to handle newly added columns and fail gracefully in case of removed columns.

Changes

Changes to columns will be announced on this page at least a couple weeks in advance as well as on the tor-dev@ mailing list.

The following changes have been made in the past or are scheduled to become effective in the near future:

• February 28, 2018: Added per-graph CSV files to eventually replace pre-aggregated CSV files.
• May 29, 2018: Made all parameters of per-graph CSV files optional to support providing both pre-filtered and complete data sets.
• July 31, 2018: Announced pending changes to per-graph CSV files to become effective on August 15 and pre-aggregated CSV files to be removed by September 15.
• August 15, 2018: Made the first batch of changes to per-graph CSV files.
• September 15, 2018: Removed all pre-aggregated CSV files.
• October 28, 2018: Added and/or removed columns to Tor Browser downloads and updates by platform and Tor Browser downloads and updates by locale graphs.
• December 20, 2018: Removed source parameters and output rows with aggregates over all sources from Time to download files over Tor, Timeouts and failures of downloading files over Tor, Circuit build times, Circuit round-trip latencies graphs.
• December 20, 2018: Removed two graphs Total relay bandwidth and Consumed bandwidth by Exit/Guard flag combination, and updated the data format of the Advertised and consumed bandwidth by relay flags graph to cover all data previously contained in the first two graphs.
• May 29, 2019: Extended Circuit round-trip latencies graph to contain high/low values.
• June 2, 2019: Added Throughput graph.
• August 5, 2019: Re-added the Total relay bandwidth graph due to popular demand.
• October 2, 2019: Added Tor Browser updates by release channel graph.
• December 18, 2019: Added BridgeDB requests by requested transport and BridgeDB requests by distributor graphs.
• May 24, 2020: Included version 3 onion service measurements in Time to download files over Tor, Timeouts and failures of downloading files over Tor, Circuit build times, Circuit round-trip latencies graphs.
• May 24, 2020: Included partial downloads of larger file sizes in Time to download files over Tor graph.
• June 25, 2020: Removed filesize parameter from Timeouts and failures of downloading files over Tor graphs.

How to parse data in our CSV files

We use tidy/"long" data formats for our CSV files. For example, the following lines are contained in the userstats-bridge-combined.csv:

date,country,users,frac
2022-04-20,,69560,94
2022-04-21,,69068,87
2022-04-22,,70663,94
2022-04-23,,69647,92
2022-04-24,,69993,92
2022-04-25,,71348,92
2022-04-26,,69745,93
2022-04-27,,69497,94
2022-04-28,,69043,92
2022-04-29,,68440,89
2022-04-30,,68368,92
2022-05-01,,67647,93
2022-05-02,,69142,93
2022-05-03,,70942,90
2022-05-04,,68913,90
2022-05-05,,71004,92
2022-05-06,,68430,85
2022-05-07,,67643,93

The tidy format is more flexible, and somewhat easier to handle with statistics tools/languages like R or python. See also Hadley Wickham's Tidy Data paper

which is a really good read on this topic.

If you are familiar with programming in python you can easily parse our csv files with pandas:

  import pandas as pd

  df = pd.read_csv('userstats-bridge-combined-2022-04-20-all-2022-07-19.csv',  comment='#')

This will load the data in a dataframe From which you can easily manipulate columns and rows. Ex:

  date_th = '2022-05-01'

  df = df[df.date >= date_th]

The above snippet would filter the data in the table published after a defined date.

Users #

Relay users graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.
• country: Two-letter lower-case country code of clients to include in the file, or "all" for all clients.
• events: Ignored; only present for compatibility reasons with the corresponding graph.

Columns

• date: UTC date (YYYY-MM-DD) for which user numbers are estimated.
• country: Two-letter lower-case country code as found in a GeoIP database by resolving clients' IP addresses, or "??" if client IP addresses could not be resolved. If this column contains the empty string, all clients are included, regardless of their country code.
• users: Estimated number of clients.
• lower: Lower number of expected clients under the assumption that there has been no censorship event. If users < lower, a censorship-related event might have happened in this country on the given day. If this column contains the empty string, there are no expectations on the number of clients.
• upper: Upper number of expected clients under the assumption that there has been no release of censorship. If users > upper, a censorship-related event might have happened in this country on the given day. If this column contains the empty string, there are no expectations on the number of clients.
• frac: Fraction of relays in percent that the estimate is based on.

Bridge users by country graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.
• country: Two-letter lower-case country code of clients to include in the file, or "all" for all clients.

Columns

• date: UTC date (YYYY-MM-DD) for which user numbers are estimated.
• country: Two-letter lower-case country code as found in a GeoIP database by resolving clients' IP addresses, or "??" if client IP addresses could not be resolved. If this column contains the empty string, all clients are included, regardless of their country code.
• users: Estimated number of clients.
• frac: Fraction of bridges in percent that the estimate is based on.

Bridge users by transport graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.
• transport: Lower-case transport name to include in the file. Possible values include "obfs4", "websocket" for Flash proxy/websocket, "fte" for FTE, "conjure" for Conjure, "webtunnel" for WebTunnel, "!%3COR%3E" (percent encoding of "!<OR>") for any pluggable transport, "%3C??%3E" (percent encoding of "<??>") for unknown pluggable transport(s), or "%3COR%3E" (percent encoding of "<OR>") for the default OR protocol. Can be given multiple times.

Columns

• date: UTC date (YYYY-MM-DD) for which user numbers are estimated.
• transport: Transport name used by clients to connect to the Tor network using bridges. Examples are "obfs4", "websocket" for Flash proxy/websocket, "fte" for FTE, "!<OR>" for any pluggable transport, "<??>" for unknown pluggable transport(s), or "<OR>" for the default OR protocol.
• users: Estimated number of clients.
• frac: Fraction of bridges in percent that the estimate is based on.

Bridge users by country and transport graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.
• country: Two-letter lower-case country code of clients to include in the file, or "all" for all clients (which, however, produces the same file as the bridge users by country for "all" countries).

Columns

• date: UTC date (YYYY-MM-DD) for which user numbers are estimated.
• country: Two-letter lower-case country code as found in a GeoIP database by resolving clients' IP addresses, or "??" if client IP addresses could not be resolved.
• transport: Transport name used by clients to connect to the Tor network using bridges. Examples are "obfs4", "websocket" for Flash proxy/websocket, "fte" for FTE, "<??>" for unknown pluggable transport(s), or "<OR>" for the default OR protocol.
• high: Upper bound of estimated users from the given country and transport.
• low: Lower bound of estimated users from the given country and transport.
• frac: Fraction of bridges in percent that the estimate is based on.

Bridge users by IP version graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.
• version: IP version used by clients to connect to the Tor network using bridges, which can be either "v4" or "v6".

Columns

• date: UTC date (YYYY-MM-DD) for which user numbers are estimated.
• version: IP version used by clients to connect to the Tor network using bridges, which can be either "v4" or "v6". If this column contains the empty string, all clients are included, regardless of their IP version.
• users: Estimated number of clients.
• frac: Fraction of bridges in percent that the estimate is based on.

BridgeDB requests by requested transport graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.

Columns

• date: UTC date (YYYY-MM-DD) when requests were sent to BridgeDB.
• transport: Name of the pluggable transport protocol, which includes "obfs2", "obfs3", "obfs4", "scramblesuit", and "fte", and which will change in the future.
• requests: Approximate number of requests for the given transport.

BridgeDB requests by distributor graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.

Columns

• date: UTC date (YYYY-MM-DD) when requests were sent to BridgeDB.
• distributor: Name of BridgeDB's distributor, which includes "https", "email", and "moat", and which may change in the future.
• requests: Approximate number of requests for the given distributor.

Servers #

Relays and bridges graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.

Columns

• date: UTC date (YYYY-MM-DD) when relays or bridges have been listed as running.
• relays: Average number of relays.
• bridges: Average number of bridges.

Relays by relay flag graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.
• flag: Relay flag to include in the file. Examples are "Running", "Exit", "Fast", "Guard", "Stable", and "HSDir". This parameter can be given multiple times with different parameter values to include more relay numbers in the file.

Columns

• date: UTC date (YYYY-MM-DD) when relays have been listed as running.
• flag: Relay flag, which can be "Exit", "Fast", "Guard", "HSDir", "Fast", "Running", or "Stable".
• relays: Average number of relays.

Relays by tor version graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.

Columns

• date: UTC date (YYYY-MM-DD) when relays have been listed as running.
• version: First three dotted numbers of the Tor software version as reported by the relay. An example is "0.3.4".
• relays: Average number of relays.

Relays by platform graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.

Columns

• date: UTC date (YYYY-MM-DD) when relays have been listed as running.
• bsd: Average number of relays on *BSD.
• linux: Average number of relays on Linux.
• macos: Average number of relays on macOS.
• other: Average number of relays on another platform than Linux, *BSD, Windows, or macOS.
• windows: Average number of relays on Windows.

Relays by IP version graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.

Columns

• date: UTC date (YYYY-MM-DD) when relays have been listed as running.
• announced: Average number of relays that have announced an IPv6 address in their server descriptor.
• exiting: Average number of relays that have announced an IPv6 exit policy other than "reject 1-65535" in their server descriptor.
• reachable: Average number of relays with an IPv6 address that was confirmed as reachable by the directory authorities.
• total: Average number of relays.

Bridges by IP version graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.

Columns

• date: UTC date (YYYY-MM-DD) when bridges have been listed as running.
• announced: Average number of bridges that have announced an IPv6 address in their server descriptor.
• total: Average number of bridges.

Total consensus weights across bandwidth authorities graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.

Columns

• date: UTC date (YYYY-MM-DD) when relays have been listed as running.
• nickname: Bandwidth authority nickname, or the empty string in case of the consensus.
• totalcw: Total consensus weight of all running relays measured by the bandwidth authority or contained in the consensus.

Traffic #

Total relay bandwidth graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.

Columns

• date: UTC date (YYYY-MM-DD) that relays reported bandwidth data for.
• advbw: Total advertised bandwidth in Gbit/s that relays are capable to provide.
• bwhist: Total consumed bandwidth in Gbit/s as the average of written and read traffic of all relays.

Advertised and consumed bandwidth by relay flags graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.

Columns

• date: UTC date (YYYY-MM-DD) that relays reported bandwidth data for.
• have_guard_flag: Whether relays included in this row had the "Guard" relay flag assigned ("t") or not ("f").
• have_exit_flag: Whether relays included in this row had the "Exit" relay flag assigned and at the same time the "BadExit" not assigned ("t") or not ("f").
• advbw: Total advertised bandwidth in Gbit/s that relays are capable to provide.
• bwhist: Total consumed bandwidth in Gbit/s as the average of written and read traffic.

Advertised bandwidth by IP version graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.

Columns

• date: UTC date (YYYY-MM-DD) that relays reported bandwidth data for.
• exiting: Total advertised bandwidth in Gbit/s of all relays that have announced an IPv6 exit policy other than "reject 1-65535" in their server descriptor.
• reachable_exit: Total advertised bandwidth in Gbit/s of relays with the "Exit" relay flag and an IPv6 address that was confirmed as reachable by the directory authorities.
• reachable_guard: Total advertised bandwidth in Gbit/s of relays with the "Guard" relay flag and an IPv6 address that was confirmed as reachable by the directory authorities.
• total: Total advertised bandwidth in Gbit/s of all relays.
• total_exit: Total advertised bandwidth in Gbit/s of relays with the "Exit" relay flag.
• total_guard: Total advertised bandwidth in Gbit/s of relays with the "Guard" relay flag.

Advertised bandwidth distribution graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.
• p: Percentile to include in the file, with pre-defined possible values: 100, 99, 98, 97, 95, 91, 90, 80, 75, 70, 60, 50, 40, 30, 25, 20, 10, 9, 5, 3, 2, 1, 0. Can be given multiple times.

Columns

• date: UTC date (YYYY-MM-DD) that relays reported bandwidth data for.
• p: Percentile as value between 0 and 100.
• all: Advertised bandwidth in Gbit/s of the p-th percentile of all relays.
• exits: Advertised bandwidth in Gbit/s of the p-th percentile of relays with the "Exit" relay flag.

Advertised bandwidth of n-th fastest relays graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.
• n: Relay by advertised bandwidth to include in the file, with pre-defined possible values: 1, 2, 3, 5, 10, 20, 30, 50, 100, 200, 300, 500, 1000, 2000, 3000, 5000. Can be given multiple times.

Columns

• date: UTC date (YYYY-MM-DD) that relays reported bandwidth data for.
• n: Position of the relay in an ordered list of all advertised bandwidths, starting at 1 for the fastest relay in the network.
• all: Advertised bandwidth in Gbit/s of n-th fastest relay.
• exits: Advertised bandwidth in Gbit/s of n-th fastest relay with the "Exit" relay flag.

Bandwidth spent on answering directory requests graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.

Columns

• date: UTC date (YYYY-MM-DD) that relays reported bandwidth data for.
• dirread: Bandwidth in Gbit/s that directory mirrors have read when serving directory data.
• dirwrite: Bandwidth in Gbit/s that directory mirrors have written when serving directory data.
• dirauthread: Bandwidth in Gbit/s that directory authorities have read when serving directory data.
• dirauthwrite: Bandwidth in Gbit/s that directory authorities have written when serving directory data.

Fraction of connections used uni-/bidirectionally graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.

Columns

• date: UTC date (YYYY-MM-DD) for which statistics on uni-/bidirectional connection usage were reported.
• direction: Direction of reported fraction, which can be "read", "write", or "both" for connections classified as "mostly reading", "mostly writing", or "both reading and writing". Connections below the threshold have been removed from this statistics file entirely.
• q1: First quartile of fraction of connections.
• md: Median of fraction of connections.
• q3: Third quartile of fraction of connections.

Performance #

Time to download files over Tor graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.
• server: Either "public" for requests to a server on the public internet, or "onion" for requests to an onion server.
• filesize: Size of the completely or partially downloaded file in bytes, with pre-defined possible values: "50kb", "1mb", or "5mb".

Columns

• date: UTC date (YYYY-MM-DD) when download performance was measured.
• filesize: Size of the downloaded file in bytes.
• source: Name of the OnionPerf or Torperf service performing measurements.
• server: Either "public" if the request was made to a server on the public internet, or "onion" if the request was made to an onion server.
• q1: First quartile of time in seconds until receiving the number of bytes in filesize.
• md: Median of time in seconds until receiving the number of bytes in filesize.
• q3: Third quartile of time in seconds until receiving the number of bytes in filesize.

Timeouts and failures of downloading files over Tor graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.
• server: Either "public" for requests to a server on the public internet, or "onion" for requests to an onion server.

Columns

• date: UTC date (YYYY-MM-DD) when download performance was measured.
• source: Name of the OnionPerf or Torperf service performing measurements.
• server: Either "public" if the request was made to a server on the public internet, or "onion" if the request was made to an onion server.
• timeouts: Fraction of requests that timed out when attempting to download the static file over Tor.
• failures: Fraction of requests that failed when attempting to download the static file over Tor.

Circuit build times graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.

Columns

• date: UTC date (YYYY-MM-DD) when download performance was measured.
• source: Name of the OnionPerf or Torperf service performing measurements.
• position: Position in the circuit, from first to third hop.
• q1: First quartile of time in milliseconds until successfully extending the circuit to the given position.
• md: Median of time in milliseconds until successfully extending the circuit to the given position.
• q3: Third quartile of time in milliseconds until successfully extending the circuit to the given position.

Circuit round-trip latencies graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.
• server: Either "public" for requests to a server on the public internet, or "onion" for requests to an onion server.

Columns

• date: UTC date (YYYY-MM-DD) when download performance was measured.
• source: Name of the OnionPerf or Torperf service performing measurements.
• server: Either "public" if the request was made to a server on the public internet, or "onion" if the request was made to an onion server.
• low: Lowest time in milliseconds between sending the HTTP request and receiving the HTTP response header within 1.5 IQR of lower quartile (lower whisker in a boxplot).
• q1: First quartile of time in milliseconds between sending the HTTP request and receiving the HTTP response header.
• md: Median of time in milliseconds between sending the HTTP request and receiving the HTTP response header.
• q3: Third quartile of time in milliseconds between sending the HTTP request and receiving the HTTP response header.
• high: Highest time in milliseconds between sending the HTTP request and receiving the HTTP response header within 1.5 IQR of upper quartile (upper whisker in a boxplot).

Throughput graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.
• server: Either "public" for requests to a server on the public internet, or "onion" for requests to an onion server.

Columns

• date: UTC date (YYYY-MM-DD) when download performance was measured.
• source: Name of the OnionPerf or Torperf service performing measurements.
• server: Either "public" if the request was made to a server on the public internet, or "onion" if the request was made to an onion server.
• low: Lowest measured throughput in kilobits per second within 1.5 IQR of lower quartile (lower whisker in a boxplot).
• q1: First quartile of measured throughput in kilobits per second.
• md: Median of measured throughput in kilobits per second.
• q3: Third quartile of measured throughput in kilobits per second.
• high: Highest measured throughput in kilobits per second within 1.5 IQR of upper quartile (upper whisker in a boxplot).

Onion Services #

Unique .torify.net addresses (version 2 only) graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.

Columns

• date: UTC date (YYYY-MM-DD) when relays have been listed as running.
• onions: Estimated number of unique .torify.net addresses observed by onion-service directories.
• frac: Total network fraction of statistics reported by onion-service directories.

Unique .torify.net addresses (version 3 only) graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.

Columns

• date: UTC date (YYYY-MM-DD) when relays have been listed as running.
• onions: Estimated number of unique .torify.net addresses observed by onion-service directories.
• frac: Total network fraction of statistics reported by onion-service directories.

Onion-service traffic (versions 2) graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.

Columns

• date: UTC date (YYYY-MM-DD) when relays have been listed as running.
• relayed: Estimated bandwidth in Gbit/s relayed on rendezvous circuits as observed by rendezvous points.
• frac: Total network fraction of statistics reported by rendezvous points.

Onion-service traffic (versions 3) graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.

Columns

• date: UTC date (YYYY-MM-DD) when relays have been listed as running.
• relayed: Estimated bandwidth in Gbit/s relayed on rendezvous circuits as observed by rendezvous points.
• frac: Total network fraction of statistics reported by rendezvous points.

Applications #

Tor Browser downloads and updates graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.

Columns

• date: UTC date (YYYY-MM-DD) when requests to torproject.org web servers have been logged.
• initial_downloads: Number of Tor Browser initial downloads: GET requests to all sites with resource strings '%/torbrowser/%.exe', '%/torbrowser/%.dmg', and '%/torbrowser/%.tar.xz' and response code 200.
• signature_downloads: Number of Tor Browser signature downloads: GET requests to all sites with resource strings '%/torbrowser/%.exe.asc', '%/torbrowser/%.dmg.asc', and '%/torbrowser/%.tar.xz.asc' and response code 200.
• update_pings: Number of Tor Browser update pings: GET requests to all sites with resource strings '%/torbrowser/update\__/%' and response code 200.
• update_requests: Number of Tor Browser update requests: GET requests to all sites with resource strings '%/torbrowser/%.mar' and response code 302.

Tor Browser downloads and updates by platform graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.

Columns

• date: UTC date (YYYY-MM-DD) when requests to torproject.org web servers have been logged.
• platform: Platform, like "Linux", "macOS", or "Windows".
• initial_downloads: Number of Tor Browser initial downloads.
• update_pings: Number of Tor Browser update pings.

Tor Browser downloads and updates by locale graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.

Columns

• date: UTC date (YYYY-MM-DD) when requests to torproject.org web servers have been logged.
• locale: Locale, like "en-US" for English (United States), "de" for German, etc., and "??" for unrecognized locales.
• initial_downloads: Number of Tor Browser initial downloads.
• update_pings: Number of Tor Browser update pings.

Tor Browser updates by release channel graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.

Columns

• date: UTC date (YYYY-MM-DD) when requests to torproject.org web servers have been logged.
• channel: Release channel, like "r" for stable releases and "a" for alpha releases.
• update_pings: Number of Tor Browser update pings.
• update_requests: Number of Tor Browser update requests.

Tor Messenger downloads and updates graph data #

Parameters

• start: First UTC date (YYYY-MM-DD) to include in the file.
• end: Last UTC date (YYYY-MM-DD) to include in the file.

Columns

• log_date: UTC date (YYYY-MM-DD) when requests to torproject.org web servers have been logged.
• initial_downloads: Number of Tor Messenger initial downloads: GET requests to all sites with resource strings '%/tormessenger/%.exe', '%/tormessenger/%.dmg', and '%/tormessenger/%.tar.xz' and response code 200.
• update_pings: Number of Tor Messenger update pings: GET requests to all sites with resource strings '%/tormessenger/update\__/%' and response code 200.