Tor Relays :: arbertDelroth

View Relay "arbertDelroth"

Family: 2 relays | [email protected] | AS13030 | Switzerland | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Fast, Running, V2Dir, Valid (4)
BW Verified: 5/6 BW Auths Measured 296 Kbit/s Median
Stability: Not Overloaded | DOWN 1d 7h 47m ago | UP 93% (1M)

Reachability: IPv4: 9/9 (Directory Auths)
First Seen: 5y 11mo 1w ago
BW Weight: 0.03% of Network | 240 Mbit/s Observed By Relay
Version: 0.4.8.16 Not Recommended

Issues Detected:

Guard: WFU below threshold : Weighted Fractional Uptime 97.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: 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 97.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.
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.
Tor version not recommended : Running Tor version 0.4.8.16 which is not on the recommended list.
Suggestion: Update to the latest stable Tor version. Outdated versions may have security vulnerabilities and could eventually be rejected by the network. See torproject.org/download for latest releases.

Connectivity and Location

Addresses

OR Address: 77.109.152.77:143
[2a02:168:6426:0:a283:780f:ec94:7c43]:143

Reachability (Directory Authorities)

IPv4: 9/9

Location

Country: Switzerland
Interactive Map: View on Interactive Map

Autonomous System

AS Number: AS13030
AS Name: Init7 (Switzerland) Ltd. (BGP.tools)

Flags and Eligibility

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

Eligibility Flag Vote Details

Flag	Metric	Status	Relay Value	Threshold Required
Guard	WFU	Below	97.7% (DA)	≥98% (all authorities)
	Time Known	Meets	15.3 days (DA)	≥8 days (all authorities)
	Bandwidth	Meets (≥2 MB/s)	240.3 Mbit/s (R)	≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s
Stable	MTBF	Below	15 days (DA)	≥26.6d - 45.4d (varies)
Stable	Uptime	Below	8.3d (R)	≥19.1d - 19.7d (varies)
Fast	Speed	Meets (≥100 KB/s)	240.3 Mbit/s (R)	≥800.0 Kbit/s (guarantee) OR top 7/8
HSDir	WFU	Below	97.7% (DA)	≥98.0%
HSDir	Time Known	Meets	15.3 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

arbertDelroth

Fingerprint

0432BEE829FCB155CE92CF418B7280F9849E12D0

AROI (?)

none

Contact

[email protected]

IPv4 Exit Policy Summary

reject: 
  1-65535

IPv6 Exit Policy Summary

none

Exit Policy

reject *:*

Effective Family Members: 2 (View)

0432BEE829FCB155CE92CF418B7280F9849E12D0
DD0C8EEC5CA402A9FA4478F10C31A440F71F6885

Alleged Family Members: 2

207AB36233C684A88C549ACF766A8D268CB4F796
75018790F33716C820745B8F7E27D08DAA3E3877

Indirect Family Members: 0

