Tor Relays :: whvger

View Relay "whvger"

Fingerprint: `FDAD785EA63CC2859C8F0AE21892701D3E9E5430` | Family: 1 relay | <whvger at quantentunnel dot de> | AS8881 | Germany | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, Fast (3)
BW Verified: 5/6 BW Auths Measured 76 Kbit/s Median
Stability: Not Overloaded | UP 6h 32m 33s ago

Reachability: IPv4: 9/9 (Directory Auths)
First Seen: 3d 12h 46m ago
BW Weight: 0.01% of Network | 76 Mbit/s Observed By Relay
Version: 0.4.9.6 Recommended

Issues Detected:

Guard: requires Stable flag : Guard flag requires having the Stable flag first
Suggestion: Get Stable flag by maintaining consistent uptime. Stable requires uptime and MTBF at or above network median (typically 2-3 weeks of stable running).
Guard: WFU below threshold : Weighted Fractional Uptime 85.7% is below 98% requirement
Suggestion: WFU measures recent uptime (recent downtime weighs more heavily). To improve: 1) Minimize restarts, 2) Use systemd with Restart=always, 3) Monitor for OOM kills, 4) Schedule updates during low-traffic periods.
Guard: Time Known below threshold : Time Known 0.6 days is below 8 days requirement (7.4 more days needed)
Suggestion: Time Known tracks how long authorities have observed your relay. This resets if: 1) Identity key changes, 2) Long downtime makes authorities forget you. Just keep running stably.
Not eligible for Stable flag : Uptime or MTBF below network median for most authorities
Suggestion: Stable flag requires uptime/MTBF at or above network median. Keep your relay running continuously for 2-3 weeks. Avoid restarts. Use reliable hardware and network connection.
HSDir: requires Stable flag : HSDir flag requires having the Stable flag first
Suggestion: Get Stable flag by maintaining consistent uptime. Stable requires uptime and MTBF at or above network median (typically 2-3 weeks of stable running). Avoid restarts.
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
HSDir: WFU below threshold : WFU 85.7% below 98% required for HSDir
Suggestion: HSDir requires ≥98% WFU, Stable flag, and Time Known ≥25 hours (or ~10 days for moria1). Improve uptime consistency.
HSDir: Time Known below threshold : Time Known 14.0 hours below 25 hours (dir-spec default)
Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.
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: i5C7461A0.versanet.de
92.116.97.160:9001

Reachability (Directory Authorities)

IPv4: 9/9

Location

Country: Germany
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS8881
AS Name: 1&1 Versatel GmbH (BGP.tools)
AS Rarity: Epic (score: 3/5, 0.05% consensus weight, 15 operators)

Flags and Eligibility

