View Relay "vnoloke"

Fingerprint: B5584189B9AB3D6E5E6A462CB720463D1BE05212 | Family: 11 relays | olokerunningtor aT protonmail dot com | AS152992 | Viet Nam | Linux

Consensus
In Consensus (8/8 Directory Auths)
BW Verified
4/5 BW Auths Measured 8 Kbit/s Median
Stability
Not Overloaded | UP 1mo 4d 15h ago | UP 94% (1M)
Reachability
IPv4: 8/9 (Directory Auths)
BW Weight
0.00% of Network | 11 Mbit/s Observed By Relay
Version
0.4.9.6 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 1.4 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 0.0% 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 0.0 days is below 8 days requirement (8.0 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 0.0% 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.
  • HSDir: Time Known below threshold : Time Known 0.0 hours below 25 hours (dir-spec default)
    Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.
  • 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: 8/9 authorities can reach this relay

Addresses
OR Address
160.187.1.243:9003
Reachability (Directory Authorities)
IPv4
8/9
Location
Country
Viet Nam Viet Nam
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS152992
AS Name
ONLINE DATA COMPANY LIMITED (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 2 operators)

Current Flags (4): Running, Valid, V2Dir, Fast
Eligible Flags (4): Running: 8/8 | Valid: 8/8 | V2Dir: 8/8 | Fast: 6/8 | Stable: 4/8 | HSDir: 2/8 | Guard: 0/8 | Exit: 0/8
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (8/8 DA) 8/8 authorities reached relay ≥5/8 DA ORPort reachable
Valid Descriptor Meets (8/8 DA) 8/8 authorities assigned Valid Not blacklisted + valid descriptor (≥5/8 DA)
V2Dir DirPort Available Meets (8/8 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/8 DA)
Fast Speed Meets (8/8 DA) 11.5 Mbit/s (R) ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (0/8 DA) Median: 3.2d (0/8 DA above threshold)
Min/Max: 0.0d / 17.5d (8/8 DA, Voting / Total Eligible)
≥16.4d - 57.7d (varies) (≥5/8 DA)
Uptime Meets (8/8 DA) 34.6d (R) ≥10.4d - 11.0d (varies) (≥5/8 DA)
HSDir Prereq: Fast Meets (6/8 DA) 6/8 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (4/8 DA) 4/8 DA assigned Stable ≥16.4d - 57.7d (varies) (≥5/8 DA)
Prereq: V2Dir Meets (8/8 DA) 8/8 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/8 DA)
WFU Below (4/8 DA) Median: 49.8% (4/8 DA above threshold)
Min/Max: 0.0% / 99.9% (8/8 DA, Voting / Total Eligible)
≥98.0% (≥5/8 DA)
Time Known Below (4/8 DA) Median: 8.7d (4/8 DA above threshold)
Min/Max: 0.0d / 22.0d (8/8 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/8 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Meets (6/8 DA) 6/8 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (4/8 DA) 4/8 DA assigned Stable ≥16.4d - 57.7d (varies) (≥5/8 DA)
Prereq: V2Dir Meets (8/8 DA) 8/8 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/8 DA)
WFU Below (4/8 DA) Median: 49.8% (4/8 DA above threshold)
Min/Max: 0.0% / 99.9% (8/8 DA, Voting / Total Eligible)
≥98% (≥5/8 DA)
Time Known Meets (4/8 DA) Median: 8.7d (4/8 DA above threshold)
Min/Max: 0.0d / 22.0d (8/8 DA, Voting / Total Eligible)
≥8 days (≥5/8 DA)
Bandwidth Below (0/8 DA) 11.5 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-328.0 Mbit/s (≥5/8 DA)
Exit Exit Policy Below (0/8 DA) Port 80: No | Port 443: No (R) Allows ≥1 /8 on ports 80 AND 443 (≥5/8 DA)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-04-29 21:45:07).

Capacity (Relay Reported)
Observed Bandwidth
11.49 Mbit/s
Advertised Bandwidth
11.49 Mbit/s
Rate Limit
83.89 Mbit/s
Burst Limit
134.22 Mbit/s
Total Data
2.5 TB (1 year)
1mo: 162 GB | 6mo: 1.2 TB | 1y: 2.5 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-04-29 21:45:07

