Tor Relays :: TorNode02

View Relay "TorNode02"

Fingerprint: `5424110BF0524432D80605090638D9CA63689BAC` | Family: 12 relays | mRtjR4JX6pgJ@protonmail.ch | AS197540 | Germany | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, Fast, Stable (4)
BW Verified: 4/6 BW Auths Measured 80 Kbit/s Median
Stability: Not Overloaded | UP 2d 18h 43m ago | UP 86% (1M)

Reachability: IPv4: 9/9 | v6: 8/8 (Directory Auths)
First Seen: 2y 7mo 3w ago
BW Weight: 0.01% of Network | 239 Mbit/s Observed By Relay
Version: 0.4.9.11 Recommended

Issues Detected:

HSDir: requires V2Dir (tunnelled-dir-server) : HSDir requires the relay to support tunnelled directory requests (V2Dir flag). This relay is missing V2Dir — the descriptor likely does not include tunnelled-dir-server, usually because DirCache 0 is set in torrc.
Suggestion: Remove DirCache 0 from torrc (DirCache is enabled by default in Tor ≥0.3.3). Restart Tor and verify the descriptor includes tunnelled-dir-server. You can check with: grep tunnelled-dir-server /var/lib/tor/cached-descriptors
High consensus weight deviation : Large variation in Consensus Weight values across authorities (see 'Cons Wt' column in Per-Authority Details below)
Suggestion: Consensus weight measurements vary significantly between authorities. This can affect traffic distribution. Ensure stable network connection and consistent bandwidth availability.

Connectivity and Location

Addresses

OR Address: v2202203171896184250.luckysrv.de
37.120.162.222:9001
[2a03:4000:6:3698::11e8]:9001

Reachability (Directory Authorities)

