View Relay "TV7893"

Fingerprint: 0F5EA7F1944A8B87B72B500DFAB731D6DA942480 | Family: 1 relay | printerexpert@mail2tor.com | AS22927 | Argentina | Linux

Health Status

Consensus
In Consensus (6/7 Directory Auths)
Flags
Running, Valid, V2Dir, Exit (4)
DNS Health
DNS Lookup Failed (via exitdnshealth.1aeo.com)
BW Verified
1/6 BW Auths Measured 15 Kbit/s Median
Stability
Not Overloaded | UP 4h 26m 26s ago
Reachability
IPv4: 6/7 (Directory Auths)
First Seen
2d 2h 45m ago
BW Weight
0.00% of Network | 15 Mbit/s Observed By Relay
Version
0.4.8.22 Not 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 15 Mbit/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 36.2% 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 2.0 days is below 8 days requirement (6.0 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 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: WFU below threshold : WFU 36.2% 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.
  • Low bandwidth authority measurements : Only 1/6 bandwidth authorities measured this relay. Minimum 3 measurements needed for accurate consensus weight.
    Suggestion: Low measurement count can indicate connectivity issues. Check: 1) Relay is reachable from multiple geographic locations, 2) ORPort accepts connections from bandwidth scanners, 3) RelayBandwidthRate in torrc matches actual capacity. New relays may take 1-2 days to be measured by all authorities.
  • Tor version not recommended : Running Tor version 0.4.8.22 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.
Notes:
  • Partial IPv4 reachability: 6/7 authorities can reach this relay

Connectivity and Location

Addresses
OR Address
190.49.7.95:9001
Reachability (Directory Authorities)
IPv4
6/7
Location
Country
Argentina Argentina
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS22927
AS Name
Unknown
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 2 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Exit
Eligible Flags (4): Running: 6/7 | Valid: 6/7 | V2Dir: 6/7 | Fast: 3/7 | Stable: 0/7 | HSDir: 0/7 | Guard: 0/7 | Exit: 6/7
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (6/7 DA) 6/7 authorities reached relay ≥4/7 DA ORPort reachable
IPv6 Reachability Below (0/1 DA) 0/1 tested authorities reached relay ≥1/1 tested (majority) (≥1/1 DA)
Valid Descriptor Meets (6/7 DA) 6/7 authorities assigned Valid Not blacklisted + valid descriptor (≥4/7 DA)
V2Dir DirPort Available Meets (6/7 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥4/7 DA)
Fast Speed Meets (7/7 DA) 15.4 Mbit/s (R) ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (0/7 DA) Median: 0.2d (0/7 DA above threshold)
Min/Max: 0.2d / 0.3d (6/7 DA, Voting / Total Eligible)		 ≥9.5d - 20.1d (varies) (≥4/7 DA)
[Stricter] moria1: ≥7732.8d
Uptime Below (0/7 DA) 0.2d (R) ≥3.8d - 3.9d (varies) (≥4/7 DA)
HSDir Prereq: Fast Below (3/7 DA) 3/7 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (0/7 DA) 0/7 DA assigned Stable ≥9.5d - 20.1d (varies) (≥4/7 DA)
[Stricter] moria1: ≥7732.8d
Prereq: V2Dir Meets (6/7 DA) 6/7 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥4/7 DA)
WFU Below (0/7 DA) Median: 35.2% (0/7 DA above threshold)
Min/Max: 32.1% / 37.2% (6/7 DA, Voting / Total Eligible)		 ≥98.0% (≥4/7 DA)
Time Known Meets (6/7 DA) Median: 2.0d (0/7 DA above threshold)
Min/Max: 1.9d / 2.0d (6/7 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥4/7 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Below (3/7 DA) 3/7 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (0/7 DA) 0/7 DA assigned Stable ≥9.5d - 20.1d (varies) (≥4/7 DA)
[Stricter] moria1: ≥7732.8d
Prereq: V2Dir Meets (6/7 DA) 6/7 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥4/7 DA)
WFU Below (0/7 DA) Median: 35.2% (0/7 DA above threshold)
Min/Max: 32.1% / 37.2% (6/7 DA, Voting / Total Eligible)		 ≥98% (≥4/7 DA)
Time Known Below (0/7 DA) (need 6.0 more days) Median: 2.0d (0/7 DA above threshold)
Min/Max: 1.9d / 2.0d (6/7 DA, Voting / Total Eligible)		 ≥8 days (≥4/7 DA)
Bandwidth Below (0/7 DA) 15.4 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-288.0 Mbit/s (≥4/7 DA)
Exit Exit Policy Meets (6/7 DA) Port 80: Yes | Port 443: Yes (R) Allows ≥1 /8 on ports 80 AND 443 (≥4/7 DA)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-07-14 02:45:10).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
15.40 Mbit/s
Advertised Bandwidth
15.40 Mbit/s
Rate Limit
100.00 Mbit/s
Burst Limit
100.00 Mbit/s
Total Data
4.2 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-07-14 02:45:10

