View Relay "troloke"

Family: 12 relays | olokerunningtor aT protonmail dot com | AS207483 | Turkey | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Fast, Running, Stable, Valid (4)
BW Verified
5/6 BW Auths Measured 31 Kbit/s Median
Stability
Overloaded | UP 1w 1d 21h ago | UP 74% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
7mo 1w 1d ago
BW Weight
0.00% of Network | 33 Mbit/s Observed By Relay
Version
0.4.8.21 Recommended
Issues Detected:
  • Guard: WFU below threshold : Weighted Fractional Uptime 78.5% 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.
  • HSDir: WFU below threshold : WFU 78.5% 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.
  • General Overload Active : Relay reported general overload at 2026-01-09 10:00 UTC. This indicates OOM killer invocation, onionskin queue saturation, or TCP port exhaustion.
    Suggestion: Check CPU/memory with htop. Review logs for "out of memory" or "onionskins" warnings. Consider increasing MaxMemInQueues in torrc. Verify TCP ports available.

Connectivity and Location

Addresses
OR Address
93.180.134.118:9009
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Turkey Turkey
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS207483
AS Name
Netvia Bilisim Yazilim Dan. Tic. Ltd. Sti. (BGP.tools)

Flags and Eligibility

Current Flags (4): Stable, Fast, Running, 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 78.5% (DA) ≥98% (all authorities)
Time Known Meets 15.1 days (DA) ≥8 days (all authorities)
Bandwidth Meets (≥2 MB/s) 33.4 Mbit/s (R) ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s
Stable MTBF Below 15 days (DA) ≥26.6d - 45.4d (varies)
Uptime Below 8.9d (R) ≥19.1d - 19.7d (varies)
Fast Speed Meets (≥100 KB/s) 33.4 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
HSDir WFU Below 78.5% (DA) ≥98.0%
Time Known Meets 15.1 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
troloke
Fingerprint
D7E182700094A899D8012DFF91366E55DEF4994E
AROI (?)
none
Contact
olokerunningtor aT protonmail dot com
IPv4 Exit Policy Summary 
reject: 
  1-65535
