View Relay "TV8115"

Family: 1 relay | printerexpert@mail2tor.com | AS36884 | Morocco | Linux

Consensus
In Consensus (7/9 Directory Auths)
Flags
Running, V2Dir, Valid (3)
BW Verified
3/6 BW Auths Measured 312 bit/s Median
Stability
Not Overloaded | UP 7h 25m 53s ago | UP 18% (1M)
Reachability
IPv4: 7/9 (Directory Auths)
First Seen
5d 2h 17m ago
BW Weight
0.00% of Network | 319 Kbit/s Observed By Relay
Version
0.4.8.22 Recommended
Issues Detected:
  • Guard: bandwidth below threshold : Observed bandwidth 0.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 17.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.
  • Guard: Time Known below threshold : Time Known 4.2 days is below 8 days requirement (3.8 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 17.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: 7/9 authorities can reach this relay
  • Bandwidth authority measurements below majority: 3/6 bandwidth authorities measured this relay (majority is 4).

Addresses
OR Address
197.146.252.177:9001
Reachability (Directory Authorities)
IPv4
7/9
Location
Country
Morocco Morocco
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS36884
AS Name
Wana Corporate (BGP.tools)
AS Rarity
Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

Current Flags (3): Running, Valid, V2Dir
Eligible Flags (3): Running: 7/9 | Valid: 7/9 | V2Dir: 7/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 319.5 Kbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below Median: 0.2d (0/9 DA above threshold)
Min/Max: 0.2d / 0.2d (7/9 DA, Voting / Total Eligible)
≥22.1d - 51.9d (varies)
[Stricter] moria1: ≥451.9d
Uptime Below 0.3d (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: 17.8% (0/9 DA above threshold)
Min/Max: 17.0% / 18.9% (7/9 DA, Voting / Total Eligible)
≥98.0%
Time Known Below Median: 4.2d (0/9 DA above threshold)
Min/Max: 4.0d / 4.3d (7/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 7/9 authorities assigned V2Dir flag ≥5/9 authorities
WFU Below Median: 17.8% (0/9 DA above threshold)
Min/Max: 17.0% / 18.9% (7/9 DA, Voting / Total Eligible)
≥98% (all authorities)
Time Known Below (need 3.8 more days) Median: 4.2d (0/9 DA above threshold)
Min/Max: 4.0d / 4.3d (7/9 DA, Voting / Total Eligible)
≥8 days (all authorities)
Bandwidth Below 319.5 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.

TV8115
77B9306E97598777E8AE28D196F6FBD3FAD8D311
none
printerexpert@mail2tor.com
reject: 
  1-65535
none
reject *:*
77B9306E97598777E8AE28D196F6FBD3FAD8D311
none
none
319.49 Kbit/s | 319.49 Kbit/s| 100.00 Mbit/s| 100.00 Mbit/s  Measured
0.00% | N/A | 0.00% | N/A
197.146.252.177:9001
none
none
Morocco Morocco
View on Interactive Map
AS36884 | Wana Corporate (BGP.tools)
Running Running V2Dir V2Dir Valid Valid
Match Overall Uptime (18.3%/0.0%/0.0%/0.0%)
18.3%/0.0%/0.0%/0.0%
UP 7h 25m 53s ago
5d 2h 17m ago (2026-02-06 20:00:00) | 1h 17m 30s ago (2026-02-11 21:00:00)
7h 27m 40s ago (2026-02-11 14:49:50)
2026-02-11 16:00:00
No
Linux | Tor 0.4.8.22 on Linux
0.4.8.22 | Yes | recommended

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

  • Consensus Status (need ≥5/9): In Consensus — 7/9 authorities voted.
  • Flag Eligibility (need ≥5/9 for flag): Running: 7/9 | Valid: 7/9 | V2Dir: 7/9 | Fast: 0/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9
  • Reachability: IPv4: 7/9
  • Consensus Weight (Dir. Auth.): Median: 312 bit/s | Min: 8 bit/s | Max: 312 bit/s [Warning] High deviation
  • Identified Issues:
    • Guard: bandwidth below threshold: Observed bandwidth 0.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 17.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.
    • Guard: Time Known below threshold: Time Known 4.2 days is below 8 days requirement (3.8 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 17.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: 7/9 authorities can reach this relay
    • Bandwidth authority measurements below majority: 3/6 bandwidth authorities measured this relay (majority is 4).

Green = meets threshold, Red = below threshold, Yellow = partial.

Metric Dir Auth Measured Dir Auth Threshold Status
In Consensus (Dir. Auth.) 7/9 authorities ≥5/9 (majority) IN CONSENSUS
Running (IPv4 Reachable) 7/9 authorities reached this relay ≥5/9 (majority) RUNNING
Valid 7/9 (Running + Valid Descriptor) ≥5/9 (majority) VALID
Consensus Weight (Dir. Auth.) 312 bit/s (median) N/A (no threshold, used for path selection)
Guard WFU (Dir. Auth., guard-wfu) 17.8% ≥98% (all authorities) BELOW - cannot get Guard
Guard TK (Dir. Auth., tk) 4.2 days ≥8 days (all authorities) BELOW - need 3.8 more days
Guard BW (Relay Reported) 319.5 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.3d ≥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) 319.5 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) 17.8% ≥98.0% (from all auths) BELOW - 0/9
HSDir TK (Dir. Auth., tk) 4.2 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.9d
BELOW - 0/9

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 Running, Valid, V2Dir 319.5 Kbit/s | 816.0 Kbit/s 319.5 Kbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 17.8% | 98% 4.2d | 8d 0.2d | 51.9d 0.3d | 7.5d 17.8% | 98.0% 4.2d | 1.0d 2026-02-11 14:54:45 24 bit/s
dannenberg (DE) Yes Yes N Yes Running, Valid, V2Dir 319.5 Kbit/s | 712.0 Kbit/s 319.5 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 17.0% | 98% 4.2d | 6d 0.2d | 22.1d 0.3d | 6.5d 17.0% | 98.0% 4.2d | 1.0d 2026-02-11 14:54:45 312 bit/s
dizum (NL) Yes Yes N Yes Running, Valid, V2Dir 319.5 Kbit/s | 704.0 Kbit/s 319.5 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 17.7% | 98% 4.3d | 6d 0.2d | 27.7d 0.3d | 6.4d 17.7% | 98.0% 4.3d | 1.0d 2026-02-11 14:54:45 312 bit/s
faravahar (US) Yes Yes N Yes Running, Valid, V2Dir 319.5 Kbit/s | 816.0 Kbit/s 319.5 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 18.2% | 98% 4.2d | 8d 0.2d | 47.9d 0.3d | 7.5d 18.2% | 98.0% 4.2d | 1.0d 2026-02-11 14:54:45 312 bit/s
gabelmoo (DE) Yes Yes Y Yes Running, Valid, V2Dir 319.5 Kbit/s | 816.0 Kbit/s 319.5 Kbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 17.5% | 98% 4.3d | 8d 0.2d | 60.4d 0.3d | 7.5d 17.5% | 98.0% 4.3d | 1.0d 2026-02-11 14:54:45 8 bit/s
longclaw (US) No Y No
maatuska (SE) Yes Yes Y Yes Running, Valid, V2Dir 319.5 Kbit/s | 816.0 Kbit/s 319.5 Kbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 18.9% | 98% 4.0d | 8d 0.2d | 41.8d 0.3d | 7.5d 18.9% | 98.0% 4.0d | 1.0d 2026-02-11 14:54:45 312 bit/s
moria1 (US) No Y No
tor26 (AT) Yes Yes Y Yes Running, Valid, V2Dir 319.5 Kbit/s | 816.0 Kbit/s 319.5 Kbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 18.6% | 98% 4.1d | 8d 0.2d | 57.3d 0.3d | 7.5d 18.6% | 98.0% 4.1d | 1.0d 2026-02-11 14:54:45 8 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.