Unmetered 1 and 10 Gbit/s ports · four European ports of call · no KYC. Pay in crypto: BTC, USDT, USDC, ETH, SOL, LTC, XMR
Language: English
Reserve a berth

Privacy infrastructure · Tor exit sizing

How much bandwidth does a Tor exit relay use, and can it fill 10 Gbps?

What one exit instance can push per the Tor Project, how many instances a 10 Gbit/s berth would take, why one IPv4 caps it, and how the numbers sit against the Tor network.

Last updated: · 7 min read

Quick answer

How much bandwidth does a Tor exit relay use, and can it fill 10 Gbps?

A Tor exit relay uses as much bandwidth as you let it: one tor instance pushes about 400 to 450 Mbit/s each way on a modern CPU. Filling a 10 Gbps port needs many instances and more than the one IPv4 we include, so one relay cannot, realistically. A Ravenquay Harbor 10G berth costs $356.25 per 30 days on an unmetered 10 Gbit/s port, paid in crypto with no KYC.

Tor exit sizing at Ravenquay

Per instance (AES-NI CPU)About 400–450 Mbit/s each way (Tor Project)
Relays per IPv48 (Tor Project relay requirements)
IPv4 per berthOne dedicated address included
RAM per exit instanceAt least 1.5 GB (Tor Project)
NetworkUnmetered means no monthly traffic quota and no overage bill: the port speed of your plan, 1 or 10 Gbit/s, is the only limit. Each server has one dedicated IPv4 address and an IPv6 /64
Port 25Port 25 is closed for outgoing mail on every server, permanently, to keep spam off the network; ports 465 and 587 toward mail providers stay open
Tor relaysTor exit relays are welcome, along with middle relays and bridges
Harbor 10G port10 Gbit/s
Harbor 10G price$356.25 per 30 days

How much bandwidth does one Tor exit instance use?

One tor instance is single-threaded for its heavy crypto work, so its throughput is capped by one CPU core. The Tor Project's relay requirements, read on 1 November 2026, put it at about 400 to 450 Mbit/s in each direction on a modern CPU with AES-NI. Check for aes in /proc/cpuinfo; the processors in every Ravenquay berth have it.

An exit sends roughly as much as it receives, so its average rate sets its monthly traffic. A fast exit, above 100 Mbit/s, also handles more than 100,000 concurrent connections, which is why a datacenter machine and not a home line is the right place for one.

How much data does that move in 30 days?

The figures below are arithmetic, not a measurement: data equals the average rate times 2,592,000 seconds, divided by 8, with 1 TB counted as 10^12 bytes. They are averages over a 30-day period, not peaks.

Average exit rate and data moved per 30 days (estimates)

Average rateData each way in 30 daysWhat it is
10 Mbit/s3.24 TBTor's floor for any relay
100 Mbit/s32.4 TBA fast exit in the Tor Project's terms
450 Mbit/s145.8 TBAbout one instance at full tilt on an AES-NI CPU
3.6 Gbit/s1,166 TBEight instances on one IPv4 (the per-IP ceiling)
10 Gbit/s3,240 TBA fully saturated 10 Gbit/s port

Calculation, not a measurement. Ravenquay publishes no throughput benchmark.

Can one exit fill a 10 Gbit/s port?

No, not from a single server as we sell it, and the limit is the IP address, not the port.

The Tor Project caps a public IPv4 address at eight tor relays. Each Ravenquay berth includes one dedicated IPv4. Eight instances at about 450 Mbit/s each come to roughly 3.6 Gbit/s each way, so one IPv4 tops out well below a 10 Gbit/s port. To fill 10 Gbit/s you would need about 22 instances (10,000 divided by 450), which means roughly three IPv4 addresses, more than the one we include. These are estimates, and Ravenquay does not promise additional IPv4 addresses.

On a Ravenquay berth, the IPv4 relay limit and per-instance throughput bound a Tor exit long before the port does. The 10 Gbit/s port of Harbor 10G still gives an exit all the headroom it can use, with none of it spent on a monthly quota: Unmetered means no monthly traffic quota and no overage bill: the port speed of your plan, 1 or 10 Gbit/s, is the only limit. Each server has one dedicated IPv4 address and an IPv6 /64.

Does the RAM or the traffic quota get in the way?

Neither on a Ravenquay berth. The Tor Project asks for at least 1.5 GB of RAM per exit instance. Eight instances need 12 GB, well inside the 128 GB DDR5 ECC of Harbor 10G and the 64 GB DDR4 ECC of the smallest berth.