IPv6 Exit Policy Summary 
none
Exit Policy 
reject *:*
Effective Family Members: 12 (View) 
00E1290EBA8EE2D60119754DBD9AD1067B2A7712
0D9402490CEBE29E10A56A6A8F4F64B9A68B804B
7E078B6363BDA7C5FE5B57A0B0513EDC0C672789
864B82238623469A1B05B9F25A8B52025FA8AEA1
893B42BA688BE6FC7506537CEE4F36C951D3E117
9DBE05A77C7609309A85D25ACC02132C02B26BF7
B2A1FFAEB5D1161FC34535539BFC58FBAE071210
B5584189B9AB3D6E5E6A462CB720463D1BE05212
BB2584CC414A8E09C3792BDEA3F6C853F44E7849
D7E182700094A899D8012DFF91366E55DEF4994E
E4D301A5ED0B83E3AF16BB8412B6C52EC8323F4C
ECB7CADAC157135CD4DB8C298E3CE1593239097C
Alleged Family Members: 2 
8D4C6E4B7BA707FCB47A65282C321CB13A52C46E
956AB97F7B7E25D823FDD35617E8FE060E5D81D4
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
33.40 Mbit/s | 33.40 Mbit/s| 33.55 Mbit/s| 50.33 Mbit/s  Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
0.00% | N/A | 0.00% | N/A
OR Address
93.180.134.118:9009
Exit Address
none
Dir Address
none
Country
Turkey Turkey
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS207483 | Netvia Bilisim Yazilim Dan. Tic. Ltd. Sti. (BGP.tools)
Flags: 4
Fast Fast Running Running Stable Stable Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
73.8%/79.0%/81.8%/—
Uptime (1M/6M/1Y/5Y)
74.1%/79.1%/82.0%/0.0%
Uptime / Downtime
UP 1w 1d 21h ago
Seen (First | Last)
7mo 1w 1d ago (2025-06-05 14:00:00) | 1h 54m 57s ago (2026-01-10 03:00:00)
Last Restarted
1w 1d 21h ago (2026-01-01 07:02:18)
Last Changed Address or Port
2025-06-05 14: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: 31.2 Kbit/s | Min: 22.4 Kbit/s | Max: 33.4 Kbit/s
  • Identified Issues:
    • Guard: WFU below threshold: Weighted Fractional Uptime 78.5% 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.
    • HSDir: WFU below threshold: WFU 78.5% 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.
    • General Overload Active: Relay reported general overload at 2026-01-09 10:00 UTC. This indicates OOM killer invocation, onionskin queue saturation, or TCP port exhaustion.
      • Suggestion: Check CPU/memory with htop. Review logs for "out of memory" or "onionskins" warnings. Consider increasing MaxMemInQueues in torrc. Verify TCP ports available.

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.) 31.2 Kbit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 78.5% ≥98% (all authorities) BELOW - cannot get Guard
Guard TK (Dir. Auth., tk) 15.1 days ≥8 days (all authorities) MEETS
Guard BW (Relay Reported) 33.4 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s MEETS - ≥2 MB/s guarantee
Stable Uptime (Relay Reported) 8.9d ≥19.1d - 19.7d (typical) BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf) 15 days ≥26.6d - 45.4d (typical)
[Stricter] moria1: ≥376.2d 		BELOW - 1/9
Fast Speed (Relay Reported) 33.4 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) 78.5% ≥98.0% (from all auths) BELOW - 0/9
HSDir TK (Dir. Auth., tk) 15.1 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, Stable, Valid 33.4 Mbit/s | 816.0 Kbit/s 33.4 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 78.5% | 98% 15.1d | 8d 9.2d | 47.0d 8.9d | 19.7d 78.5% | 98.0% 15.1d | 1.0d 2026-01-09 19:06:13 31.2 Kbit/s
dannenberg (DE) Yes Yes N Yes Fast, Running, Stable, Valid 33.4 Mbit/s | 816.0 Kbit/s 33.4 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 80.1% | 98% 16.3d | 8d 11.0d | 35.7d 8.9d | 20.2d 80.1% | 98.0% 16.3d | 1.0d 2026-01-09 19:06:13 33.4 Kbit/s
dizum (NL) Yes Yes N Yes Fast, Running, Stable, Valid 33.4 Mbit/s | 816.0 Kbit/s 33.4 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 77.8% | 98% 14.6d | 8d 8.5d | 26.6d 8.9d | 20.4d 77.8% | 98.0% 14.6d | 1.0d 2026-01-09 19:06:13 33.4 Kbit/s
faravahar (US) Yes Yes N Yes Fast, Running, Stable, Valid 33.4 Mbit/s | 816.0 Kbit/s 33.4 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 78.2% | 98% 14.9d | 8d 9.1d | 41.9d 8.9d | 19.1d 78.2% | 98.0% 14.9d | 1.0d 2026-01-09 19:06:13 33.4 Kbit/s
gabelmoo (DE) Yes Yes Y Yes Fast, Running, Stable, Valid 33.4 Mbit/s | 816.0 Kbit/s 33.4 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 78.4% | 98% 15.1d | 8d 9.2d | 45.4d 8.9d | 19.6d 78.4% | 98.0% 15.1d | 1.0d 2026-01-09 19:06:13 22.4 Kbit/s
longclaw (US) Yes Yes Y Yes Fast, Running, Stable, Valid 33.4 Mbit/s | 816.0 Kbit/s 33.4 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 78.2% | 98% 14.9d | 8d 9.2d | 48.7d 8.9d | 19.5d 78.2% | 98.0% 14.9d | 1.0d 2026-01-09 19:06:13 33.4 Kbit/s
maatuska (SE) Yes Yes Y Yes Fast, Running, Stable, Valid 33.4 Mbit/s | 816.0 Kbit/s 33.4 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 80.3% | 98% 16.4d | 8d 11.1d | 42.3d 8.9d | 19.4d 80.3% | 98.0% 16.4d | 1.0d 2026-01-09 19:06:13 24.8 Kbit/s
moria1 (US) Yes Yes Y Yes Fast, Running, Stable, Valid 33.4 Mbit/s | 8.4 Mbit/s 33.4 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 76.8% | 98% 9.8d | 8d 4491.9d | 376.2d 8.9d | 20.4d 76.8% | 98.0% 9.8d | 9.9d 2026-01-09 19:06:13 29.6 Kbit/s
tor26 (AT) Yes Yes Y Yes Fast, Running, Stable, Valid 33.4 Mbit/s | 816.0 Kbit/s 33.4 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 80.2% | 98% 16.4d | 8d 11.1d | 51.8d 8.9d | 19.7d 80.2% | 98.0% 16.4d | 1.0d 2026-01-09 19:06:13 27.2 Kbit/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.