View Relay "TV5035"

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

Consensus
Not In Consensus (4/8 Directory Auths, need 5)
DNS Health
DNS Lookup Failed (via exitdnshealth.1aeo.com)
BW Verified
1/5 BW Auths Measured 3192 bit/s Median
Stability
Not Overloaded | DOWN 10h 45m 49s ago
Reachability
IPv4: 4/9 (Directory Auths)
BW Weight
0.00% of Network | 3 Mbit/s Observed By Relay
Version
0.4.8.22 Recommended
Issues Detected:
  • Not in consensus : Only 4/8 authorities voted for this relay (need 5)
    Suggestion: Verify your relay is reachable from multiple geographic locations. Check firewall rules allow incoming connections on your ORPort from all directory authority IP addresses.
  • IPv4 reachability issues : Only 4/9 authorities can reach this relay
    Suggestion: Authorities that cannot reach you: bastet, gabelmoo, longclaw, maatuska, moria1. Check: 1) Firewall allows incoming TCP on ORPort, 2) No ISP-level blocking, 3) Tor is running and listening. Use 'nc -zv your-ip your-orport' from external hosts to test.
  • 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.4 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 64.0% 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.8 days is below 8 days requirement (5.2 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 64.0% 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/5 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.

Addresses
OR Address
201-188-1-166.fo.baf.movistar.cl
201.188.1.166:9001
Reachability (Directory Authorities)
IPv4
4/9
Location
Country
Chile Chile
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS7418
AS Name
Unknown
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 4 operators)

Current Flags (4): Running, Valid, V2Dir, Exit
Eligible Flags (0): Running: 4/8 | Valid: 4/8 | V2Dir: 4/8 | Fast: 3/8 | Stable: 0/8 | HSDir: 0/8 | Guard: 0/8 | Exit: 4/8
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Below (4/8 DA) 4/8 authorities reached relay ≥5/8 DA ORPort reachable
IPv6 Reachability Below (0/4 DA) 0/4 tested authorities reached relay ≥3/4 tested (majority) (≥3/4 DA)
Valid Descriptor Partial (4/8 DA) 4/8 authorities assigned Valid Not blacklisted + valid descriptor (≥5/8 DA)
V2Dir DirPort Available Meets (4/8 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/8 DA)
Fast Speed Meets (8/8 DA) 3.2 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 (0/8 DA) Median: 1.0d (0/8 DA above threshold)
Min/Max: 0.6d / 1.0d (4/8 DA, Voting / Total Eligible)
≥32.5d - 59.0d (varies) (≥5/8 DA)
[Stricter] moria1: ≥317.9d
Uptime Below (0/8 DA) 0.8d (R) ≥7.0d - 7.2d (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 (0/8 DA) 0/8 DA assigned Stable ≥32.5d - 59.0d (varies) (≥5/8 DA)
[Stricter] moria1: ≥317.9d
Prereq: V2Dir Below (4/8 DA) 4/8 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/8 DA)
WFU Below (0/8 DA) Median: 64.1% (0/8 DA above threshold)
Min/Max: 63.2% / 64.5% (4/8 DA, Voting / Total Eligible)
≥98.0% (≥5/8 DA)
Time Known Below (4/8 DA) Median: 2.8d (0/8 DA above threshold)
Min/Max: 2.7d / 2.8d (4/8 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/8 DA)
[Stricter] moria1: ≥9.9d
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 (0/8 DA) 0/8 DA assigned Stable ≥32.5d - 59.0d (varies) (≥5/8 DA)
[Stricter] moria1: ≥317.9d
Prereq: V2Dir Below (4/8 DA) 4/8 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/8 DA)
WFU Below (0/8 DA) Median: 64.1% (0/8 DA above threshold)
Min/Max: 63.2% / 64.5% (4/8 DA, Voting / Total Eligible)
≥98% (≥5/8 DA)
Time Known Below (0/8 DA) (need 5.2 more days) Median: 2.8d (0/8 DA above threshold)
Min/Max: 2.7d / 2.8d (4/8 DA, Voting / Total Eligible)
≥8 days (≥5/8 DA)
Bandwidth Below (0/8 DA) 3.2 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-304.0 Mbit/s (≥5/8 DA)
Exit Exit Policy Below (4/8 DA) No exit policy (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-14 22:45:08).

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