IPv4: 9/9
IPv6: 8/8 (1 don't test)

Location

Country: Germany
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS197540
AS Name: netcup GmbH (BGP.tools)
AS Rarity: Emerging (score: 1/5, 3.96% consensus weight, 179 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, Fast, Stable

Eligibility Flag Vote Details

Flag	Metric	Status	Relay Value	Threshold Required
Running	IPv4 Reachability	Meets (9/9 DA)	9/9 authorities reached relay	≥5/9 DA ORPort reachable
Running	IPv6 Reachability	Meets (8/8 DA)	8/8 tested authorities reached relay	≥5/8 tested (majority) (≥5/8 DA)
Valid	Descriptor	Meets (9/9 DA)	9/9 authorities assigned Valid	Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir	DirPort Available	Below (0/9 DA)	No DirPort, no tunnelled-dir-server (R)	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast	Speed	Meets (9/9 DA)	239.8 Mbit/s (R)	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s
Stable	MTBF	Partial (8/9 DA)	Median: 35.1d (8/9 DA above threshold) Min/Max: 11.2d / 1240.2d (9/9 DA, Voting / Total Eligible)	≥7.8d - 13.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥7051.8d
Stable	Uptime	Below (0/9 DA)	2.8d (R)	≥9.7d - 10.2d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (9/9 DA)	9/9 DA assigned Fast	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Meets (9/9 DA)	9/9 DA assigned Stable	≥7.8d - 13.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥7051.8d
	Prereq: V2Dir	Below (0/9 DA)	0/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Meets (7/9 DA)	Median: 98.8% (7/9 DA above threshold) Min/Max: 96.9% / 99.2% (9/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 32.0d (9/9 DA above threshold) Min/Max: 9.9d / 47.0d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.8d
Guard	Prereq: Fast	Meets (9/9 DA)	9/9 DA assigned Fast	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Meets (9/9 DA)	9/9 DA assigned Stable	≥7.8d - 13.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥7051.8d
	Prereq: V2Dir	Below (0/9 DA)	0/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Meets (7/9 DA)	Median: 98.8% (7/9 DA above threshold) Min/Max: 96.9% / 99.2% (9/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 32.0d (9/9 DA above threshold) Min/Max: 9.9d / 47.0d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Meets (9/9 DA)	239.8 Mbit/s (R)	≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-320.0 Mbit/s (≥5/9 DA)
Exit	Exit Policy	Below (0/9 DA)	Port 80: No \| Port 443: No (R)	Allows ≥1 /8 on ports 80 AND 443 (≥5/9 DA)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-08-24 00:01:31).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 239.79 Mbit/s
Advertised Bandwidth: 134.22 Mbit/s
Rate Limit: 134.22 Mbit/s
Burst Limit: 8.59 Gbit/s
Total Data: 1.4 PB (5 years)
1mo: 73 TB | 6mo: 245 TB | 1y: 414 TB | 5y: 1.4 PB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-08-24 00:01:31

Measured By: 4/6 Bandwidth Authorities
Not measured by: faravahar, longclaw
Median Measurement: 80.0 Kbit/s
Min / Max: 80.0 Kbit/s / 320.0 Kbit/s
Deviation: 240.0 Kbit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0129% of network (73th pctl) | Guard: N/A | Middle: 0.0382% (89th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics

Current Status: UP 2d 18h 43m ago
Overall Uptime (1M/6M/1Y/5Y): 87.0%/97.8%/98.9%/99.4%
Flag Uptime (1M/6M/1Y/5Y): Matches Overall Uptime (87.0%/97.8%/98.9%/99.4%)
Hibernating: No

Timestamps

First Seen: 2y 7mo 3w ago (2024-01-01 00:00:00)
Last Seen: 2h 2m 50s ago (2026-08-23 23:00:00)
Last Restarted: 2d 18h 43m ago (2026-08-21 06:19:29)
Last Changed Address: 2026-04-06 23:00:00

Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-08-23 16:00 UTC

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: mRtjR4JX6pgJ@protonmail.ch

Family Configuration

Family Support: MyFamily Only (12) — Legacy only. Consider migrating to Happy Families. | View Full Family (12)

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Members: 12

026F3D3E1FCEBEE056FBE3B3EB02449B913128D8
152F6D93677B89107D8E7FECC572EA0DA66B9D9C
239F4FB389E8AD2BC3192B5499FDF4A231AC08E2
3076723D196C84E233E57CA04EE7768A8E58EDAA
4D0245D2B6FB22F818DA5EC0C3A8338B7474CE07
5424110BF0524432D80605090638D9CA63689BAC (this relay)
54625FCF74D8311F3175349A1F879A0A298D5CA8
561D7A3E0D988E16760677B0F542E68CCA82B5FA
6B0C3EC11B67DE2ADB0B963F8FEEEF6B441AB868
6DB69445BDF2F67844582A7B4C02E46E0129AF35
ACFDA3EA9C6F153AE728FEB13C7110833959BDF5
C8C4DBB84AB4B2261EC3540C931DB28652DAD219

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

Platform: Linux — Tor 0.4.9.11 on Linux
Version: 0.4.9.11 — Recommended
Version Status: Recommended

Exit Health & Policy

DNS Health

Not an exit relay — DNS health testing does not apply.

IPv4 Exit Policy Summary

reject: 
  1-65535

Full Exit Policy

reject *:*

Last fetch was at Mon, 24 Aug 2026 01:02:45 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-08-24 00:01:31).

Per-Authority Details

Each cell shows: your measured value | authority threshold. Green = meets, red = below. Flags: green = all authorities agree, yellow = partial.

Authority	Running	Valid	Exit	MiddleOnly	BW Scan (Authority)	v4	v6	Flags	Fast (Relay\|T)	Guard BW (Relay\|Threshold)	Guard WFU (M\|T)	Guard TK (M\|T)	Stable MTBF (M\|T)	Stable Uptime (Relay\|T)	HSDir WFU (M\|T)	HSDir TK (M\|T)	Desc Published	Cons Wt (Authority)
bastet (US)	Yes	Yes	No	—	N	Yes	Yes	Running, Valid, Fast, Stable	239.8 Mbit/s \| 816.0 Kbit/s	239.8 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	99.0% \| 98%	44.2d \| 8d	35.1d \| 11.2d	2.8d \| 9.7d	99.0% \| 98.0%	44.2d \| 1.0d	2026-08-23 12:19:45	80.0 Kbit/s
dannenberg (DE)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, Fast, Stable	239.8 Mbit/s \| 816.0 Kbit/s	239.8 Mbit/s \| 320.0 Mbit/s OR 16.0 Mbit/s	98.8% \| 98%	32.0d \| 8d	29.8d \| 13.4d	2.8d \| 11.7d	98.8% \| 98.0%	32.0d \| 1.0d	2026-08-23 12:19:45	320.0 Kbit/s
dizum (NL)	Yes	Yes	No	—	N	Yes	Yes	Running, Valid, Fast, Stable	239.8 Mbit/s \| 816.0 Kbit/s	239.8 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	98.6% \| 98%	28.0d \| 8d	26.0d \| 12.8d	2.8d \| 10.0d	98.6% \| 98.0%	28.0d \| 1.0d	2026-08-23 12:19:45	80.0 Kbit/s
faravahar (US)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, Fast, Stable	239.8 Mbit/s \| 816.0 Kbit/s	239.8 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	98.6% \| 98%	27.1d \| 8d	25.1d \| 12.7d	2.8d \| 10.2d	98.6% \| 98.0%	27.1d \| 1.0d	2026-08-23 12:19:45	80.0 Kbit/s
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, Fast, Stable	239.8 Mbit/s \| 816.0 Kbit/s	239.8 Mbit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	99.1% \| 98%	42.7d \| 8d	35.7d \| 13.7d	2.8d \| 10.2d	99.1% \| 98.0%	42.7d \| 1.0d	2026-08-23 12:19:45	232.0 Kbit/s
longclaw (US)	Yes	Yes	No	—	Y	Yes	—	Running, Valid, Fast, Stable	239.8 Mbit/s \| 816.0 Kbit/s	239.8 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	99.2% \| 98%	47.0d \| 8d	43.8d \| 17.1d	2.8d \| 10.2d	99.2% \| 98.0%	47.0d \| 1.0d	2026-08-23 12:19:45	80.0 Kbit/s
maatuska (SE)	Yes	Yes	No	—	N	Yes	Yes	Running, Valid, Fast, Stable	239.8 Mbit/s \| 816.0 Kbit/s	239.8 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	97.4% \| 98%	18.5d \| 8d	11.2d \| 7.8d	2.8d \| 10.1d	97.4% \| 98.0%	18.5d \| 1.0d	2026-08-23 12:19:45	80.0 Kbit/s
moria1 (US)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, Fast, Stable	239.8 Mbit/s \| 8.4 Mbit/s	239.8 Mbit/s \| 208.0 Mbit/s OR 16.0 Mbit/s	96.9% \| 98%	9.9d \| 8d	1240.2d \| 7051.8d	2.8d \| 9.7d	96.9% \| 98.0%	9.9d \| 9.8d	2026-08-23 12:19:45	168.0 Kbit/s
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, Fast, Stable	239.8 Mbit/s \| 816.0 Kbit/s	239.8 Mbit/s \| 280.0 Mbit/s OR 16.0 Mbit/s	99.1% \| 98%	41.6d \| 8d	38.7d \| 13.5d	2.8d \| 10.6d	99.1% \| 98.0%	41.6d \| 1.0d	2026-08-23 12:19:45	296.0 Kbit/s

— = not tested/available • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known

Bandwidth Values Explained:
Relay Reported = Your relay's self-reported bandwidth from its descriptor (observed_bandwidth). Used for flag eligibility (Guard, Fast).
Authority Measured = Bandwidth measured by authority's sbws scanner. Used for consensus weight (path selection probability).
Why different? Authorities verify your reported bandwidth independently. 6 of 9 authorities run bandwidth scanners; 3 use relay-reported values directly.

Stable Uptime (Two Data Sources):
Relay Uptime = From Onionoo API (last_restarted field). Self-reported uptime from descriptor. Same value for all authorities.
Authority Threshold = From CollecTor vote files (flag-thresholds stable-uptime). Each authority may have different thresholds.
Why two sources? Vote files contain authority thresholds but not per-relay uptime values. Onionoo aggregates relay descriptors which include uptime.