View Relay "ieditedmyconfigalil"

Fingerprint: F9E2261E6A5F678CD5CCF80B326F402EB43F4E95 | Family: 1 relay | 8a6rjyxql@mozmail.com | AS37611 | South Africa | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Fast (4)
BW Verified
7/8 BW Auths Measured 2160 bit/s Median
Stability
Overloaded | DOWN 2h 16m 27s ago | UP 92% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
1w 3d 1h ago
BW Weight
0.00% of Network | 7 Mbit/s Observed By Relay
Version
0.4.9.10 Recommended
Issues Detected:
  • 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 7 Mbit/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 91.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 7.4 days is below 8 days requirement (0.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 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 91.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.
  • File Descriptor Exhaustion : Relay ran out of file descriptors at 2026-07-25 04:00 UTC. This severely impacts connections and performance.
    Suggestion: Increase file descriptor limits: For systemd: add "LimitNOFILE=65535" to [Service] section. For shell: ulimit -n 65535. Persistent: edit /etc/security/limits.conf.

Connectivity and Location

Addresses
OR Address
165-73-61-162.ip.afrihost.joburg
165.73.61.162:9001
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
South Africa South Africa
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS37611
AS Name
AFRIHOST SP (PTY) LTD (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 2 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Fast
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 7/9 | Stable: 1/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 (9/9 DA) 9/9 authorities reached relay ≥5/9 DA ORPort reachable
Valid Descriptor Meets (9/9 DA) 9/9 authorities assigned Valid Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir DirPort Available Meets (9/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 7.5 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 (1/9 DA) Median: 0.5d (1/9 DA above threshold)
Min/Max: 0.2d / 19260.4d (9/9 DA, Voting / Total Eligible)		 ≥8.0d - 12.5d (varies) (≥5/9 DA)
[Stricter] moria1: ≥9298.7d
Uptime Below (0/9 DA) 1.0d (R) ≥7.2d - 7.5d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (7/9 DA) 7/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 (1/9 DA) 1/9 DA assigned Stable ≥8.0d - 12.5d (varies) (≥5/9 DA)
[Stricter] moria1: ≥9298.7d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 87.9% (0/9 DA above threshold)
Min/Max: 77.7% / 91.8% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 7.2d (0/9 DA above threshold)
Min/Max: 3.9d / 7.4d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥10.0d
Guard Prereq: Fast Meets (7/9 DA) 7/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 (1/9 DA) 1/9 DA assigned Stable ≥8.0d - 12.5d (varies) (≥5/9 DA)
[Stricter] moria1: ≥9298.7d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 87.9% (0/9 DA above threshold)
Min/Max: 77.7% / 91.8% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 0.8 more days) Median: 7.2d (0/9 DA above threshold)
Min/Max: 3.9d / 7.4d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 7.5 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-304.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-07-25 10:15:09).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
7.50 Mbit/s
Advertised Bandwidth
7.50 Mbit/s
Rate Limit
125.83 Mbit/s
Burst Limit
167.77 Mbit/s
Total Data
32 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-07-25 10:15:09

Measured By
7/8 Bandwidth Authorities
Not measured by: bastet
Median Measurement
2160 bit/s
Min / Max
8 bit/s / 7488 bit/s
Deviation
7480 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0001% of network (6th pctl) | Guard: N/A | Middle: N/A | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
DOWN 2h 16m 27s ago
Overall Uptime (1M/6M/1Y/5Y)
92.8%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
44.5%/—/—/—
Hibernating
No
Timestamps
First Seen
1w 3d 1h ago (2026-07-15 10:00:00)
Last Seen
2h 16m 27s ago (2026-07-25 09:00:00)
Last Restarted
23h 40m 38s ago (2026-07-24 11:35:49)
Last Changed Address
2026-07-15 10:00:00
[Warning] OVERLOADED — FD exhaustion (last: 2026-07-25)
General Overload (from /details)
Status
Not Reported

OOM killer, onionskin queue saturation, or TCP port exhaustion. Flag remains 72h after last event (Tor spec 328).

File Descriptor Exhaustion (from /bandwidth)
Status
Reported — 2026-07-25 04:00 UTC (7 hours ago)
Rate Limits (from /bandwidth)

No rate limit data from /bandwidth endpoint.

Recommendations
  • Increase FD limit: ulimit -n 65535
  • systemd: LimitNOFILE=65535 in [Service]

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-07-25 03:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
8a6rjyxql@mozmail.com
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
F9E2261E6A5F678CD5CCF80B326F402EB43F4E95 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

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

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 Sat, 25 Jul 2026 11:16:24 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-07-25 10:15:09).

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 Running, Valid, V2Dir, Fast 7.5 Mbit/s | 816.0 Kbit/s 7.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 91.8% | 98% 7.4d | 8d 0.7d | 16.7d 1.0d | 7.2d 91.8% | 98.0% 7.4d | 1.0d 2026-07-25 07:24:53 7488 bit/s
dannenberg (DE) Yes Yes No — Y Yes Running, Valid, V2Dir 7.5 Mbit/s | 816.0 Kbit/s 7.5 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 87.3% | 98% 7.2d | 8d 0.5d | 8.0d 1.0d | 7.4d 87.3% | 98.0% 7.2d | 1.0d 2026-07-25 07:24:53 8 bit/s
dizum (NL) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 7.5 Mbit/s | 816.0 Kbit/s 7.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 89.9% | 98% 7.3d | 8d 0.5d | 11.7d 1.0d | 7.4d 89.9% | 98.0% 7.3d | 1.0d 2026-07-25 07:24:53 7488 bit/s
faravahar (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 7.5 Mbit/s | 816.0 Kbit/s 7.5 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 89.3% | 98% 7.2d | 8d 0.5d | 11.9d 1.0d | 7.7d 89.3% | 98.0% 7.2d | 1.0d 2026-07-25 07:24:53 1840 bit/s
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 7.5 Mbit/s | 816.0 Kbit/s 7.5 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 82.7% | 98% 3.9d | 7d 0.3d | 12.3d 1.0d | 7.5d 82.7% | 98.0% 3.9d | 1.0d 2026-07-25 07:24:53 1920 bit/s
longclaw (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 7.5 Mbit/s | 816.0 Kbit/s 7.5 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 77.7% | 98% 3.9d | 8d 0.2d | 24.7d 1.0d | 8.1d 77.7% | 98.0% 3.9d | 1.0d 2026-07-25 07:24:53 3040 bit/s
maatuska (SE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 7.5 Mbit/s | 816.0 Kbit/s 7.5 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 87.9% | 98% 7.1d | 8d 0.5d | 12.5d 1.0d | 8.1d 87.9% | 98.0% 7.1d | 1.0d 2026-07-25 07:24:53 1600 bit/s
moria1 (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Stable 7.5 Mbit/s | 8.4 Mbit/s 7.5 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 87.5% | 98% 6.5d | 8d 19260.4d | 9298.7d 1.0d | 7.5d 87.5% | 98.0% 6.5d | 10.0d 2026-07-25 07:24:53 2800 bit/s
tor26 (AT) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 7.5 Mbit/s | 816.0 Kbit/s 7.5 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 90.2% | 98% 7.2d | 8d 0.5d | 16.7d 1.0d | 7.5d 90.2% | 98.0% 7.2d | 1.0d 2026-07-25 07:24:53 2160 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.