Tor relays are volunteer servers that carry encrypted traffic for Tor users around the world. The more running relays and bandwidth a region has, the more it contributes to the network. Spread matters too: when every relay sits on one provider, trouble at that provider, or pressure on it, takes them all down together.
The data comes from Pulse, which the community runs. It collects from Onionoo, part of Tor Metrics, every hour, and the page is regenerated every hour as well. Taiwan is shown by default, with other regions as reference points; switch between them with the region list below. The glossary at the end of the page explains the fields and flags. Each quarter's changes are written up in the quarterly reports.
Running relays<55–910–1920–49≥50IndiaReference (comparison table only)Select a region on the map to open its page. Germany, the Netherlands and the United States are outside the map and appear in the region list and comparison table as reference points.
Latest snapshot 2026-10-20 18:00 UTC
Running relays26+3vs 30 days ago
Bandwidth169.9MB/s+11.0 MB/svs 30 days ago
Networks (ASNs)110vs 30 days ago
Exit relays1+1vs 30 days ago
Cards show the latest snapshot against 30 days ago, with the trend over the last 60 days. An autonomous system (ASN) is a network run by one organisation, such as a telecom, a university or a cloud provider, and the more ASNs relays spread across the better. Exit relays connect users to ordinary websites, which see the exit relay's IP address.
Running relays and bandwidth
Running and stopped relays in the last snapshot of each day, and the total observed bandwidth of the running ones. A stopped relay appeared in the past week but is missing from the latest Tor network consensus, perhaps because it was shut down, lost its connection or is no longer maintained. Observed bandwidth is the most traffic a relay reports it can sustain, an upper bound on what it can carry.
RelaysRunningStoppedObserved bandwidth (MB/s)
Use and contribution
Tor Metrics estimates the average number of Tor clients online at the same time each day from the directory requests relays receive; it cannot count distinct people. Bridges are entry points that are not publicly listed in the Tor directory, used when connecting directly is blocked, so a high bridge share usually means direct connections to Tor are being blocked. Weight is the score Tor gives each relay from bandwidth measurements, and clients pick relays by weight, so a region's total weight roughly matches the share of Tor traffic passing through it. Setting the region's share of the world's users beside its weight shows the gap between the capacity it uses and the capacity it provides.
Concurrent users127,50930-day average
Via bridges1.7%30-day average
Share of world users3.6%30-day average
Share of network weight0.061%Latest snapshot
Average concurrent Tor clients connecting directly, per dayShare via bridges (%)
Tor Metrics estimates up to 2026-10-17
Diversity
The more autonomous systems (ASNs) the relays spread across, the less likely trouble at a single provider is to take them all down at once.
Guards are the first hop of a circuit, exits connect to the destination, and middles sit in between. A relay can hold more than one role.
Relay rolesGuardMiddleExit
Tor versions
Tor versions on running relays, with each day's bar adding up to 100%. The faster a new version's share grows after a release, the faster operators are keeping up.
Tor versions0.4.9.140.4.9.130.4.9.120.4.9.6Others
Versions in the latest snapshot
0.4.9.1412
0.4.9.137
0.4.9.124
0.4.9.61
0.4.9.111
0.4.9.101
Flags
V2Dir22Serves directory data for Tor clients to download
Fast21At least 100 KB/s, or in the top seven-eighths of the network
Stable18Up long enough to suit long-lived connections
Guard7Stable and fast enough to be picked as a circuit's entry
HSDir3Stores directory data for onion services (.onion sites)
BadExit1Judged faulty as an exit, so clients never use it as one
Exit1Exit policy allows common web ports such as 80 and 443
StaleDesc1Has not refreshed its descriptor in over 18 hours
Flags the directory authorities, the few servers that vote on the Tor network consensus every hour, assign from each relay's behaviour. What each flag means is written under its name. A relay can carry several, and Running and Valid, which every running relay has, are left out.
Across regions
Running relays in the latest snapshot. Each small chart shows the change over the last 60 days, indexed to 100 on the region's first day. All regions share one scale, so the size of the swings compares directly. In regions with few relays, one or two coming or going makes a visible swing. Open a region for its full charts.
Small-chart scale: 40 to 200. The dashed line is the first day's 100.
Use and contribution across regions
Relay counts are above. Weight comes from the latest snapshot; users and the bridge share are Tor Metrics averages over the last 30 days. Weight has been collected since October 2026. The reference region at the end has no running relays, so only users and the bridge share are listed.
Tor relay: a server that carries encrypted traffic for Tor users. A Tor connection passes through three relays in turn, an entry (guard), a middle and an exit, and each relay only knows the one before and the one after it
Snapshot: Pulse reads the state of every relay from Onionoo once an hour, and each reading is a snapshot. Times on the page are UTC
Running, stopped: a running relay is listed in the latest Tor network consensus. A stopped relay appeared in the past week but is missing from that consensus
Observed bandwidth: the most traffic a relay reports it could sustain over the past few days, an upper bound on what it can carry. Actual traffic is usually lower. MB/s is megabytes per second; multiply by 8 for roughly Mbps
Autonomous system (ASN): a group of networks run by one organisation under one routing policy, such as a telecom, a university or a cloud provider, each with its own AS number
Exit relay: the last relay on a connection, which reaches ordinary websites on the user's behalf. Websites see the exit relay's IP address, so exit operators handle more abuse complaints
Roles and flags: the roles chart follows Onionoo's probabilities, counting any relay with a probability above zero. Flags come from the directory authorities under stricter conditions, so a region's number of guards by role and by flag can differ
Directory authorities: a handful of servers run by people the Tor Project trusts, which vote every hour on the network consensus listing every relay and its flags
Tor version: for example 0.4.9.13. Versions sharing the first three parts belong to one series, and the last part is an update within it, usually with security fixes
Concurrent users: Tor Metrics' estimate of the average number of Tor clients connected at the same time during a day. One person may use several devices, or use Tor for only a few minutes a day, so this is not a count of people
Bridge: an entry relay that is not publicly listed in the Tor directory. Where connecting to Tor directly is blocked, users connect through bridges
Share of world users: the region's users, direct and through bridges, as a share of all Tor users
Share of network weight: Tor gives each relay a weight from bandwidth measurements (consensus weight), and clients pick relays by weight. The total weight of a region's relays roughly matches the share of Tor traffic passing through it
Reference region: a region without its own page, listed in a comparison table for contrast
How the numbers are calculated
Each day uses its last snapshot, not every relay seen during the day
Bandwidth is the sum of the observed bandwidth of running relays
Share of network weight is the sum of the running relays' consensus weight fractions, collected since October 2026
User estimates come from Tor Metrics, updated daily with a lag of two to three days; Tor Users in Taiwan explains the method and its limits
Relay roles follow Onionoo's probabilities: a relay counts as a guard, middle or exit when that probability is above zero
Days when collection was interrupted show as gaps in the charts, with nothing filled in
The raw data is available from the Pulse API; this page uses /api/summary