Traffic is the usual ceiling elsewhere, but not here: an unmetered port has no monthly quota and no overage bill. If you still want a cap, the Tor Project's bandwidth FAQ uses RelayBandwidthRate for the average rate and AccountingMax with AccountingStart day 00:00 for a daily byte budget.

How do those numbers sit against the whole Tor network?

Modestly, which is the point of diversity. Per metrics.torproject.org, read on 1 November 2026 with data to 29 October 2026, the Tor network had about 9,220 running relays, roughly 2,750 of them flagged as exits, and about 1,210 Gbit/s of total advertised bandwidth. Relays carrying the Exit flag advertised around 386 Gbit/s of that.

A single berth's practical exit capacity, about 3.6 Gbit/s each way on one IPv4, is under 1% of the network's exit-flagged bandwidth. That is a useful contribution in a location the network is short of, not a bottleneck you need to worry about overrunning.

Exit-friendly hosts are scarce as well. Ravenquay checked 34 dedicated-server hosts on 30 October 2026: 4 allowed Tor exit relays, 1 more after a ticket, and 8 banned them.

How fast will a new exit actually run?

Not at full speed on day one. The Tor Project explains that a new relay's consensus weight ramps up over time: it gets almost no traffic for the first few days while bandwidth authorities measure it, then climbs over weeks. Plan for days, not minutes, before an exit reaches its capacity.

Start with the reduced exit policy. The Debian torrc manual says ReducedExitPolicy 1 allows about 65 ports while blocking most, which cuts abuse mail and keeps BitTorrent users off your exit. Tor's default exit policy already rejects port 25, and so does Ravenquay: Port 25 is closed for outgoing mail on every server, permanently, to keep spam off the network; ports 465 and 587 toward mail providers stay open For the full setup, read what you need to run a Tor relay.

Tor exit relay bandwidth: FAQ

Why can't one tor instance use a whole 10 Gbit/s port?

Each instance is limited by a single CPU core to about 450 Mbit/s each way. You run several instances to use more of the port, but the Tor Project caps a public IPv4 address at eight relays, and each berth includes one IPv4.

How much traffic will a 100 Mbit/s exit move a month?

About 32.4 TB each way over 30 days, as a plain calculation. On a Ravenquay berth that traffic is not metered or billed: the port speed is the only limit.

Can I get more IPv4 addresses for more exit instances?

Ravenquay includes one dedicated IPv4 per berth and does not promise more. Ask support before you order if extra addresses matter to your plan; they are not a published part of the service.

Which berth should I pick for a busy exit?

Harbor 10G: AMD EPYC 9254 (24 cores / 48 threads), 128 GB DDR5 ECC, 2 × 1.92 TB NVMe in RAID 1, unmetered 10 Gbit/s port, 1 IPv4 and an IPv6 /64, for $356.25 per 30 days. Its 10 Gbit/s port gives an exit all the headroom one IPv4 can use.

Run a busy exit on an unmetered 10 Gbit/s port

Harbor 10G: AMD EPYC 9254 (24 cores / 48 threads), 128 GB DDR5 ECC, 2 × 1.92 TB NVMe in RAID 1, unmetered 10 Gbit/s port, 1 IPv4 and an IPv6 /64, for $356.25 per 30 days. Exits welcome; pay in crypto, no KYC.

Sources (7)
  1. Relay requirements (throughput, RAM, 8 relays per IPv4) community.torproject.org/relay/relays-requirements — The Tor Project (read 2026-11-01)
  2. Exit relay setup and reduced exit policy community.torproject.org/relay/setup/exit — The Tor Project (read 2026-11-01)
  3. torrc(5): ReducedExitPolicy, AccountingMax, RelayBandwidthRate — Debian manpages (tor) (read 2026-11-01)
  4. Bandwidth limits and shaping support.torproject.org/relays/performance/bandwidth-limits — The Tor Project support portal (read 2026-11-01)
  5. The lifecycle of a new relay blog.torproject.org/lifecycle-of-a-new-relay — The Tor Project blog (read 2026-11-01)
  6. Tor network totals: relays and total advertised bandwidth metrics.torproject.org/networksize.html — Tor Metrics (data to 29 October 2026) (read 2026-11-01)
  7. Advertised bandwidth by relay flag (Exit flag) metrics.torproject.org/bandwidth-flags.html — Tor Metrics (data to 29 October 2026) (read 2026-11-01)

Unmetered from $72.62/30 days · no KYC

Reserve a berth