View Relay "benzomniac"

Fingerprint: F5018AF4477EFC921E63DF0CF0840CC13CBAF553 | Family: 1 relay | 0x98198E95 Benzomaniac benzomaniac@proton.me | AS27823 | Argentina | Linux

Health Status

Consensus
In Consensus (8/8 Directory Auths)
Flags
Running, Valid (2)
BW Verified
5/5 BW Auths Measured 220 bit/s Median
Stability
Not Overloaded | UP 1d 18h 14m ago | UP 79% (1M)
Reachability
IPv4: 8/9 (Directory Auths)
First Seen
3w 1d 14h ago
BW Weight
0.00% of Network | 1 Mbit/s Observed By Relay
Version
0.4.9.6 Recommended
Issues Detected:
  • Guard: requires Fast flag : Guard flag requires having the Fast flag first
    Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
  • 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: bandwidth below threshold : Observed bandwidth 0.2 MB/s is below 2 MB/s minimum (AuthDirGuardBWGuarantee)
    Suggestion: Guard requires ≥2 MB/s bandwidth OR being in top 25% of network. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx or ARM.
  • Guard: WFU below threshold : Weighted Fractional Uptime 58.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.
  • 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 Fast flag : HSDir flag requires having the Fast flag first
    Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
  • 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 58.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.
Notes:
  • Partial IPv4 reachability: 8/9 authorities can reach this relay

Connectivity and Location

Addresses
OR Address
vps-2925746-x.dattaweb.com
168.181.185.147:443
Reachability (Directory Authorities)
IPv4
8/9
Location
Country
Argentina Argentina
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS27823
AS Name
Unknown
AS Rarity
Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

Flags and Eligibility

Current Flags (2): Running, Valid
Eligible Flags (3): Running: 8/8 | Valid: 8/8 | V2Dir: 8/8 | Fast: 3/8 | Stable: 1/8 | HSDir: 0/8 | Guard: 0/8 | Exit: 0/8
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (8/8 DA) 8/8 authorities reached relay ≥5/8 DA ORPort reachable
Valid Descriptor Meets (8/8 DA) 8/8 authorities assigned Valid Not blacklisted + valid descriptor (≥5/8 DA)
V2Dir DirPort Available Below (0/8 DA) No DirPort, no tunnelled-dir-server (R) Tunnelled directory via ORPort or DirPort (≥5/8 DA)
Fast Speed Meets (8/8 DA) 1.8 Mbit/s (R) ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (1/8 DA) Median: 1.3d (1/8 DA above threshold)
Min/Max: 1.1d / 16292.6d (8/8 DA, Voting / Total Eligible)		 ≥16.5d - 58.9d (varies) (≥5/8 DA)
Uptime Below (0/8 DA) 1.8d (R) ≥10.4d - 10.9d (varies) (≥5/8 DA)
HSDir Prereq: Fast Below (3/8 DA) 3/8 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (1/8 DA) 1/8 DA assigned Stable ≥16.5d - 58.9d (varies) (≥5/8 DA)
Prereq: V2Dir Below (0/8 DA) 0/8 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/8 DA)
WFU Below (0/8 DA) Median: 58.6% (0/8 DA above threshold)
Min/Max: 53.7% / 62.8% (8/8 DA, Voting / Total Eligible)		 ≥98.0% (≥5/8 DA)
Time Known Meets (7/8 DA) Median: 11.2d (8/8 DA above threshold)
Min/Max: 9.5d / 11.4d (8/8 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/8 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Below (3/8 DA) 3/8 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (1/8 DA) 1/8 DA assigned Stable ≥16.5d - 58.9d (varies) (≥5/8 DA)
Prereq: V2Dir Below (0/8 DA) 0/8 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/8 DA)
WFU Below (0/8 DA) Median: 58.6% (0/8 DA above threshold)
Min/Max: 53.7% / 62.8% (8/8 DA, Voting / Total Eligible)		 ≥98% (≥5/8 DA)
Time Known Meets (8/8 DA) Median: 11.2d (8/8 DA above threshold)
Min/Max: 9.5d / 11.4d (8/8 DA, Voting / Total Eligible)		 ≥8 days (≥5/8 DA)
Bandwidth Below (0/8 DA) 1.8 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-328.0 Mbit/s (≥5/8 DA)
Exit Exit Policy Below (0/8 DA) Port 80: No | Port 443: No (R) Allows ≥1 /8 on ports 80 AND 443 (≥5/8 DA)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-04-29 12:45:03).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
1.81 Mbit/s
Advertised Bandwidth
1.64 Mbit/s
Rate Limit
1.64 Mbit/s
Burst Limit
3.28 Mbit/s
Total Data
1.5 TB (5 years)
1mo: 2.2 GB | 6mo: 146 GB | 1y: 167 GB | 5y: 1.5 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-04-29 12:45:03