Current Flags (3): Running, Valid, Fast

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
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)	76.5 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	Below (1/9 DA)	Median: 0.6d (1/9 DA above threshold) Min/Max: 0.2d / 16882.3d (9/9 DA, Voting / Total Eligible)	≥38.3d - 62.2d (varies) (≥5/9 DA)
Stable	Uptime	Below (0/9 DA)	0.3d (R)	≥8.3d - 11.1d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (8/9 DA)	8/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	Below (1/9 DA)	1/9 DA assigned Stable	≥38.3d - 62.2d (varies) (≥5/9 DA)
	Prereq: V2Dir	Below (0/9 DA)	0/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Below (0/9 DA)	Median: 90.6% (0/9 DA above threshold) Min/Max: 85.7% / 94.1% (9/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Meets (7/9 DA)	Median: 3.1d (0/9 DA above threshold) Min/Max: 0.6d / 3.3d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.9d
Guard	Prereq: Fast	Meets (8/9 DA)	8/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	Below (1/9 DA)	1/9 DA assigned Stable	≥38.3d - 62.2d (varies) (≥5/9 DA)
	Prereq: V2Dir	Below (0/9 DA)	0/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Below (0/9 DA)	Median: 90.6% (0/9 DA above threshold) Min/Max: 85.7% / 94.1% (9/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Below (0/9 DA) (need 4.9 more days)	Median: 3.1d (0/9 DA above threshold) Min/Max: 0.6d / 3.3d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Meets (9/9 DA)	76.5 Mbit/s (R)	≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-312.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-04-20 10:15:08).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 76.46 Mbit/s
Advertised Bandwidth: 76.46 Mbit/s
Rate Limit: 83.89 Mbit/s
Burst Limit: 2.52 Gbit/s
Total Data: 169 GB (1 month)

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-04-20 10:15:08

Measured By: 5/6 Bandwidth Authorities
Not measured by: bastet
Median Measurement: 76.5 Kbit/s
Min / Max: 0 bit/s / 112.0 Kbit/s
Deviation: 112.0 Kbit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0064% of network (51th pctl) | Guard: N/A | Middle: 0.0193% (82th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics

Current Status: UP 6h 32m 33s ago
Overall Uptime (1M/6M/1Y/5Y): 0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y): Matches Overall Uptime (0.0%/0.0%/0.0%/0.0%)
Hibernating: No

Timestamps

First Seen: 3d 12h 46m ago (2026-04-16 22:00:00)
Last Seen: 1h 46m 39s ago (2026-04-20 09:00:00)
Last Restarted: 6h 32m 33s ago (2026-04-20 04:14:06)
Last Changed Address: 2026-04-20 02:00:00

Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-04-20 03:00 UTC

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: <whvger at quantentunnel dot de>

Family Configuration

Family Support: None — No family membership configured

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Member: 1

FDAD785EA63CC2859C8F0AE21892701D3E9E5430 (this relay)

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

Platform: Linux — Tor 0.4.9.6 on Linux
Version: 0.4.9.6 — 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, 20 Apr 2026 10:46:38 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-04-20 10:15:08).

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	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	—	Y	Yes	Running, Valid	76.5 Mbit/s \| 816.0 Kbit/s	76.5 Mbit/s \| 200.0 Mbit/s OR 16.0 Mbit/s	85.7% \| 98%	0.6d \| 8d	0.2d \| 62.2d	0.3d \| 8.3d	85.7% \| 98.0%	0.6d \| 1.0d	2026-04-17 08:45:18	—
dannenberg (DE)	Yes	Yes	No	—	N	Yes	Running, Valid, Fast	76.5 Mbit/s \| 816.0 Kbit/s	76.5 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	92.0% \| 98%	3.2d \| 8d	0.7d \| 38.3d	0.3d \| 11.1d	92.0% \| 98.0%	3.2d \| 1.0d	2026-04-20 04:29:06	76.5 Kbit/s
dizum (NL)	Yes	Yes	No	—	N	Yes	Running, Valid, Fast	76.5 Mbit/s \| 816.0 Kbit/s	76.5 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	90.6% \| 98%	3.3d \| 8d	0.5d \| 40.3d	0.3d \| 11.1d	90.6% \| 98.0%	3.3d \| 1.0d	2026-04-20 04:29:06	76.5 Kbit/s
faravahar (US)	Yes	Yes	No	—	N	Yes	Running, Valid, Fast	76.5 Mbit/s \| 816.0 Kbit/s	76.5 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	91.1% \| 98%	3.1d \| 8d	0.6d \| 61.2d	0.3d \| 11.1d	91.1% \| 98.0%	3.1d \| 1.0d	2026-04-20 04:29:06	76.5 Kbit/s
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid, Fast	76.5 Mbit/s \| 816.0 Kbit/s	76.5 Mbit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	89.3% \| 98%	3.3d \| 8d	0.5d \| 63.0d	0.3d \| 11.1d	89.3% \| 98.0%	3.3d \| 1.0d	2026-04-20 04:29:06	104.0 Kbit/s
longclaw (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, Fast	76.5 Mbit/s \| 816.0 Kbit/s	76.5 Mbit/s \| 240.0 Mbit/s OR 16.0 Mbit/s	91.2% \| 98%	3.1d \| 8d	0.6d \| 62.3d	0.3d \| 11.1d	91.2% \| 98.0%	3.1d \| 1.0d	2026-04-20 04:29:06	112.0 Kbit/s
maatuska (SE)	Yes	Yes	No	—	Y	Yes	Running, Valid, Fast	76.5 Mbit/s \| 816.0 Kbit/s	76.5 Mbit/s \| 312.0 Mbit/s OR 16.0 Mbit/s	94.1% \| 98%	2.4d \| 8d	0.8d \| 61.4d	0.3d \| 10.2d	94.1% \| 98.0%	2.4d \| 1.0d	2026-04-19 09:21:25	96.0 Kbit/s
moria1 (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, Fast, Stable	76.5 Mbit/s \| 8.4 Mbit/s	76.5 Mbit/s \| 216.0 Mbit/s OR 16.0 Mbit/s	89.8% \| 98%	3.0d \| 8d	16882.3d \| 303.7d	0.3d \| 11.0d	89.8% \| 98.0%	3.0d \| 9.9d	2026-04-20 04:29:06	65.6 Kbit/s
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Running, Valid, Fast	76.5 Mbit/s \| 816.0 Kbit/s	76.5 Mbit/s \| 288.0 Mbit/s OR 16.0 Mbit/s	90.6% \| 98%	3.1d \| 8d	0.5d \| 63.2d	0.3d \| 11.1d	90.6% \| 98.0%	3.1d \| 1.0d	2026-04-20 04:29:06	104.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.