Source: CollecTor — fetched 2026-04-14 22:45:08

Measured By
1/5 Bandwidth Authorities
Not measured by: gabelmoo, longclaw, maatuska, moria1
Median Measurement
3192.0 bit/s
Min / Max
16 bit/s / 3192 bit/s
Deviation
3176 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (1th pctl) | Guard: N/A | Middle: N/A | Exit: N/A

Uptime Metrics
Current Status
DOWN 10h 45m 49s 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
3d 2h 45m ago (2026-04-11 21:00:00)
Last Seen
10h 45m 49s ago (2026-04-14 13:00:00)
Last Restarted
19h 2m 47s ago (2026-04-14 04:43:02)
Last Changed Address
2026-04-11 21:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator Identity

Source: AROI Validation API — 2026-04-14 15: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
0EF81964E7A24D2FF53AA8DA8F2D950BA0901ABE (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Platform
Linux — Tor 0.4.8.22 on Linux
Version
0.4.8.22Recommended
Version Status
Recommended

DNS Health
Status
DNS Lookup Failed (failed last 1 scan)
Error
DNS Error: SOCKS 4 - Domain not found (NXDOMAIN)
Query Domain
64d9316667264353bb9896f50c3a5635.0ef81964.tor.exit.validator.1aeo.com
DNS Result
No Response (expected 64.65.4.1)
Cross-Validation
0/4 instances succeeded
First Hop
hellomyduckWinter (CH) 8DBA9ADCA5B3A3AB6D2B4F88AC2F96614D33DAB3
Exit Address Used
201.188.1.166
Per-Instance Results
Cross Validation Attempt 1: DNS Fail, 15.6s (cv1_w1)
Cross Validation Attempt 2: DNS Fail, 14.1s (cv2_w1)
Cross Validation Attempt 3: DNS Fail, 25.9s (cv3_w1)
Cross Validation Attempt 4: DNS Fail, 17.8s (cv4_w1)
Tested: 2026-04-14 07:06:12 UTC
IPv4 Exit Policy Summary
None
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 201.188.1.166:*
accept *:*

Last fetch was at Tue, 14 Apr 2026 23:45:47 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-04-14 22:45:08).

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 Yes N Yes Valid, V2Dir, Fast, Exit 3.2 Mbit/s | 816.0 Kbit/s 3.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 64.0% | 98% 2.8d | 8d 1.0d | 32.5d 0.8d | 7.1d 64.0% | 98.0% 2.8d | 1.0d 2026-04-14 20:15:23 3192 bit/s
dizum (NL) Yes Yes Yes N Yes Valid, V2Dir, Fast, Exit 3.2 Mbit/s | 816.0 Kbit/s 3.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 64.5% | 98% 2.8d | 8d 1.0d | 42.0d 0.8d | 7.0d 64.5% | 98.0% 2.8d | 1.0d 2026-04-14 20:15:23 3192 bit/s
faravahar (US) Yes Yes Yes N Yes Valid, V2Dir, Fast, Exit 3.2 Mbit/s | 816.0 Kbit/s 3.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 64.2% | 98% 2.7d | 8d 1.0d | 59.3d 0.8d | 7.2d 64.2% | 98.0% 2.7d | 1.0d 2026-04-14 20:15:23 3192 bit/s
gabelmoo (DE) No Y No
longclaw (US) No Y No
maatuska (SE) No Y No
moria1 (US) No Y No
tor26 (AT) Yes Yes Yes Y Yes Valid, V2Dir, Exit 3.2 Mbit/s | 816.0 Kbit/s 3.2 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 63.2% | 98% 2.7d | 8d 0.6d | 58.8d 0.8d | 7.3d 63.2% | 98.0% 2.7d | 1.0d 2026-04-14 20:15:23 16 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.