Tor Relay Nodes

P2P Infrastructure

Volunteer-operated network nodes implementing the Tor onion routing protocol, providing anonymous multi-hop routing for internet traffic through guard (entry), middle, and exit relay roles. Each relay peels one layer of encryption, ensuring no single node knows both the origin and destination of traffic.

Community
Links
Visit Community

Details

License BSD-3-Clause (https://gitlab.torproject.org/tpo/core/tor)
Dev Status 🟢 Active
Dev Status Detail Released (production)
Owner The Tor Project, Inc. (nonprofit) / Volunteer operators worldwide
Country USA (Tor Project HQ, Cambridge MA) / Globally distributed
Start Year 2002
Stack C (core Tor daemon); Python (tooling and scripts)
Funding US State Department / OTF / NSF / private donations (Tor Project receives grants; relays operated by unpaid volunteers)
Last Investigated Mar 9, 2026

Use Case Domains

Platform Evolution & Sovereignty

Affordances

Self-hostable

P2P Infrastructure Attributes

Origins US Naval Research Lab onion routing research (Paul Syverson, Michael G. Reed, David Goldschlag, 1990s); EFF funded early development
Database N/A (routing infrastructure, no application data store)
Data Formats Arbitrary TCP streams (application-agnostic transport layer)
Mobile Support N/A (relay operator infrastructure, not an end-user app)
Web Support N/A
Native Apps Yes (CLI: torrc configuration; relay management tooling)
Terms Free to operate (volunteer bandwidth donation); no compensation for relay operators
Funds Tor Project budget ~$5M/year (grants from US State Dept, OTF, NSF, private donors); relay operators self-fund
Based On Onion routing (Paul Syverson et al., US NRL); inspired by earlier mix networks
P2P Architecture Onion routing (layered encryption, 3-hop circuit: guard → middle → exit)
Overlay Network Global (public relay directory maintained by directory authorities; bridges unlisted)
Content Addressing No (location-based routing, not content-addressed)
Local-First N/A (routing infrastructure; data passes through, not stored)
E2EE Yes — multi-layer onion encryption (each hop decrypts one layer; E2EE between client and exit for HTTPS traffic depends on application)
Byzantine Fault Tolerance No (probabilistic, not BFT; network trusts directory authority consensus)
Signature RSA-1024 (legacy) / Ed25519 (modern) — relay identity keys; TLS for transport
Permissions Exit policies (each relay operator configures exit policy rules); directory authority flags (Guard, Exit, Fast, Stable)
Protocol Maturity / Standardization De Facto Standard (Tor protocol is an open specification implemented by multiple clients; no formal standards body)
Infrastructure Function Anonymous routing; Censorship circumvention
Threat Model State-level censorship; Mass surveillance; Traffic analysis; DPI (Deep Packet Inspection); ISP-level blocking
Volunteer / Node Model Volunteer-operated (self-funded by operators); Hybrid (volunteer + foundation-operated bridges and some exit relays)
Traffic Visibility No content (encrypted payload only); No metadata between hops (each relay knows only previous and next hop, not origin and destination simultaneously)
Active Deployment Scale ~8,000 active relay nodes (July 2025); ~2,000 bridge relays; ~2.5M daily users; majority of traffic from Russia, Iran, USA