Measured By
1/6 Bandwidth Authorities
Not measured by: bastet, dannenberg, faravahar, moria1, tor26
Median Measurement
15.4 Kbit/s
Min / Max
3040 bit/s / 15.4 Kbit/s
Deviation
12.4 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (2th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0000% (1th pctl)

Uptime and Stability

Uptime Metrics
Current Status
UP 4h 26m 26s 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
2d 2h 45m ago (2026-07-12 00:00:00)
Last Seen
1h 45m 57s ago (2026-07-14 01:00:00)
Last Restarted
4h 26m 26s ago (2026-07-13 22:19:31)
Last Changed Address
2026-07-13 01:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-07-13 19:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
printerexpert@mail2tor.com
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
0F5EA7F1944A8B87B72B500DFAB731D6DA942480 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

Platform
Linux — Tor 0.4.8.22 on Linux
Version
0.4.8.22 — Not Recommended
Version Status
Obsolete — Update urgently. See torproject.org/download

Exit Health & Policy

DNS Health
Status
DNS Lookup Failed (failed last 1 scan)
Error
DNS Error: SOCKS 4 - Domain not found (NXDOMAIN)
Query Domain
8db15be0cce34c11ac73f58203dd1838.0f5ea7f1.tor.exit.validator.1aeo.com
DNS Result
No Response (expected 64.65.4.1)
Cross-Validation
0/4 instances succeeded
First Hop
UFOAlien1 (EE) F02F6A561E845B591D1539AED0ED63A3EEFB2BC2
Exit Address Used
190.49.7.95
Per-Instance Results
Cross Validation Attempt 1: DNS Fail, 14.1s (cv1_w1)
Cross Validation Attempt 2: DNS Fail, 17.6s (cv2_w1)
Cross Validation Attempt 3: DNS Fail, 23.4s (cv3_w1)
Cross Validation Attempt 4: DNS Fail, 18.8s (cv4_w1)
Tested: 2026-07-13 19:06:21 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 
  1-65535
IPv6 Exit Policy Summary
None
Full Exit Policy
reject 0.0.0.0/8:*
reject 169.254.0.0/16:*
reject 127.0.0.0/8:*
reject 192.168.0.0/16:*
reject 10.0.0.0/8:*
reject 172.16.0.0/12:*
reject 190.49.7.95:*
accept *:*

Last fetch was at Tue, 14 Jul 2026 02:45:56 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-07-14 02:45:10).

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 Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 15.4 Mbit/s | 816.0 Kbit/s 15.4 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 36.2% | 98% 2.0d | 8d 0.3d | 29.6d 0.2d | 4.2d 36.2% | 98.0% 2.0d | 1.0d 2026-07-13 22:20:34 15.4 Kbit/s
dannenberg (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 15.4 Mbit/s | 816.0 Kbit/s 15.4 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 37.2% | 98% 1.9d | 8d 0.3d | 9.5d 0.2d | 3.9d 37.2% | 98.0% 1.9d | 1.0d 2026-07-13 22:20:34 15.4 Kbit/s
dizum (NL) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Exit 15.4 Mbit/s | 816.0 Kbit/s 15.4 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 34.8% | 98% 1.9d | 8d 0.2d | 18.6d 0.2d | 3.9d 34.8% | 98.0% 1.9d | 1.0d 2026-07-13 22:20:34 15.4 Kbit/s
faravahar (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 15.4 Mbit/s | 816.0 Kbit/s 15.4 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 32.1% | 98% 2.0d | 8d 0.2d | 16.3d 0.2d | 3.9d 32.1% | 98.0% 2.0d | 1.0d 2026-07-13 22:20:34 15.4 Kbit/s
maatuska (SE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 15.4 Mbit/s | 816.0 Kbit/s 15.4 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 34.7% | 98% 1.9d | 8d 0.2d | 20.1d 0.2d | 3.9d 34.7% | 98.0% 1.9d | 1.0d 2026-07-13 22:20:34 3040 bit/s
moria1 (US) No — — — Y No — — — — — — — — — — —
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 15.4 Mbit/s | 816.0 Kbit/s 15.4 Mbit/s | 264.0 Mbit/s OR 16.0 Mbit/s 35.5% | 98% 2.0d | 8d 0.2d | 30.3d 0.2d | 3.8d 35.5% | 98.0% 2.0d | 1.0d 2026-07-13 22:20:34 15.4 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.