en
Tor Bridge Bandwidth Economics and Contribution Analysis
Running a Tor bridge is an act of technical altruism - contributing network infrastructure to help users in censored regions access the free internet. Understanding the actual bandwidth consumption, costs, and network contribution of a bridge allows operators to make informed decisions about relay configuration, VPS plan selection, and operational budgets. Tor bridges - unlike exit relays - handle traffic only within the Tor network, routing encrypted data between clients and the Tor network. Their bandwidth consumption depends on how many clients connect and how actively they use the bridge, with usage concentrated among users in countries with active censorship. This guide provides concrete data on bridge bandwidth usage and how to estimate your operational costs and network contribution.
Need this done for your project?
We implement, you ship. Async, documented, done in days.
How Bridge Bandwidth Is Consumed
Tor bridge bandwidth is consumed when users connect to the bridge and route traffic through it. Unlike exit relays (where all traffic is user-originated internet traffic), bridge traffic is fully encrypted Tor protocol data - it enters from clients and exits toward the Tor network (toward guard relays or other relays in the circuit). Bandwidth consumption factors: (1) number of simultaneous circuits through the bridge, (2) the bandwidth of user connections (Tor circuits are limited, typically 1-10 Mbit/s per circuit, but many circuits share the bridge's total bandwidth), (3) the bridge's configured bandwidth limits (BandwidthRate and BandwidthBurst in torrc), (4) whether the bridge is listed in BridgeDB (public bridges receive more connections than private bridges shared with a small number of users). A publicly listed obfs4 bridge with no bandwidth limits on a well-connected VPS typically serves 50-200 active users and uses 50-200 Mbit/s of sustained bandwidth.
Bandwidth Limits and VPS Plan Selection
Most VPS plans include a monthly bandwidth allocation (transfer cap). Bridge bandwidth consumption maps directly to this: a bridge using 50 Mbit/s sustained 24/7 would consume approximately 15TB/month (50 Mbit/s x 3600s x 24h x 30d / 8 = 16.2 TB). This exceeds most entry-level VPS plans. Practical configuration: set BandwidthRate in torrc to limit the bridge to a level within your plan. Setting BandwidthRate 10 MB (10 megabytes per second = 80 Mbit/s) and BandwidthBurst 20 MB limits the bridge to a manageable level. With a 5TB/month transfer VPS plan: configure the bridge at BandwidthRate 1.5 MB (12 Mbit/s sustained) to stay within the allocation. Tor's bandwidth limiting is per-second: BandwidthRate limits the average, BandwidthBurst allows short bursts above this rate.
Cost Modeling for Bridge Operation
Cost model for a bridge on Romania VPS Mini ($19.99/mo): The plan includes transfer allowance. At the configured bandwidth limit, calculate expected monthly transfer: if BandwidthRate is set to 1 MB/s (8 Mbit/s), monthly usage = 1 MB/s x 86400 x 30 = 2.592 TB/month. Verify this is within the plan's transfer allowance before configuring. For a bridge helping 20-50 active users: the $19.99/mo cost per user is approximately $0.40-$1.00/month for the operator - reasonable for altruistic bridge operation. For a higher-bandwidth bridge serving 200+ users: Iceland VPS II ($59.99/mo) or III ($79.99/mo) with larger transfer allocations. The Tor Project's bridge incentive programs (relay rewards) do not offer cash payments, but operators can take a tax deduction as charitable contribution to a nonprofit (in US) for the cost of running a bridge.
Measuring Your Bridge Contribution
Tor Metrics (metrics.torproject.org) publishes data on all public bridges including bandwidth consumed and client connections. Once your bridge is public and running for 48+ hours: search for your bridge fingerprint on Tor Metrics to see: consensus weight (how much traffic the network routes through you relative to other relays), bandwidth history (actual bandwidth measurements over time), and client connection estimates. Tor's relay search tool shows bridge contribution in context. A bridge at consensus weight 1000 in a network total of 10,000,000 contributes approximately 0.01% of total Tor capacity. Running multiple bridges (using multiple VPS plans) scales this proportionally. Private bridges (not listed in BridgeDB) do not appear on Tor Metrics but are still serving users who have their bridge address.
Optimizing Bridge Performance and Contribution
Configuration optimizations to maximize contribution within bandwidth limits: (1) configure NumCPUs to the number of physical CPU cores on the VPS to maximize Tor's parallelism, (2) enable IPv6 in addition to IPv4 (adding ORPort [::]:9001 in torrc) to serve users on IPv6-capable networks, (3) configure RelayBandwidthRate and RelayBandwidthBurst appropriately (RelayBandwidthRate is the cap for relay traffic specifically, separate from overall BandwidthRate), (4) enable the Tor bridge statistics (BridgeRecordUsageByCountry 1 in torrc) to see which countries your users connect from - this data informs whether your bridge is reaching its intended audience in censored countries. Review bridge statistics monthly to verify the bridge is actively used and contributing to users in target censored countries.
Related Services
Why Anubiz Host
100% async — no calls, no meetings
Delivered in days, not weeks
Full documentation included
Production-grade from day one
Security-first approach
Post-delivery support included
Ready to get started?
Skip the research. Tell us what you need, and we'll scope it, implement it, and hand it back — fully documented and production-ready.