none

Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit): 240.30 Mbit/s | 240.30 Mbit/s| 8.59 Gbit/s| 8.59 Gbit/s Measured
Network Participation (Consensus Weight | Guard | Middle | Exit): 0.03% | N/A | N/A | N/A
OR Address: 77.109.152.77:143, [2a02:168:6426:0:a283:780f:ec94:7c43]:143
Exit Address: none
Dir Address: none
Country: Switzerland
Interactive Map: View on Interactive Map
Autonomous System (AS Number | AS Name): AS13030 | Init7 (Switzerland) Ltd. (BGP.tools)
Flags: 4: Fast Running V2Dir Valid
Flag Uptime (1M/6M/1Y/5Y): Match Overall Uptime (93.8%/97.9%/98.4%/81.4%)
Uptime (1M/6M/1Y/5Y): 93.8%/97.9%/98.4%/81.4%
Uptime / Downtime: DOWN 1d 7h 47m ago
Seen (First | Last): 5y 11mo 1w ago (2020-02-05 05:00:00) | 1d 7h 54m ago (2026-01-08 21:00:00)
Last Restarted: 1w 1d 7h ago (2026-01-01 21:21:16)
Last Changed Address or Port: 2026-01-01 22:00:00
Hibernating: No
Platform (Short | Long): Linux | Tor 0.4.8.16 on Linux
Version (Running | Recommended | Status): 0.4.8.16 | No | obsolete

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: 2/9 | Stable: 1/9 | Fast: 9/9 | HSDir: 2/9 | Running: 9/9 | Valid: 9/9 | V2Dir: 9/9
Reachability: IPv4: 9/9 | IPv6: 0/0
Consensus Weight (Dir. Auth.): Median: 296.0 Kbit/s | Min: 80.0 Kbit/s | Max: 688.0 Kbit/s [Warning] High deviation
Identified Issues:
- Guard: WFU below threshold: Weighted Fractional Uptime 97.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: 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 97.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.
- 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.
- Tor version not recommended: Running Tor version 0.4.8.16 which is not on the recommended list.
  - Suggestion: Update to the latest stable Tor version. Outdated versions may have security vulnerabilities and could eventually be rejected by the network. See torproject.org/download for latest releases.

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.)	296.0 Kbit/s (median)	N/A (no threshold, used for path selection)	—
Guard WFU (Dir. Auth., guard-wfu)	97.7%	≥98% (all authorities)	BELOW - cannot get Guard
Guard TK (Dir. Auth., tk)	15.3 days	≥8 days (all authorities)	MEETS
Guard BW (Relay Reported)	240.3 Mbit/s	≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s	MEETS - ≥2 MB/s guarantee
Stable Uptime (Relay Reported)	8.3d	≥19.1d - 19.7d (typical)	BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf)	15 days	≥26.6d - 45.4d (typical) [Stricter] moria1: ≥376.2d	BELOW - 1/9
Fast Speed (Relay Reported)	240.3 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)	97.7%	≥98.0% (from all auths)	BELOW - 2/9
HSDir TK (Dir. Auth., tk)	15.3 days	≥1.0d (8/9 auths) [Stricter] moria1: ≥9.9d	BELOW - 2/9
IPv6 Reachable (Dir. Auth.)	0/0 tested	≥1/0 (majority)	NOT TESTED

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	—	Fast, V2Dir, Valid	240.3 Mbit/s \| 816.0 Kbit/s	240.3 Mbit/s \| 224.0 Mbit/s OR 16.0 Mbit/s	97.7% \| 98%	15.3d \| 8d	0.3d \| 47.0d	8.3d \| 19.7d	97.7% \| 98.0%	15.3d \| 1.0d	2026-01-10 01:22:27	344.0 Kbit/s
dannenberg (DE)	Yes	Yes	N	Yes	—	Fast, V2Dir, Valid	240.3 Mbit/s \| 816.0 Kbit/s	240.3 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	97.6% \| 98%	14.9d \| 8d	0.3d \| 35.7d	8.3d \| 20.2d	97.6% \| 98.0%	14.9d \| 1.0d	2026-01-10 01:22:27	80.0 Kbit/s
dizum (NL)	Yes	Yes	N	Yes	—	Fast, Guard, HSDir, Running, Stable, V2Dir, Valid	240.3 Mbit/s \| 816.0 Kbit/s	240.3 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	28.5d \| 8d	25.1d \| 26.6d	8.3d \| 20.4d	100.0% \| 98.0%	28.5d \| 1.0d	2026-01-10 01:22:27	80.0 Kbit/s
faravahar (US)	Yes	Yes	N	Yes	—	Fast, V2Dir, Valid	240.3 Mbit/s \| 816.0 Kbit/s	240.3 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	97.7% \| 98%	15.0d \| 8d	0.3d \| 41.9d	8.3d \| 19.1d	97.7% \| 98.0%	15.0d \| 1.0d	2026-01-10 01:22:27	80.0 Kbit/s
gabelmoo (DE)	Yes	Yes	Y	Yes	—	Fast, V2Dir, Valid	240.3 Mbit/s \| 816.0 Kbit/s	240.3 Mbit/s \| 288.0 Mbit/s OR 16.0 Mbit/s	97.8% \| 98%	15.3d \| 8d	0.3d \| 45.4d	8.3d \| 19.6d	97.8% \| 98.0%	15.3d \| 1.0d	2026-01-10 01:22:27	688.0 Kbit/s
longclaw (US)	Yes	Yes	Y	Yes	—	Fast, Guard, HSDir, Running, Stable, V2Dir, Valid	240.3 Mbit/s \| 816.0 Kbit/s	240.3 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	28.9d \| 8d	27.0d \| 48.7d	8.3d \| 19.5d	100.0% \| 98.0%	28.9d \| 1.0d	2026-01-10 01:22:27	80.0 Kbit/s
maatuska (SE)	Yes	Yes	Y	Yes	—	Fast, V2Dir, Valid	240.3 Mbit/s \| 816.0 Kbit/s	240.3 Mbit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	97.7% \| 98%	15.7d \| 8d	0.3d \| 42.3d	8.3d \| 19.4d	97.7% \| 98.0%	15.7d \| 1.0d	2026-01-10 01:22:27	488.0 Kbit/s
moria1 (US)	Yes	Yes	Y	Yes	—	Fast, Stable, V2Dir, Valid	240.3 Mbit/s \| 8.4 Mbit/s	240.3 Mbit/s \| 232.0 Mbit/s OR 16.0 Mbit/s	96.4% \| 98%	9.7d \| 8d	20459.2d \| 376.2d	8.3d \| 20.4d	96.4% \| 98.0%	9.7d \| 9.9d	2026-01-10 01:22:27	296.0 Kbit/s
tor26 (AT)	Yes	Yes	Y	Yes	—	Fast, V2Dir, Valid	240.3 Mbit/s \| 816.0 Kbit/s	240.3 Mbit/s \| 272.0 Mbit/s OR 16.0 Mbit/s	97.8% \| 98%	15.0d \| 8d	0.3d \| 51.8d	8.3d \| 19.7d	97.8% \| 98.0%	15.0d \| 1.0d	2026-01-10 01:22:27	672.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). 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.