View Relay "LillyCL"

Family: 20 relays | nashepro [at] proton [dot] me | AS7418 | Chile | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Fast, Running, V2Dir, Valid (4)
BW Verified
5/6 BW Auths Measured 6000 bit/s Median
Stability
Not Overloaded | UP 3h 30m 49s ago | UP 76% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
5mo 1w 4d ago
BW Weight
0.00% of Network | 8 Mbit/s Observed By Relay
Version
0.4.8.21 Recommended
Issues Detected:
  • Guard: bandwidth below threshold : Observed bandwidth 1.0 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 70.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: 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 70.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.

Connectivity and Location

Addresses
OR Address
186-104-124-58.fo.baf.movistar.cl
186.104.124.58:9008
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Chile Chile
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS7418
AS Name
Unknown

Flags and Eligibility

Current Flags (4): Fast, Running, V2Dir, 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 70.2% (DA) ≥98% (all authorities)
Time Known Meets 10.6 days (DA) ≥8 days (all authorities)
Bandwidth Below 8.2 Mbit/s (R) ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s
Stable MTBF Below 11 days (DA) ≥26.6d - 45.4d (varies)
Uptime Below 0.1d (R) ≥19.1d - 19.7d (varies)
Fast Speed Meets (≥100 KB/s) 8.2 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
HSDir WFU Below 70.2% (DA) ≥98.0%
Time Known Meets 10.6 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
LillyCL
Fingerprint
650EE30A57CB27F56EDCEA7ABCC6A245E20CE225
AROI (?)
none
Contact
nashepro [at] proton [dot] me
IPv4 Exit Policy Summary 
reject: 
  1-65535
