CryptoServers

Tor relay & exit hosting in Romania

Tor relays, bridges and exits on a network that publishes its abuse posture and won't pull the plug after one boilerplate notice.

No KYC DMCA ignored Crypto only 60-second deploy
1 Tbps
DDoS absorption
41s
Median deploy
Bucharest (RO-BUH)
Datacenter
$26.99
Entry plan / month
Why Romania

The Romania case for Tor relay & exit hosting

Romania is an EU member but the Constitutional Court has struck down data-retention legislation twice (2009 and 2014), holding that bulk retention violates the Romanian constitution. The result is a unique posture inside the EU: full GDPR rights without mandatory traffic logging. Bucharest network is well-peered with Eastern Europe, has competitive bandwidth pricing, and tolerates DMCA-weighted workloads better than most western European jurisdictions. Common pick for seedboxes, scraping infrastructure, and Tor relays.

Cryptoservers explicitly allows Tor relays, including exit nodes. We respond to legitimate abuse (CSAM, credible threats, phishing) within 48 hours; everything else stays up. Each location publishes its peering and the upstream carriers it announces under our ASN, so you can pick a relay home that won't disappear behind a forwarded DMCA email.

Workload alignment

What Tor relay & exit hosting gets from Romania

Tor exits are allowed, not just tolerated. Relays included by default in our anycast scrubbing fabric.
1 Tbps DDoS absorption — exits draw the traffic that VPNs draw, plus reflection probes.
IPv4 + /64 IPv6 on every plan. Ed25519 SSH keys; no password auth on our side.
48-hour abuse response window. CSAM and credible-threat content excepted (acted on within 4 hours).
No bandwidth re-billing on overage — you stay on the plan you ordered.
Sysadmin FAQ

Tor relay & exit hosting in Romania — questions answered

Are exits really allowed in Romania, or just unaccompanied silence?
Allowed in writing — see our /aup/. Exits run today across all four jurisdictions; abuse posture is public on /abuse/. We don't require notification before bringing one up, but we appreciate the heads-up so we can pre-empt support tickets if a downstream carrier escalates.
How much bandwidth does a meaningful Tor relay need?
A guard at 10 MB/s sustained moves about 25 TB/month; an exit at the same rate pulls 30–40 TB once you factor in the reverse-path traffic. All our VPS plans ship with unmetered uplinks (1–10 Gbps depending on tier); relays don't hit overage.
What happens when a downstream carrier complains about my exit?
We forward the complaint to your account email with our standard "Tor exit boilerplate" already attached. You ack within 48 hours; we don't take action unless the complaint is CSAM or a credible imminent threat. Same path as any other abuse contact — just a different reply template.
Can I run a hidden service (.onion) on the same node?
Yes. Hidden services don't generate abuse mail (they're inbound from the Tor network, not the open internet) so they're actually a softer load profile than relays or exits.
Do you publish your ASN, peers, and downstream carriers?
Yes — see /network/. AS59264 in Switzerland and Romania, mixed transit elsewhere; full peering matrix is public. You can trace from your own ISP to verify the path lands locally.

Deploy Tor relay & exit hosting in Romania

From $26.99/month, paid in crypto, no email or ID required.