Tor Relays :: PlebsTogetherStrong

View Relay "PlebsTogetherStrong"

Family: 1 relay | [email protected] | AS197540 | Germany | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Fast, Running, Valid (3)
BW Verified: 5/6 BW Auths Measured 78 Kbit/s Median
Stability: Not Overloaded | UP 4d 15h 22m ago | UP 49% (1M)

Reachability: IPv4: 9/9 | v6: 7/7 (Directory Auths)
First Seen: 1w 2d 18h ago
BW Weight: 0.01% of Network | 78 Mbit/s Observed By Relay
Version: 0.4.8.21 Recommended

Issues Detected:

Guard: WFU below threshold : Weighted Fractional Uptime 59.6% 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 7.8 days is below 8 days requirement (0.2 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.
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).
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: WFU below threshold : WFU 59.6% 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.
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: v2202512328052422856.supersrv.de
152.53.49.154:9001
[2a0a:4cc0:80:178b:c85e:45ff:fec4:a4cd]:9001

Reachability (Directory Authorities)

IPv4: 9/9
IPv6: 7/7 (2 don't test)

Location

Country: Germany
Interactive Map: View on Interactive Map

Autonomous System

AS Number: AS197540
AS Name: netcup GmbH (BGP.tools)

Flags and Eligibility

Current Flags (3): Fast, Running, Valid

Eligibility Flag Vote Details

Flag	Metric	Status	Relay Value	Threshold Required
Guard	WFU	Below	59.6% (DA)	≥98% (all authorities)
	Time Known	Below (need 0.2 more days)	7.8 days (DA)	≥8 days (all authorities)
	Bandwidth	Meets (≥2 MB/s)	78.2 Mbit/s (R)	≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s
Stable	MTBF	Below	8 days (DA)	≥26.6d - 45.4d (varies)
Stable	Uptime	Below	4.6d (R)	≥19.1d - 19.7d (varies)
Fast	Speed	Meets (≥100 KB/s)	78.2 Mbit/s (R)	≥800.0 Kbit/s (guarantee) OR top 7/8
HSDir	WFU	Below	59.6% (DA)	≥98.0%
HSDir	Time Known	Below	7.8 days (DA)	≥1.0d (most) / 9.9d (max)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-01-10 04:46:16).

Last fetch was at Sat, 10 Jan 2026 04:47:26 GMT.

Nickname

PlebsTogetherStrong

Fingerprint

A349EB0E33F0FF20BFFE149497BAEC525D46237E

AROI (?)

none

Contact

[email protected]

IPv4 Exit Policy Summary

reject: 
  1-65535

IPv6 Exit Policy Summary

none

Exit Policy

reject *:*

Effective Family Member: 1

A349EB0E33F0FF20BFFE149497BAEC525D46237E

Alleged Family Members: 0

none

Indirect Family Members: 0

none

Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit): 78.21 Mbit/s | 78.21 Mbit/s| 167.77 Mbit/s| 209.72 Mbit/s Measured
Network Participation (Consensus Weight | Guard | Middle | Exit): 0.01% | N/A | 0.02% | N/A
OR Address: v2202512328052422856.supersrv.de | 152.53.49.154:9001, [2a0a:4cc0:80:178b:c85e:45ff:fec4:a4cd]:9001
Exit Address: none
Dir Address: none
Country: Germany
Interactive Map: View on Interactive Map
Autonomous System (AS Number | AS Name): AS197540 | netcup GmbH (BGP.tools)
Flags: 3: Fast Running Valid
Flag Uptime (1M/6M/1Y/5Y): 48.6%/—/—/—
Uptime (1M/6M/1Y/5Y): 49.2%/0.0%/0.0%/0.0%
Uptime / Downtime: UP 4d 15h 22m ago
Seen (First | Last): 1w 2d 18h ago (2025-12-31 10:00:00) | 1h 54m 51s ago (2026-01-10 03:00:00)
Last Restarted: 4d 15h 30m ago (2026-01-05 13:24:41)
Last Changed Address or Port: 2025-12-31 10:00:00
Hibernating: No
Platform (Short | Long): Linux | Tor 0.4.8.21 on Linux
Version (Running | Recommended | Status): 0.4.8.21 | Yes | recommended

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-01-10 04:46:16).