Measured By
4/5 Bandwidth Authorities
Not measured by: gabelmoo
Median Measurement
8.5 Kbit/s
Min / Max
1760 bit/s / 11.5 Kbit/s
Deviation
9.7 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0002% of network (10th pctl) | Guard: N/A | Middle: 0.0006% (11th pctl) | Exit: N/A

Uptime Metrics
Current Status
UP 1mo 4d 15h ago
Overall Uptime (1M/6M/1Y/5Y)
94.8%/93.8%/94.4%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
—/93.2%/94.0%/—
Hibernating
No
Timestamps
First Seen
3w 1d 22h ago (2026-04-06 23:00:00)
Last Seen
1h 45m 38s ago (2026-04-29 20:00:00)
Last Restarted
1mo 4d 15h ago (2026-03-26 06:31:45)
Last Changed Address
2026-04-06 23:00:00
Overload Status: Not Overloaded — No overload conditions reported.

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

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, 29 Apr 2026 21:45:37 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-04-29 21:45:07).

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) No N No
dannenberg (DE) Yes Yes No N Yes Valid, V2Dir, Fast 11.5 Mbit/s | 816.0 Kbit/s 11.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 0.0% | 98% 0.0d | 8d 0.0d | 46.8d 34.6d | 10.8d 0.0% | 98.0% 0.0d | 1.0d 2026-04-29 19:14:15 11.5 Kbit/s
dizum (NL) Yes Yes No N Yes Running, Valid, V2Dir, Fast, Stable, HSDir 11.5 Mbit/s | 816.0 Kbit/s 11.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.8% | 98% 18.1d | 8d 8.0d | 42.5d 34.6d | 10.4d 99.8% | 98.0% 18.1d | 1.0d 2026-04-28 06:29:09 11.5 Kbit/s
faravahar (US) Yes Yes No N Yes Running, Valid, V2Dir, Fast, Stable 11.5 Mbit/s | 816.0 Kbit/s 11.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.7% | 98% 17.5d | 8d 6.4d | 57.7d 34.6d | 11.0d 99.7% | 98.0% 17.5d | 1.0d 2026-04-29 19:14:15 11.5 Kbit/s
gabelmoo (DE) Yes Yes No Y Yes Valid, V2Dir 11.5 Mbit/s | 816.0 Kbit/s 11.5 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 0.0% | 98% 0.0d | 8d 0.0d | 57.6d 34.6d | 11.1d 0.0% | 98.0% 0.0d | 1.0d 2026-04-29 19:14:15 11.5 Kbit/s
longclaw (US) Yes Yes No Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir 11.5 Mbit/s | 816.0 Kbit/s 11.5 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 99.9% | 98% 22.0d | 8d 17.5d | 63.0d 34.6d | 10.9d 99.9% | 98.0% 22.0d | 1.0d 2026-04-29 19:14:15 2960 bit/s
maatuska (SE) Yes Yes No Y Yes Valid, V2Dir, Fast 11.5 Mbit/s | 816.0 Kbit/s 11.5 Mbit/s | 328.0 Mbit/s OR 16.0 Mbit/s 0.0% | 98% 0.0d | 8d 0.0d | 16.4d 34.6d | 10.8d 0.0% | 98.0% 0.0d | 1.0d 2026-04-29 19:14:15 1760 bit/s
moria1 (US) Yes Yes No Y Yes Valid, V2Dir 11.5 Mbit/s | 8.4 Mbit/s 11.5 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 0.0% | 98% 0.0d | 8d 0.0d | 281.0d 34.6d | 12.6d 0.0% | 98.0% 0.0d | 9.9d 2026-04-29 19:14:15 5520 bit/s
tor26 (AT) Yes Yes No Y Yes Running, Valid, V2Dir, Fast, Stable 11.5 Mbit/s | 816.0 Kbit/s 11.5 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 99.8% | 98% 20.3d | 8d 10.2d | 58.0d 34.6d | 11.4d 99.8% | 98.0% 20.3d | 1.0d 2026-04-29 19:14:15 1920 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.