Measured By
5/5 Bandwidth Authorities
Median Measurement
220.0 bit/s
Min / Max
96 bit/s / 1632 bit/s
Deviation
1536 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (2th pctl) | Guard: N/A | Middle: 0.0000% (2th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 1d 18h 14m ago
Overall Uptime (1M/6M/1Y/5Y)
79.1%/93.8%/83.0%/86.5%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (79.1%/93.8%/83.0%/86.5%)
Hibernating
No
Timestamps
First Seen
3w 1d 14h ago (2026-04-06 23:00:00)
Last Seen
5h 46m 39s ago (2026-04-29 08:00:00)
Last Restarted
1d 18h 14m ago (2026-04-27 19:32:33)
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-04-29 05:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
0x98198E95 Benzomaniac benzomaniac@proton.me
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
F5018AF4477EFC921E63DF0CF0840CC13CBAF553 (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
IPv6 Exit Policy Summary
None
Full Exit Policy
reject *:*

Last fetch was at Wed, 29 Apr 2026 13:46:37 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-04-29 12:45:03).

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) No — — — N No — — — — — — — — — — —
dannenberg (DE) Yes Yes No — N Yes Running, Valid, Fast 1.8 Mbit/s | 816.0 Kbit/s 1.8 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 58.8% | 98% 11.4d | 8d 1.3d | 46.4d 1.8d | 10.9d 58.8% | 98.0% 11.4d | 1.0d 2026-04-29 08:13:26 1632 bit/s
dizum (NL) Yes Yes No — N Yes Running, Valid, Fast 1.8 Mbit/s | 816.0 Kbit/s 1.8 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 53.7% | 98% 10.5d | 8d 1.1d | 42.5d 1.8d | 10.4d 53.7% | 98.0% 10.5d | 1.0d 2026-04-28 14:13:25 1632 bit/s
faravahar (US) Yes Yes No — N Yes Running, Valid, Fast 1.8 Mbit/s | 816.0 Kbit/s 1.8 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 58.7% | 98% 11.4d | 8d 1.3d | 58.9d 1.8d | 10.9d 58.7% | 98.0% 11.4d | 1.0d 2026-04-29 08:13:26 1632 bit/s
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid 1.8 Mbit/s | 816.0 Kbit/s 1.8 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 58.8% | 98% 10.9d | 8d 1.3d | 57.3d 1.8d | 10.9d 58.8% | 98.0% 10.9d | 1.0d 2026-04-29 08:13:26 96 bit/s
longclaw (US) Yes Yes No — Y Yes Running, Valid 1.8 Mbit/s | 816.0 Kbit/s 1.8 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 58.6% | 98% 11.3d | 8d 1.3d | 63.3d 1.8d | 10.9d 58.6% | 98.0% 11.3d | 1.0d 2026-04-29 08:13:26 184 bit/s
maatuska (SE) Yes Yes No — Y Yes Running, Valid 1.8 Mbit/s | 816.0 Kbit/s 1.8 Mbit/s | 328.0 Mbit/s OR 16.0 Mbit/s 56.4% | 98% 11.1d | 8d 1.3d | 16.5d 1.8d | 10.7d 56.4% | 98.0% 11.1d | 1.0d 2026-04-29 08:13:26 104 bit/s
moria1 (US) Yes Yes No — Y Yes Running, Valid, Stable 1.8 Mbit/s | 8.4 Mbit/s 1.8 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 62.8% | 98% 9.5d | 8d 16292.6d | 280.2d 1.8d | 12.2d 62.8% | 98.0% 9.5d | 9.8d 2026-04-29 08:13:26 256 bit/s
tor26 (AT) Yes Yes No — Y Yes Running, Valid 1.8 Mbit/s | 816.0 Kbit/s 1.8 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 58.5% | 98% 11.4d | 8d 1.3d | 59.0d 1.8d | 11.1d 58.5% | 98.0% 11.4d | 1.0d 2026-04-29 08:13:26 112 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). 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.