Consensus Status (need ≥5/9): In Consensus — 9/9 authorities voted.
Flag Eligibility (need ≥5/9 for flag): Guard: 0/9 | Stable: 1/9 | Fast: 9/9 | HSDir: 0/9 | Running: 9/9 | Valid: 9/9 | V2Dir: 9/9
Reachability: IPv4: 9/9 | IPv6: 7/7 (2 don't test)
Consensus Weight (Dir. Auth.): Median: 78.2 Kbit/s | Min: 63.2 Kbit/s | Max: 144.0 Kbit/s [Warning] High deviation
Identified Issues:
- Guard: WFU below threshold: Weighted Fractional Uptime 59.6% 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 7.8 days is below 8 days requirement (0.2 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.
- 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).
- 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: WFU below threshold: WFU 59.6% 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.
- 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.

Summary: Your Relay vs Consensus

Green = meets threshold, Red = below threshold, Yellow = partial.

Metric	Dir Auth Measured	Dir Auth Threshold	Status
In Consensus (Dir. Auth.)	9/9 authorities	≥5/9 (majority)	IN CONSENSUS
Running (IPv4 Reachable)	9/9 authorities reached this relay	≥5/9 (majority)	RUNNING
Valid	9/9 (Running + Valid Descriptor)	≥5/9 (majority)	VALID
Consensus Weight (Dir. Auth.)	78.2 Kbit/s (median)	N/A (no threshold, used for path selection)	—
Guard WFU (Dir. Auth., guard-wfu)	59.6%	≥98% (all authorities)	BELOW - cannot get Guard
Guard TK (Dir. Auth., tk)	7.8 days	≥8 days (all authorities)	BELOW - need 0.2 more days
Guard BW (Relay Reported)	78.2 Mbit/s	≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s	MEETS - ≥2 MB/s guarantee
Stable Uptime (Relay Reported)	4.6d	≥19.1d - 19.7d (typical)	BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf)	8 days	≥26.6d - 45.4d (typical) [Stricter] moria1: ≥376.2d	BELOW - 1/9
Fast Speed (Relay Reported)	78.2 Mbit/s	≥800.0 Kbit/s (guarantee) OR ≥816.0 Kbit/s (typical) [Stricter] moria1: ≥8.4 Mbit/s	MEETS - ≥100 KB/s guarantee
HSDir WFU (Dir. Auth., wfu)	59.6%	≥98.0% (from all auths)	BELOW - 0/9
HSDir TK (Dir. Auth., tk)	7.8 days	≥1.0d (8/9 auths) [Stricter] moria1: ≥9.9d	BELOW - 0/9
IPv6 Reachable (Dir. Auth.)	7/7 tested	≥4/7 (majority)	REACHABLE

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	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	Y	Yes	Yes	Fast, Running, Valid	78.2 Mbit/s \| 816.0 Kbit/s	78.2 Mbit/s \| 224.0 Mbit/s OR 16.0 Mbit/s	59.6% \| 98%	7.8d \| 8d	3.4d \| 47.0d	4.6d \| 19.7d	59.6% \| 98.0%	7.8d \| 1.0d	2026-01-10 02:04:22	69.6 Kbit/s
dannenberg (DE)	Yes	Yes	N	Yes	Yes	Fast, Running, Valid	78.2 Mbit/s \| 816.0 Kbit/s	78.2 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	59.6% \| 98%	7.8d \| 8d	3.4d \| 35.7d	4.6d \| 20.2d	59.6% \| 98.0%	7.8d \| 1.0d	2026-01-10 02:04:22	78.2 Kbit/s
dizum (NL)	Yes	Yes	N	Yes	—	Fast, Running, Valid	78.2 Mbit/s \| 816.0 Kbit/s	78.2 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	59.6% \| 98%	7.8d \| 8d	3.4d \| 26.6d	4.6d \| 20.4d	59.6% \| 98.0%	7.8d \| 1.0d	2026-01-10 02:04:22	78.2 Kbit/s
faravahar (US)	Yes	Yes	N	Yes	Yes	Fast, Running, Valid	78.2 Mbit/s \| 816.0 Kbit/s	78.2 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	60.9% \| 98%	7.6d \| 8d	3.4d \| 41.9d	4.6d \| 19.1d	60.9% \| 98.0%	7.6d \| 1.0d	2026-01-10 02:04:22	78.2 Kbit/s
gabelmoo (DE)	Yes	Yes	Y	Yes	Yes	Fast, Running, Valid	78.2 Mbit/s \| 816.0 Kbit/s	78.2 Mbit/s \| 288.0 Mbit/s OR 16.0 Mbit/s	59.6% \| 98%	7.8d \| 8d	3.4d \| 45.4d	4.6d \| 19.6d	59.6% \| 98.0%	7.8d \| 1.0d	2026-01-10 02:04:22	144.0 Kbit/s
longclaw (US)	Yes	Yes	Y	Yes	—	Fast, Running, Valid	78.2 Mbit/s \| 816.0 Kbit/s	78.2 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	60.9% \| 98%	7.6d \| 8d	3.4d \| 48.7d	4.6d \| 19.5d	60.9% \| 98.0%	7.6d \| 1.0d	2026-01-10 02:04:22	78.2 Kbit/s
maatuska (SE)	Yes	Yes	Y	Yes	Yes	Fast, Running, Valid	78.2 Mbit/s \| 816.0 Kbit/s	78.2 Mbit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	59.6% \| 98%	7.8d \| 8d	3.4d \| 42.3d	4.6d \| 19.4d	59.6% \| 98.0%	7.8d \| 1.0d	2026-01-10 02:04:22	96.0 Kbit/s
moria1 (US)	Yes	Yes	Y	Yes	Yes	Fast, Running, Stable, Valid	78.2 Mbit/s \| 8.4 Mbit/s	78.2 Mbit/s \| 232.0 Mbit/s OR 16.0 Mbit/s	60.2% \| 98%	6.1d \| 8d	5607.0d \| 376.2d	4.6d \| 20.4d	60.2% \| 98.0%	6.1d \| 9.9d	2026-01-10 02:04:22	128.0 Kbit/s
tor26 (AT)	Yes	Yes	Y	Yes	Yes	Fast, Running, Valid	78.2 Mbit/s \| 816.0 Kbit/s	78.2 Mbit/s \| 272.0 Mbit/s OR 16.0 Mbit/s	60.8% \| 98%	7.6d \| 8d	3.4d \| 51.8d	4.6d \| 19.7d	60.8% \| 98.0%	7.6d \| 1.0d	2026-01-10 02:04:22	63.2 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). This is your relay's self-reported uptime from its 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.