View Relay "bdoloke"

Fingerprint: BB2584CC414A8E09C3792BDEA3F6C853F44E7849 | Family: 6 relays | olokerunningtor aT protonmail dot com | AS147181 | Bangladesh | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Stable (4)
BW Verified
5/7 BW Auths Measured 64 bit/s Median
Stability
Not Overloaded | UP 1w 2d 16h ago | UP 100% (1M)
Reachability
IPv4: 9/9 | v6: 8/8 (Directory Auths)
First Seen
1w 2d 22h ago
BW Weight
0.00% of Network | 702 Kbit/s Observed By Relay
Version
0.4.9.14 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: bandwidth below threshold : Observed bandwidth 702 Kbit/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 54.2% 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: 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: WFU below threshold : WFU 54.2% 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.

Connectivity and Location

Addresses
OR Address
bd.oloke.xyz
103.174.51.78:9003
[2001:df1:8f40:24::a]:9003
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
Location
Country
Bangladesh Bangladesh
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS147181
AS Name
Flarezen Ltd. (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 2 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Stable
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 1/9 | Stable: 9/9 | HSDir: 1/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
IPv6 Reachability Meets (8/8 DA) 8/8 tested authorities reached relay ≥5/8 tested (majority) (≥5/8 DA)
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 Below (0/9 DA) 702.2 Kbit/s (R) ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Partial (8/9 DA) Median: 10.3d (9/9 DA above threshold)
Min/Max: 9.7d / 763.8d (9/9 DA, Voting / Total Eligible)		 ≥6.1d - 9.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10198.2d
Uptime Meets (9/9 DA) 9.7d (R) ≥5.7d - 5.7d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (1/9 DA) 1/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 Meets (9/9 DA) 9/9 DA assigned Stable ≥6.1d - 9.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10198.2d
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: 55.5% (0/9 DA above threshold)
Min/Max: 54.1% / 67.9% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 19.2d (9/9 DA above threshold)
Min/Max: 9.7d / 19.8d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.7d
Guard Prereq: Fast Below (1/9 DA) 1/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 Meets (9/9 DA) 9/9 DA assigned Stable ≥6.1d - 9.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10198.2d
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: 55.5% (0/9 DA above threshold)
Min/Max: 54.1% / 67.9% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 19.2d (9/9 DA above threshold)
Min/Max: 9.7d / 19.8d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 702.2 Kbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-312.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-10-17 23:00:36).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
702.23 Kbit/s
Advertised Bandwidth
655.36 Kbit/s
Rate Limit
655.36 Kbit/s
Burst Limit
983.04 Kbit/s
Total Data
2.9 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-10-17 23:00:36

Measured By
5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Median Measurement
64 bit/s
Min / Max
16 bit/s / 648 bit/s
Deviation
632 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (2th pctl) | Guard: N/A | Middle: 0.0000% (2th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 1w 2d 16h ago
Overall Uptime (1M/6M/1Y/5Y)
100.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (100.0%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
1w 2d 22h ago (2026-10-08 01:00:00)
Last Seen
2h 6m 48s ago (2026-10-17 21:00:00)
Last Restarted
1w 2d 16h ago (2026-10-08 06:33:13)
Last Changed Address
2026-10-08 01:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-10-17 14:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
olokerunningtor aT protonmail dot com
Family Configuration
Family Support
MyFamily Only (6) — Legacy only. Consider migrating to Happy Families. | View Full Family (6)
Happy Families (family-cert)
Effective Members: 0
none

Software and Version

Platform
Linux — Tor 0.4.9.14 on Linux
Version
0.4.9.14 — 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, 17 Oct 2026 23:06:30 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-10-17 23:00:36).

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 v6 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 Yes Running, Valid, V2Dir, Stable 702.2 Kbit/s | 816.0 Kbit/s 702.2 Kbit/s | 184.0 Mbit/s OR 16.0 Mbit/s 54.2% | 98% 19.4d | 8d 10.1d | 9.0d 9.7d | 5.7d 54.2% | 98.0% 19.4d | 1.0d 2026-10-17 13:33:29 64 bit/s
dannenberg (DE) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Stable 702.2 Kbit/s | 816.0 Kbit/s 702.2 Kbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 56.3% | 98% 19.2d | 8d 10.4d | 6.1d 9.7d | 5.8d 56.3% | 98.0% 19.2d | 1.0d 2026-10-17 13:33:29 16 bit/s
dizum (NL) Yes Yes No — N Yes Yes Running, Valid, V2Dir, Stable 702.2 Kbit/s | 816.0 Kbit/s 702.2 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 55.1% | 98% 19.8d | 8d 10.3d | 9.0d 9.7d | 5.7d 55.1% | 98.0% 19.8d | 1.0d 2026-10-17 13:33:29 648 bit/s
faravahar (US) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir 702.2 Kbit/s | 816.0 Kbit/s 702.2 Kbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 55.5% | 98% 19.0d | 8d 9.7d | 9.5d 9.7d | 6.3d 55.5% | 98.0% 19.0d | 1.0d 2026-10-17 13:33:29 648 bit/s
gabelmoo (DE) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Stable 702.2 Kbit/s | 816.0 Kbit/s 702.2 Kbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 54.1% | 98% 19.4d | 8d 9.9d | 9.0d 9.7d | 5.7d 54.1% | 98.0% 19.4d | 1.0d 2026-10-17 13:33:29 24 bit/s
longclaw (US) Yes Yes No — Y Yes — Running, Valid, V2Dir, Stable 702.2 Kbit/s | 816.0 Kbit/s 702.2 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 56.0% | 98% 19.2d | 8d 10.4d | 9.2d 9.7d | 5.7d 56.0% | 98.0% 19.2d | 1.0d 2026-10-17 13:33:29 648 bit/s
maatuska (SE) Yes Yes No — N Yes Yes Running, Valid, V2Dir, Stable 702.2 Kbit/s | 816.0 Kbit/s 702.2 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 55.2% | 98% 18.9d | 8d 9.9d | 8.8d 9.7d | 5.7d 55.2% | 98.0% 18.9d | 1.0d 2026-10-17 13:33:29 648 bit/s
moria1 (US) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Stable 702.2 Kbit/s | 8.4 Mbit/s 702.2 Kbit/s | 192.0 Mbit/s OR 16.0 Mbit/s 67.9% | 98% 9.7d | 8d 763.8d | 10198.2d 9.7d | 5.7d 67.9% | 98.0% 9.74d | 9.73d 2026-10-17 13:33:29 40 bit/s
tor26 (AT) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Stable 702.2 Kbit/s | 816.0 Kbit/s 702.2 Kbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 56.1% | 98% 19.3d | 8d 10.4d | 9.3d 9.7d | 5.7d 56.1% | 98.0% 19.3d | 1.0d 2026-10-17 13:33:29 24 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.