View Relay "TV6705"

Family: 1 relay | printerexpert@mail2tor.com | AS7418 | Chile | Linux

Health Status

Consensus
In Consensus (8/9 Directory Auths)
Flags
Exit, Running, V2Dir, Valid (4)
BW Verified
3/6 BW Auths Measured 640 bit/s Median
Stability
Not Overloaded | DOWN 19h 15m 43s ago | UP 19% (1M)
Reachability
IPv4: 8/9 (Directory Auths)
First Seen
1w 8h 17m ago
BW Weight
0.00% of Network | 647 Kbit/s Observed By Relay
Version
0.4.8.22 Recommended
Issues Detected:
  • Guard: bandwidth below threshold : Observed bandwidth 0.1 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 13.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 5.3 days is below 8 days requirement (2.7 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).
  • 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.
  • 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 13.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.
  • StaleDesc flag assigned : Relay descriptor is older than 18 hours
    Suggestion: Your relay is not publishing fresh descriptors. Check: 1) Tor process is running, 2) Network connectivity, 3) Clock is synchronized (NTP). Restart Tor if needed.
Notes:
  • Partial IPv4 reachability: 8/9 authorities can reach this relay
  • Bandwidth authority measurements below majority: 3/6 bandwidth authorities measured this relay (majority is 4).

Connectivity and Location

Addresses
OR Address
152.173.203.197:9001
Reachability (Directory Authorities)
IPv4
8/9
Location
Country
Chile Chile
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS7418
AS Name
Unknown
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 5 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Exit
Eligible Flags (3): Running: 8/9 | Valid: 8/9 | V2Dir: 8/9 | Fast: 0/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9 (need ≥5/9 for flag)
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Fast Speed Below 647.2 Kbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below Median: 0.1d (0/9 DA above threshold)
Min/Max: 0.1d / 0.1d (8/9 DA, Voting / Total Eligible)		 ≥22.1d - 51.9d (varies)
[Stricter] moria1: ≥451.9d
Uptime Below 0.9d (R) ≥6.4d - 7.5d (varies)
HSDir Prereq: Stable Below 0/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: Fast Below 0/9 authorities assigned Fast flag ≥5/9 authorities
WFU Below Median: 13.2% (0/9 DA above threshold)
Min/Max: 12.2% / 14.2% (8/9 DA, Voting / Total Eligible)		 ≥98.0%
Time Known Below Median: 5.2d (0/9 DA above threshold)
Min/Max: 5.1d / 5.4d (8/9 DA, Voting / Total Eligible)		 ≥1.0d (most)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Below 0/9 authorities assigned Fast flag ≥5/9 authorities
Prereq: Stable Below 0/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: V2Dir Meets 8/9 authorities assigned V2Dir flag ≥5/9 authorities
WFU Below Median: 13.2% (0/9 DA above threshold)
Min/Max: 12.2% / 14.2% (8/9 DA, Voting / Total Eligible)		 ≥98% (all authorities)
Time Known Below (need 2.8 more days) Median: 5.2d (0/9 DA above threshold)
Min/Max: 5.1d / 5.4d (8/9 DA, Voting / Total Eligible)		 ≥8 days (all authorities)
Bandwidth Below 647.2 Kbit/s (R) ≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-02-11 21:15:08).

Last fetch was at Wed, 11 Feb 2026 22:15:42 GMT.

Nickname
TV6705
Fingerprint
8544F9F4A24114D30CE6671F3400BC3DA8628A69
AROI (?)
none
Contact
printerexpert@mail2tor.com
IPv4 Exit Policy Summary 
accept: 
  1-65535