IPv6 Exit Policy Summary 
none
Exit Policy 
reject *:*
Effective Family Members: 20 (View) 
1C124E048CFEE9A4B91153E6E01764B7DF4FE86F
24F10CBA8DFA4F9B108793A174650298424A76D3
48725E92F68200F93981B26E33204761B72EA267
4C89EFD87D91D7CD91004C34B50E1D06085A80F0
5DC73079EC1BB69B68AB98D271954DF547A5D303
5EC2728F09F82EB8E15B43AE462C4AB12D9AF933
650EE30A57CB27F56EDCEA7ABCC6A245E20CE225
65BC471566CBAEA416B4C0C4FCC57CD1BE45D1C6
6C3C6A4003D6D01A14F4E53E4D44B741BC06FB00
6EB89BEC0CF927F50AE76699F42A60BE6EFD0C77
7E1129961A0673C13868AB96B63FA9277B8F4625
87395D641F219455791C8DB0A43A7E90735D8AD3
936AAC50D69C9A3E3B37BA258156547F000C8D9D
A426F1A30B0843FBEE5596CA33032F64DD608AA8
A60163640A3C50D320915D3E62C3644D14639EC5
BD5478AF4FC21E27F0D7B2A302408CA778295F30
CB0445D2046289D166F70EC99EBA4B22162CD337
CD5E21D918B5E7BE18197E5566FACA8BC4D3C3E1
D70775A2BE422E0EBDBD49D75BE02C9D14B00CB3
EF4EE975512B4A59CD9B1BC8631A82A0D7C51897
Alleged Family Members: 0 
none
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
8.25 Mbit/s | 8.25 Mbit/s| 8.59 Gbit/s| 8.59 Gbit/s  Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
0.00% | N/A | 0.00% | N/A
OR Address
186-104-124-58.fo.baf.movistar.cl | 186.104.124.58:9008
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
Fast Fast Running Running V2Dir V2Dir Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
68.9%/85.0%/—/—
Uptime (1M/6M/1Y/5Y)
76.9%/91.9%/0.0%/0.0%
Uptime / Downtime
UP 3h 30m 49s ago
Seen (First | Last)
5mo 1w 4d ago (2025-08-02 01:00:00) | 1h 55m 2s ago (2026-01-10 03:00:00)
Last Restarted
3h 38m 22s ago (2026-01-10 01:16:40)
Last Changed Address or Port
2026-01-10 02: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: 6000 bit/s | Min: 664 bit/s | Max: 8.2 Kbit/s [Warning] High deviation
  • Identified Issues:
    • Guard: bandwidth below threshold: Observed bandwidth 1.0 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 70.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: 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 70.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.

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.) 6000 bit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 70.2% ≥98% (all authorities) BELOW - cannot get Guard
Guard TK (Dir. Auth., tk) 10.6 days ≥8 days (all authorities) MEETS
Guard BW (Relay Reported) 8.2 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s BELOW - need ≥2 MB/s
Stable Uptime (Relay Reported) 0.1d ≥19.1d - 19.7d (typical) BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf) 11 days ≥26.6d - 45.4d (typical)
[Stricter] moria1: ≥376.2d 		BELOW - 1/9
Fast Speed (Relay Reported) 8.2 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) 70.2% ≥98.0% (from all auths) BELOW - 0/9
HSDir TK (Dir. Auth., tk) 10.6 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, V2Dir, Valid 8.2 Mbit/s | 816.0 Kbit/s 8.2 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 70.2% | 98% 10.6d | 8d 0.2d | 47.0d 0.1d | 19.7d 70.2% | 98.0% 10.6d | 1.0d 2026-01-10 01:28:40 6000 bit/s
dannenberg (DE) Yes Yes N Yes Fast, Running, V2Dir, Valid 8.2 Mbit/s | 816.0 Kbit/s 8.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 72.1% | 98% 10.3d | 8d 0.2d | 35.7d 0.1d | 20.2d 72.1% | 98.0% 10.3d | 1.0d 2026-01-10 01:28:40 8.2 Kbit/s
dizum (NL) Yes Yes N Yes Fast, Running, V2Dir, Valid 8.2 Mbit/s | 816.0 Kbit/s 8.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 70.2% | 98% 10.6d | 8d 0.2d | 26.6d 0.1d | 20.4d 70.2% | 98.0% 10.6d | 1.0d 2026-01-10 01:28:40 8.2 Kbit/s
faravahar (US) Yes Yes N Yes Fast, Running, V2Dir, Valid 8.2 Mbit/s | 816.0 Kbit/s 8.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 69.7% | 98% 10.3d | 8d 0.2d | 41.9d 0.1d | 19.1d 69.7% | 98.0% 10.3d | 1.0d 2026-01-10 01:28:40 8.2 Kbit/s
gabelmoo (DE) Yes Yes Y Yes Fast, Running, V2Dir, Valid 8.2 Mbit/s | 816.0 Kbit/s 8.2 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 71.3% | 98% 10.6d | 8d 0.2d | 45.4d 0.1d | 19.6d 71.3% | 98.0% 10.6d | 1.0d 2026-01-10 01:28:40 2080 bit/s
longclaw (US) Yes Yes Y Yes Fast, Running, V2Dir, Valid 8.2 Mbit/s | 816.0 Kbit/s 8.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 70.5% | 98% 10.3d | 8d 0.2d | 48.7d 0.1d | 19.5d 70.5% | 98.0% 10.3d | 1.0d 2026-01-10 01:28:40 8.2 Kbit/s
maatuska (SE) Yes Yes Y Yes Running, V2Dir, Valid 8.2 Mbit/s | 816.0 Kbit/s 8.2 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 70.5% | 98% 10.6d | 8d 0.2d | 42.3d 0.1d | 19.4d 70.5% | 98.0% 10.6d | 1.0d 2026-01-10 01:28:40 664 bit/s
moria1 (US) Yes Yes Y Yes Stable, V2Dir, Valid 8.2 Mbit/s | 8.4 Mbit/s 8.2 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 1.9% | 98% 8.9d | 8d 20441.2d | 376.2d 0.1d | 20.4d 1.9% | 98.0% 8.9d | 9.9d 2026-01-10 01:28:40 2960 bit/s
tor26 (AT) Yes Yes Y Yes Fast, Running, V2Dir, Valid 8.2 Mbit/s | 816.0 Kbit/s 8.2 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 70.0% | 98% 10.3d | 8d 0.2d | 51.8d 0.1d | 19.7d 70.0% | 98.0% 10.3d | 1.0d 2026-01-10 01:28:40 1360 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.