View Relay "ZoddyTor"

Family: 1 relay | [email protected] | AS1267 | Italy | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Fast, Running, Valid (3)
BW Verified
5/6 BW Auths Measured 14 Kbit/s Median
Stability
Not Overloaded | UP 23h 41m 1s ago | UP 98% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
2w 17h 55m ago
BW Weight
0.00% of Network | 17 Mbit/s Observed By Relay
Version
0.4.8.21 Recommended
Issues Detected:
  • Guard: WFU below threshold : Weighted Fractional Uptime 96.8% 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 96.8% 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
151.67.0.29:9001
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Italy Italy
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS1267
AS Name
WIND TRE S.P.A. (BGP.tools)

Flags and Eligibility

Current Flags (3): Fast, Running, Valid
Eligible Flags (4): Guard: 0/9 | Stable: 1/9 | Fast: 9/9 | HSDir: 0/9 | Running: 9/9 | V2Dir: 9/9 | Valid: 9/9 (need ≥5/9 for flag)
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Guard WFU Below 96.8% (DA) ≥98% (all authorities)
Time Known Meets 9.3 days (DA) ≥8 days (all authorities)
Bandwidth Meets (≥2 MB/s) 17.6 Mbit/s (R) ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s
Stable MTBF Below 9 days (DA) ≥26.6d - 45.4d (varies)
Uptime Below 1.0d (R) ≥19.1d - 19.7d (varies)
Fast Speed Meets (≥100 KB/s) 17.6 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
HSDir WFU Below 96.8% (DA) ≥98.0%
Time Known Below 9.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
ZoddyTor
Fingerprint
B6AB437081DEA0420A0A5BC8DAD7565DFFC00BBA
AROI (?)
none
Contact
[email protected]
IPv4 Exit Policy Summary 
reject: 
  1-65535
IPv6 Exit Policy Summary 
none
Exit Policy 
reject *:*
Effective Family Member: 1 
B6AB437081DEA0420A0A5BC8DAD7565DFFC00BBA
Alleged Family Members: 0 
none
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
17.56 Mbit/s | 17.56 Mbit/s| 32.77 Mbit/s| 32.77 Mbit/s  Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
0.00% | N/A | 0.00% | N/A
OR Address
151.67.0.29:9001
Exit Address
none
Dir Address
none
Country
Italy Italy
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS1267 | WIND TRE S.P.A. (BGP.tools)
Flags: 3
Fast Fast Running Running Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
94.9%/—/—/—
Uptime (1M/6M/1Y/5Y)
98.0%/0.0%/0.0%/0.0%
Uptime / Downtime
UP 23h 41m 1s ago
Seen (First | Last)
2w 17h 55m ago (2025-12-26 11:00:00) | 1h 55m ago (2026-01-10 03:00:00)
Last Restarted
23h 48m 32s ago (2026-01-09 05:06:28)
Last Changed Address or Port
2026-01-05 20: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
  • Consensus Weight (Dir. Auth.): Median: 14.4 Kbit/s | Min: 6240 bit/s | Max: 17.6 Kbit/s [Warning] High deviation
  • Identified Issues:
    • Guard: WFU below threshold: Weighted Fractional Uptime 96.8% 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 96.8% 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.) 14.4 Kbit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 96.8% ≥98% (all authorities) BELOW - cannot get Guard
Guard TK (Dir. Auth., tk) 9.3 days ≥8 days (all authorities) MEETS
Guard BW (Relay Reported) 17.6 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s MEETS - ≥2 MB/s guarantee
Stable Uptime (Relay Reported) 1.0d ≥19.1d - 19.7d (typical) BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf) 9 days ≥26.6d - 45.4d (typical)
[Stricter] moria1: ≥376.2d 		BELOW - 1/9
Fast Speed (Relay Reported) 17.6 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) 96.8% ≥98.0% (from all auths) BELOW - 0/9
HSDir TK (Dir. Auth., tk) 9.3 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.9d 		BELOW - 0/9

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 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, Running, Valid 17.6 Mbit/s | 816.0 Kbit/s 17.6 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 96.8% | 98% 9.3d | 8d 2.3d | 47.0d 1.0d | 19.7d 96.8% | 98.0% 9.3d | 1.0d 2026-01-09 23:07:32 13.6 Kbit/s
dannenberg (DE) Yes Yes N Yes Fast, Running, Valid 17.6 Mbit/s | 816.0 Kbit/s 17.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 96.1% | 98% 8.9d | 8d 1.8d | 35.7d 1.0d | 20.2d 96.1% | 98.0% 8.9d | 1.0d 2026-01-09 23:07:32 17.6 Kbit/s
dizum (NL) Yes Yes N Yes Fast, Running, Valid 17.6 Mbit/s | 816.0 Kbit/s 17.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 96.7% | 98% 8.8d | 8d 2.1d | 26.6d 1.0d | 20.4d 96.7% | 98.0% 8.8d | 1.0d 2026-01-09 23:07:32 17.6 Kbit/s
faravahar (US) Yes Yes N Yes Fast, Running, Valid 17.6 Mbit/s | 816.0 Kbit/s 17.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 96.7% | 98% 9.1d | 8d 2.4d | 41.9d 1.0d | 19.1d 96.7% | 98.0% 9.1d | 1.0d 2026-01-09 23:07:32 17.6 Kbit/s
gabelmoo (DE) Yes Yes Y Yes Fast, Running, Valid 17.6 Mbit/s | 816.0 Kbit/s 17.6 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 97.7% | 98% 10.2d | 8d 4.0d | 45.4d 1.0d | 19.6d 97.7% | 98.0% 10.2d | 1.0d 2026-01-09 23:07:32 7280 bit/s
longclaw (US) Yes Yes Y Yes Fast, Running, Valid 17.6 Mbit/s | 816.0 Kbit/s 17.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 97.6% | 98% 9.7d | 8d 3.5d | 48.7d 1.0d | 19.5d 97.6% | 98.0% 9.7d | 1.0d 2026-01-09 23:07:32 17.6 Kbit/s
maatuska (SE) Yes Yes Y Yes Fast, Running, Valid 17.6 Mbit/s | 816.0 Kbit/s 17.6 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 97.4% | 98% 9.8d | 8d 2.9d | 42.3d 1.0d | 19.4d 97.4% | 98.0% 9.8d | 1.0d 2026-01-09 23:07:32 6240 bit/s
moria1 (US) Yes Yes Y Yes Fast, Running, Stable, Valid 17.6 Mbit/s | 8.4 Mbit/s 17.6 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 96.9% | 98% 7.7d | 8d 13622.6d | 376.2d 1.0d | 20.4d 96.9% | 98.0% 7.7d | 9.9d 2026-01-09 23:07:32 14.4 Kbit/s
tor26 (AT) Yes Yes Y Yes Fast, Running, Valid 17.6 Mbit/s | 816.0 Kbit/s 17.6 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 97.4% | 98% 9.4d | 8d 3.1d | 51.8d 1.0d | 19.7d 97.4% | 98.0% 9.4d | 1.0d 2026-01-09 23:07:32 7600 bit/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.