We estimate the number of users by analyzing the requests induced by clients to relays and bridges.
This graph shows the estimated number of directly-connecting clients; that is, it excludes clients connecting via bridges. These estimates are derived from the number of directory requests counted on directory authorities and mirrors. Relays resolve client IP addresses to country codes, so that graphs are available for most countries. Furthermore, it is possible to display indications of censorship events as obtained from an anomaly-based censorship-detection system (for more details, see this technical report). For further details see these questions and answers about user statistics.
The following events have been manually collected on this wiki page and might be related to the displayed graph.
|Dates||Places/Protocols||Description and Links|
|2017-01-15 to 2017-03-01||United Arab Emirates <OR> Relays Unknown||
Huge spike in relay users (400k+). An anonymous contributor suggests that it may be a botnet, based on the large number of hosts with an open SMB port in the UAE.
graph metrics-team thread Reddit thread comment about botnet
Decreased the rate limit on the meek-azure bridge to 2.0 MB/s, from 3.0 MB/s.
geoip and geoip6 databases updated to "January 4 2017 Maxmind GeoLite2 Country" (
|2016-12-21 to 2016-12-28||<OR> Relays Unknown||
Drop in relay users.
metrics-team thread thread continues
Tor Browser 6.5a6 is released. It fixes the
geoip and geoip6 databases updated to "December 7 2016 Maxmind GeoLite2 Country" (
Decreased the rate limit on the meek-amazon bridge to 2.0 MB/s, from 3.0 MB/s.
Default obfs4 bridge Lisbeth turns on timing obfuscation (
Tor Browser 6.5a4 is released. It changes the
blog post ticket
Tor Browser 6.0.6 is released, unbreaking meek on macOS 10.12 (Sierra). (See 2016-09-20 breaking event.)
blog post ticket
Default obfs4 bridges ndnop3 and ndnop5 turn on timing obfuscation (
mailing list post ticket
geoip and geoip6 databases updated to "November 3 2016 Maxmind GeoLite2 Country" (
Increased the rate limit on the meek-amazon bridge to 3.0 MB/s, from 1.0 MB/s.
Decreased the rate limit on the meek-amazon bridge to 1.0 MB/s, from 3.0 MB/s.
|2016-10-19 to 2016-11-10||meek||
Large decrease in meek users, perhaps caused by problems in Orbot 15.0.2 BETA 1 that were fixed in Orbot 15.2.0 RC8.
ticket initial email followup email Orbot mail
|2016-09-23 to 2016-11-28||obfs3||
Outage of default obfs3 bridges "Unnamed" and "Unnamed" (fingerprint AF9F66B7B04F8FF6F32D455F05135250A16543C9). (Start date not known for sure, though it must have been after 2016-09-23; discussed in non-archived tor-team email.)
This material is supported in part by the National Science Foundation under Grant No. CNS-0959138. Any opinions, finding, and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the National Science Foundation. "Tor" and the "Onion Logo" are registered trademarks of The Tor Project, Inc.. 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.