IPv6 Exit Policy Summary 
none
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 152.173.203.197:*
accept *:*
Effective Family Member: 1 
8544F9F4A24114D30CE6671F3400BC3DA8628A69
Alleged Family Members: 0 
none
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
647.17 Kbit/s | 647.17 Kbit/s| 100.00 Mbit/s| 100.00 Mbit/s  Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
0.00% | N/A | N/A | N/A
OR Address
152.173.203.197:9001
Exit Address
none
Dir Address
none
Country
Chile Chile
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS7418 | unknown
Flags: 4
Exit Exit Running Running V2Dir V2Dir Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
Match Overall Uptime (19.4%/0.0%/0.0%/0.0%)
Uptime (1M/6M/1Y/5Y)
19.4%/0.0%/0.0%/0.0%
Uptime / Downtime
DOWN 19h 15m 43s ago
Seen (First | Last)
1w 8h 17m ago (2026-02-04 14:00:00) | 19h 17m 29s ago (2026-02-11 03:00:00)
Last Restarted
21h 53m 2s ago (2026-02-11 00:24:27)
Last Changed Address or Port
2026-02-10 11:00:00
Hibernating
No
Platform (Short | Long)
Linux | Tor 0.4.8.22 on Linux
Version (Running | Recommended | Status)
0.4.8.22 | Yes | recommended

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-02-11 21:15:08).

  • Consensus Status (need ≥5/9): In Consensus — 8/9 authorities voted.
  • Flag Eligibility (need ≥5/9 for flag): Running: 8/9 | Valid: 8/9 | V2Dir: 8/9 | Fast: 0/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9
  • Reachability: IPv4: 8/9
  • Consensus Weight (Dir. Auth.): Median: 640.0 bit/s | Min: 8 bit/s | Max: 640 bit/s [Warning] High deviation
  • Identified Issues:
    • Guard: bandwidth below threshold: Observed bandwidth 0.1 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 13.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 5.3 days is below 8 days requirement (2.7 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).
    • 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.
    • 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 13.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.
    • StaleDesc flag assigned: Relay descriptor is older than 18 hours
      • Suggestion: Your relay is not publishing fresh descriptors. Check: 1) Tor process is running, 2) Network connectivity, 3) Clock is synchronized (NTP). Restart Tor if needed.
  • Notes:
    • Partial IPv4 reachability: 8/9 authorities can reach this relay
    • Bandwidth authority measurements below majority: 3/6 bandwidth authorities measured this relay (majority is 4).

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.) 8/9 authorities ≥5/9 (majority) IN CONSENSUS
Running (IPv4 Reachable) 8/9 authorities reached this relay ≥5/9 (majority) RUNNING
Valid 8/9 (Running + Valid Descriptor) ≥5/9 (majority) VALID
Consensus Weight (Dir. Auth.) 640.0 bit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 13.2% ≥98% (all authorities) BELOW - cannot get Guard
Guard TK (Dir. Auth., tk) 5.2 days ≥8 days (all authorities) BELOW - need 2.8 more days
Guard BW (Relay Reported) 647.2 Kbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s BELOW - need ≥2 MB/s
Stable Uptime (Relay Reported) 0.9d ≥6.4d - 7.5d (typical) BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf) 0 days ≥22.1d - 51.9d (typical)
[Stricter] moria1: ≥451.9d 		BELOW - 0/9
Fast Speed (Relay Reported) 647.2 Kbit/s ≥800.0 Kbit/s (guarantee) OR ≥816.0 Kbit/s (typical)
[Stricter] moria1: ≥8.4 Mbit/s 		BELOW - need ≥100 KB/s
HSDir WFU (Dir. Auth., wfu) 13.2% ≥98.0% (from all auths) BELOW - 0/9
HSDir TK (Dir. Auth., tk) 5.2 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 Valid, V2Dir, Exit, StaleDesc 647.2 Kbit/s | 816.0 Kbit/s 647.2 Kbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 13.2% | 98% 5.3d | 8d 0.1d | 51.9d 0.9d | 7.5d 13.2% | 98.0% 5.3d | 1.0d 2026-02-11 00:25:36 [Stale] 120 bit/s
dannenberg (DE) Yes Yes N Yes Valid, V2Dir, Exit, StaleDesc 647.2 Kbit/s | 712.0 Kbit/s 647.2 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 13.2% | 98% 5.2d | 6d 0.1d | 22.1d 0.9d | 6.5d 13.2% | 98.0% 5.2d | 1.0d 2026-02-11 00:25:36 [Stale] 640 bit/s
dizum (NL) Yes Yes N Yes Valid, V2Dir, Exit, StaleDesc 647.2 Kbit/s | 704.0 Kbit/s 647.2 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 12.4% | 98% 5.4d | 6d 0.1d | 27.7d 0.9d | 6.4d 12.4% | 98.0% 5.4d | 1.0d 2026-02-11 00:25:36 [Stale] 640 bit/s
faravahar (US) Yes Yes N Yes Valid, V2Dir, Exit, StaleDesc 647.2 Kbit/s | 816.0 Kbit/s 647.2 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 13.6% | 98% 5.2d | 8d 0.1d | 47.9d 0.9d | 7.5d 13.6% | 98.0% 5.2d | 1.0d 2026-02-11 00:25:36 [Stale] 640 bit/s
gabelmoo (DE) Yes Yes Y Yes Valid, V2Dir, Exit, StaleDesc 647.2 Kbit/s | 816.0 Kbit/s 647.2 Kbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 13.4% | 98% 5.4d | 8d 0.1d | 60.4d 0.9d | 7.5d 13.4% | 98.0% 5.4d | 1.0d 2026-02-11 00:25:36 [Stale] 8 bit/s
longclaw (US) Yes Yes Y Yes Valid, V2Dir, Exit 647.2 Kbit/s | 816.0 Kbit/s 647.2 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 14.2% | 98% 5.2d | 8d 0.1d | 61.0d 0.9d | 7.3d 14.2% | 98.0% 5.2d | 1.0d 2026-02-11 00:25:36 640 bit/s
maatuska (SE) Yes Yes Y Yes Valid, V2Dir, Exit, StaleDesc 647.2 Kbit/s | 816.0 Kbit/s 647.2 Kbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 12.2% | 98% 5.1d | 8d 0.1d | 41.8d 0.9d | 7.5d 12.2% | 98.0% 5.1d | 1.0d 2026-02-11 00:25:36 [Stale] 64 bit/s
moria1 (US) No — Y No — — — — — — — — — — —
tor26 (AT) Yes Yes Y Yes Valid, V2Dir, Exit, StaleDesc 647.2 Kbit/s | 816.0 Kbit/s 647.2 Kbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 13.0% | 98% 5.2d | 8d 0.1d | 57.3d 0.9d | 7.5d 13.0% | 98.0% 5.2d | 1.0d 2026-02-11 00:25:36 [Stale] 640 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.