View Relay "TV241"

Fingerprint: D3FDAFA7CD95A29FFCFF0F65399BEB50532A1C4C | Family: 1 relay | printerexpert@mail2tor.com | AS36925 | Morocco | Linux

Health Status

Consensus
In Consensus (8/9 Directory Auths)
Flags
Running, Valid, V2Dir (3)
BW Verified
2/7 BW Auths Measured 3992 bit/s Median
Stability
Not Overloaded | DOWN 5d 4h 45m ago | UP 1% (1M)
Reachability
IPv4: 8/9 (Directory Auths)
First Seen
4mo 6d 17h ago
BW Weight
0.00% of Network | 4 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 0.5 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 4.4% 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.4 days is below 8 days requirement (2.6 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 4.4% 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 2/7 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.
  • 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.
  • 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: 8/9 authorities can reach this relay

Connectivity and Location

Addresses
OR Address
105.188.58.143:9001
Reachability (Directory Authorities)
IPv4
8/9
Location
Country
Morocco Morocco
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS36925
AS Name
MEDITELECOM (BGP.tools)
AS Rarity
Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

Flags and Eligibility

Current Flags (3): Running, Valid, V2Dir
Eligible Flags (3): Running: 8/9 | Valid: 8/9 | V2Dir: 8/9 | Fast: 3/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 0/9
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (8/9 DA) 8/9 authorities reached relay ≥5/9 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 (8/9 DA) 8/9 authorities assigned Valid Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir DirPort Available Meets (8/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 4.0 Mbit/s (R) ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (0/9 DA) Median: 0.4d (0/9 DA above threshold)
Min/Max: 0.4d / 0.4d (8/9 DA, Voting / Total Eligible)		 ≥31.1d - 55.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥286.0d
Uptime Below (0/9 DA) 5.7d (R) ≥10.0d - 10.0d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (3/9 DA) 3/9 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (0/9 DA) 0/9 DA assigned Stable ≥31.1d - 55.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥286.0d
Prereq: V2Dir Meets (8/9 DA) 8/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 4.4% (0/9 DA above threshold)
Min/Max: 4.3% / 4.5% (8/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 5.4d (0/9 DA above threshold)
Min/Max: 5.3d / 5.4d (8/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Below (3/9 DA) 3/9 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (0/9 DA) 0/9 DA assigned Stable ≥31.1d - 55.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥286.0d
Prereq: V2Dir Meets (8/9 DA) 8/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 4.4% (0/9 DA above threshold)
Min/Max: 4.3% / 4.5% (8/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 2.6 more days) Median: 5.4d (0/9 DA above threshold)
Min/Max: 5.3d / 5.4d (8/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 4.0 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-320.0 Mbit/s (≥5/9 DA)
Exit Exit Policy Below (0/9 DA) Port 80: No | Port 443: No (R) Allows ≥1 /8 on ports 80 AND 443 (≥5/9 DA)

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

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
4.00 Mbit/s
Advertised Bandwidth
4.00 Mbit/s
Rate Limit
100.00 Mbit/s
Burst Limit
100.00 Mbit/s
Total Data
1.5 GB (6 months)
1mo: 851 MB | 6mo: 1.5 GB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-06-17 11:15:06

Measured By
2/7 Bandwidth Authorities
Not measured by: bastet, dannenberg, longclaw, maatuska, moria1
Median Measurement
3992.0 bit/s
Min / Max
8 bit/s / 3992 bit/s
Deviation
3984 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 and Stability

Uptime Metrics
Current Status
DOWN 5d 4h 45m ago
Overall Uptime (1M/6M/1Y/5Y)
1.3%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (1.3%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
4mo 6d 17h ago (2026-02-10 18:00:00)
Last Seen
5d 4h 45m ago (2026-06-12 07:00:00)
Last Restarted
5d 16h 10m ago (2026-06-11 19:35:13)
Last Changed Address
2026-06-11 22:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-06-17 04: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 
D3FDAFA7CD95A29FFCFF0F65399BEB50532A1C4C (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
Not an exit relay — DNS health testing does not apply.
IPv4 Exit Policy Summary
reject: 
  1-65535
IPv6 Exit Policy Summary
None
Full Exit Policy
reject *:*

Last fetch was at Wed, 17 Jun 2026 11:45:33 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-06-17 11:15:06).

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 No — Y Yes Valid, V2Dir, StaleDesc 4.0 Mbit/s | 816.0 Kbit/s 4.0 Mbit/s | 256.0 Mbit/s OR 16.0 Mbit/s 4.4% | 98% 5.4d | 8d 0.4d | 57.5d 5.7d | 11.0d 4.4% | 98.0% 5.4d | 1.0d 2026-06-16 15:22:55 [Stale] 3992 bit/s
dannenberg (DE) Yes Yes No — Y Yes Valid, V2Dir, Fast, StaleDesc 4.0 Mbit/s | 816.0 Kbit/s 4.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 4.5% | 98% 5.4d | 8d 0.4d | 31.1d 5.7d | 10.0d 4.5% | 98.0% 5.4d | 1.0d 2026-06-16 15:22:55 [Stale] 3992 bit/s
dizum (NL) Yes Yes No — N Yes Valid, V2Dir, Fast, StaleDesc 4.0 Mbit/s | 816.0 Kbit/s 4.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 4.4% | 98% 5.4d | 8d 0.4d | 36.3d 5.7d | 10.0d 4.4% | 98.0% 5.4d | 1.0d 2026-06-16 15:22:55 [Stale] 3992 bit/s
faravahar (US) Yes Yes No — N Yes Valid, V2Dir, Fast, StaleDesc 4.0 Mbit/s | 816.0 Kbit/s 4.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 4.4% | 98% 5.4d | 8d 0.4d | 53.4d 5.7d | 10.0d 4.4% | 98.0% 5.4d | 1.0d 2026-06-16 15:22:55 [Stale] 3992 bit/s
gabelmoo (DE) Yes Yes No — Y Yes Valid, V2Dir, StaleDesc 4.0 Mbit/s | 816.0 Kbit/s 4.0 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 4.4% | 98% 5.4d | 8d 0.4d | 55.0d 5.7d | 10.0d 4.4% | 98.0% 5.4d | 1.0d 2026-06-16 15:22:55 [Stale] 8 bit/s
longclaw (US) Yes Yes No — Y Yes Valid, V2Dir, StaleDesc 4.0 Mbit/s | 816.0 Kbit/s 4.0 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 4.4% | 98% 5.4d | 8d 0.4d | 61.5d 5.7d | 10.0d 4.4% | 98.0% 5.4d | 1.0d 2026-06-16 15:22:55 [Stale] 3992 bit/s
maatuska (SE) Yes Yes No — Y Yes Valid, V2Dir, StaleDesc 4.0 Mbit/s | 816.0 Kbit/s 4.0 Mbit/s | 320.0 Mbit/s OR 16.0 Mbit/s 4.3% | 98% 5.3d | 8d 0.4d | 32.9d 5.7d | 10.0d 4.3% | 98.0% 5.3d | 1.0d 2026-06-16 15:22:55 [Stale] 3992 bit/s
moria1 (US) No — — — Y No — — — — — — — — — — —
tor26 (AT) Yes Yes No — Y Yes Valid, V2Dir, StaleDesc 4.0 Mbit/s | 816.0 Kbit/s 4.0 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 4.4% | 98% 5.4d | 8d 0.4d | 57.4d 5.7d | 10.0d 4.4% | 98.0% 5.4d | 1.0d 2026-06-16 15:22:55 [Stale] 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.