View Relay "uzoloke"

Family: 12 relays | olokerunningtor aT protonmail dot com | AS61106 | Uzbekistan | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Fast, Running, V2Dir, Valid (4)
BW Verified
5/6 BW Auths Measured 25 Kbit/s Median
Stability
Not Overloaded | UP 3w 2d 5h ago | UP 99% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
10mo 2w 4d ago
BW Weight
0.00% of Network | 32 Mbit/s Observed By Relay
Version
0.4.8.21 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).
  • 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.
  • 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
81.162.55.28:9009
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Uzbekistan Uzbekistan
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS61106
AS Name
PS Cloud Services LLC (BGP.tools)

Flags and Eligibility

Current Flags (4): Fast, Running, V2Dir, Valid
Eligible Flags (6): Guard: 6/9 | Stable: 1/9 | Fast: 9/9 | HSDir: 6/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 Meets 99.3% (DA) ≥98% (all authorities)
Time Known Meets 52.5 days (DA) ≥8 days (all authorities)
Bandwidth Meets (≥2 MB/s) 32.1 Mbit/s (R) ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s
Stable MTBF Below 52 days (DA) ≥26.6d - 45.4d (varies)
Uptime Meets 23.2d (R) ≥19.1d - 19.7d (varies)
Fast Speed Meets (≥100 KB/s) 32.1 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
HSDir WFU Meets 99.3% (DA) ≥98.0%
Time Known Meets 52.5 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
uzoloke
Fingerprint
B2A1FFAEB5D1161FC34535539BFC58FBAE071210
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)
32.06 Mbit/s | 32.06 Mbit/s| 67.11 Mbit/s| 100.66 Mbit/s  Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
0.00% | N/A | 0.00% | N/A
OR Address
81.162.55.28:9009
Exit Address
none
Dir Address
none
Country
Uzbekistan Uzbekistan
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS61106 | PS Cloud Services LLC (BGP.tools)
Flags: 4
Fast Fast Running Running V2Dir V2Dir Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
Match Overall Uptime (99.7%/99.7%/99.8%/0.0%)
Uptime (1M/6M/1Y/5Y)
99.7%/99.7%/99.8%/0.0%
Uptime / Downtime
UP 3w 2d 5h ago
Seen (First | Last)
10mo 2w 4d ago (2025-02-26 00:00:00) | 1h 54m 58s ago (2026-01-10 03:00:00)
Last Restarted
3w 2d 5h ago (2025-12-17 23:06:34)
Last Changed Address or Port
2025-06-24 01: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: 6/9 | Stable: 1/9 | Fast: 9/9 | HSDir: 6/9 | Running: 9/9 | Valid: 9/9 | V2Dir: 9/9
  • Reachability: IPv4: 9/9
  • Consensus Weight (Dir. Auth.): Median: 25.6 Kbit/s | Min: 7120 bit/s | Max: 32.1 Kbit/s [Warning] High deviation
  • Identified Issues:
    • 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).
    • 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.
    • 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.

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.) 25.6 Kbit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 99.3% ≥98% (all authorities) MEETS
Guard TK (Dir. Auth., tk) 52.5 days ≥8 days (all authorities) MEETS
Guard BW (Relay Reported) 32.1 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s MEETS - ≥2 MB/s guarantee
Stable Uptime (Relay Reported) 23.2d ≥19.1d - 19.7d (typical) MEETS - all authorities
Stable MTBF (Dir. Auth., mtbf) 52 days ≥26.6d - 45.4d (typical)
[Stricter] moria1: ≥376.2d 		BELOW - 1/9
Fast Speed (Relay Reported) 32.1 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) 99.3% ≥98.0% (from all auths) PARTIAL - 6/9
HSDir TK (Dir. Auth., tk) 52.5 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.9d 		PARTIAL - 6/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, Guard, Running, Stable, V2Dir, Valid 32.1 Mbit/s | 816.0 Kbit/s 32.1 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 99.3% | 98% 52.5d | 8d 5.7d | 47.0d 23.2d | 19.7d 99.3% | 98.0% 52.5d | 1.0d 2026-01-09 14:23:46 19.2 Kbit/s
dannenberg (DE) Yes Yes N Yes Fast, Running, V2Dir, Valid 32.1 Mbit/s | 816.0 Kbit/s 32.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.2% | 98% 56.1d | 8d 4.8d | 35.7d 23.2d | 20.2d 99.2% | 98.0% 56.1d | 1.0d 2026-01-09 14:23:46 32.1 Kbit/s
dizum (NL) Yes Yes N Yes Fast, Running, V2Dir, Valid 32.1 Mbit/s | 816.0 Kbit/s 32.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 97.5% | 98% 14.0d | 8d 1.5d | 26.6d 23.2d | 20.4d 97.5% | 98.0% 14.0d | 1.0d 2026-01-09 14:23:46 32.1 Kbit/s
faravahar (US) Yes Yes N Yes Fast, Running, V2Dir, Valid 32.1 Mbit/s | 816.0 Kbit/s 32.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 98.5% | 98% 20.2d | 8d 3.0d | 41.9d 23.2d | 19.1d 98.5% | 98.0% 20.2d | 1.0d 2026-01-09 14:23:46 32.1 Kbit/s
gabelmoo (DE) Yes Yes Y Yes Fast, HSDir, Running, Stable, V2Dir, Valid 32.1 Mbit/s | 816.0 Kbit/s 32.1 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 99.5% | 98% 31.4d | 8d 6.0d | 45.4d 23.2d | 19.6d 99.5% | 98.0% 31.4d | 1.0d 2026-01-09 14:23:46 14.4 Kbit/s
longclaw (US) Yes Yes Y Yes Fast, Running, V2Dir, Valid 32.1 Mbit/s | 816.0 Kbit/s 32.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 95.3% | 98% 10.5d | 8d 0.9d | 48.7d 23.2d | 19.5d 95.3% | 98.0% 10.5d | 1.0d 2026-01-09 14:23:46 32.1 Kbit/s
maatuska (SE) Yes Yes Y Yes Fast, Running, V2Dir, Valid 32.1 Mbit/s | 816.0 Kbit/s 32.1 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 98.9% | 98% 15.5d | 8d 2.9d | 42.3d 23.2d | 19.4d 98.9% | 98.0% 15.5d | 1.0d 2026-01-09 14:23:46 7120 bit/s
moria1 (US) Yes Yes Y Yes Fast, Running, Stable, V2Dir, Valid 32.1 Mbit/s | 8.4 Mbit/s 32.1 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 98.0% | 98% 9.9d | 8d 17028.6d | 376.2d 23.2d | 20.4d 98.0% | 98.0% 9.9d | 9.9d 2026-01-09 14:23:46 25.6 Kbit/s
tor26 (AT) Yes Yes Y Yes Fast, Running, Stable, V2Dir, Valid 32.1 Mbit/s | 816.0 Kbit/s 32.1 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 99.7% | 98% 58.9d | 8d 10.9d | 51.8d 23.2d | 19.7d 99.7% | 98.0% 58.9d | 1.0d 2026-01-09 14:23:46 12.8 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.