View Relay "olmecrubber"

Fingerprint: 5AD9217B09AE2E3BD0FAF4A1A1B251BDA06FEAA8 | Family: 1 relay | plainjan3 | AS55720 | Malaysia | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Exit (4)
DNS Health
Not Tested (via exitdnshealth.1aeo.com)
BW Verified
4/6 BW Auths Measured 12 Kbit/s Median
Stability
Not Overloaded | UP 2d 22h 1m ago
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
2d 21h 15m ago
BW Weight
0.00% of Network | 12 Mbit/s Observed By Relay
Version
0.4.9.6 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: 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.6 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: Time Known below threshold : Time Known 2.8 days is below 8 days requirement (5.2 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 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: 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.
  • 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
143.20.166.14:443
Exit Address
143.20.166.14
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Malaysia Malaysia
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS55720
AS Name
Gigabit Hosting Sdn Bhd (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 4 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Exit
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 4/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 9/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) 12.7 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 (0/9 DA) Median: 2.8d (0/9 DA above threshold)
Min/Max: 2.2d / 2.8d (9/9 DA, Voting / Total Eligible)		 ≥17.9d - 58.6d (varies) (≥5/9 DA)
Uptime Below (0/9 DA) 2.9d (R) ≥3.3d - 3.4d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (4/9 DA) 4/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 (0/9 DA) 0/9 DA assigned Stable ≥17.9d - 58.6d (varies) (≥5/9 DA)
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (9/9 DA) Majority: 100.0% (9/9 DA) ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 2.8d (0/9 DA above threshold)
Min/Max: 2.2d / 2.8d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Below (4/9 DA) 4/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 (0/9 DA) 0/9 DA assigned Stable ≥17.9d - 58.6d (varies) (≥5/9 DA)
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (9/9 DA) Majority: 100.0% (9/9 DA) ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 5.2 more days) Median: 2.8d (0/9 DA above threshold)
Min/Max: 2.2d / 2.8d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 12.7 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-296.0 Mbit/s (≥5/9 DA)
Exit Exit Policy Meets (9/9 DA) Port 80: Yes | Port 443: Yes (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-03-29 11:15:07).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
12.67 Mbit/s
Advertised Bandwidth
12.67 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
2.8 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-29 11:15:07

Measured By
4/6 Bandwidth Authorities
Not measured by: bastet, longclaw
Median Measurement
12.7 Kbit/s
Min / Max
8 bit/s / 12.7 Kbit/s
Deviation
12.7 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (0th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0000% (0th pctl)

Uptime and Stability

Uptime Metrics
Current Status
UP 2d 22h 1m ago
Overall Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (0.0%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
2d 21h 15m ago (2026-03-26 14:00:00)
Last Seen
2h 15m 38s ago (2026-03-29 09:00:00)
Last Restarted
2d 22h 1m ago (2026-03-26 13:14:21)
Last Changed Address
2026-03-26 14:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-03-29 04:00 UTC

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

Software and Version

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

Exit Health & Policy

DNS Health
Status
Not Tested
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 
  20-23
  43
  53
  79-81
  88
  110
  143
  194
  220
  389
  443
  464-465
  531
  543-544
  554
  563
  587
  636
  706
  749
  853
  873
  902-904
  981
  989-995
  1194
  1220
  1293
  1500
  1533
  1677
  1723
  1755
  1863
  2082-2083
  2086-2087
  2095-2096
  2102-2104
  3128
  3389
  3690
  4321
  4643
  5050
  5190
  5222-5223
  5228
  5900
  6660-6669
  6679
  6697
  8000
  8008
  8074
  8080
  8082
  8087-8088
  8232-8233
  8332-8333
  8443
  8888
  9418
  9999-10000
  11371
  19294
  19638
  50002
  64738
IPv6 Exit Policy Summary
None
Full Exit Policy
reject 0.0.0.0/8:*
reject 169.254.0.0/16:*
reject 127.0.0.0/8:*
reject 192.168.0.0/16:*
reject 10.0.0.0/8:*
reject 172.16.0.0/12:*
reject 143.20.166.14:*
accept *:20-21
accept *:22
accept *:23
accept *:43
accept *:53
accept *:79
accept *:80-81
accept *:88
accept *:110
accept *:143
accept *:194
accept *:220
accept *:389
accept *:443
accept *:464
accept *:465
accept *:531
accept *:543-544
accept *:554
accept *:563
accept *:587
accept *:636
accept *:706
accept *:749
accept *:853
accept *:873
accept *:902-904
accept *:981
accept *:989-990
accept *:991
accept *:992
accept *:993
accept *:994
accept *:995
accept *:1194
accept *:1220
accept *:1293
accept *:1500
accept *:1533
accept *:1677
accept *:1723
accept *:1755
accept *:1863
accept *:2082
accept *:2083
accept *:2086-2087
accept *:2095-2096
accept *:2102-2104
accept *:3128
accept *:3389
accept *:3690
accept *:4321
accept *:4643
accept *:5050
accept *:5190
accept *:5222-5223
accept *:5228
accept *:5900
accept *:6660-6669
accept *:6679
accept *:6697
accept *:8000
accept *:8008
accept *:8074
accept *:8080
accept *:8082
accept *:8087-8088
accept *:8232-8233
accept *:8332-8333
accept *:8443
accept *:8888
accept *:9418
accept *:9999
accept *:10000
accept *:11371
accept *:19294
accept *:19638
accept *:50002
accept *:64738
reject *:*

Last fetch was at Sun, 29 Mar 2026 11:15:37 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-03-29 11:15:07).

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 Yes — Y Yes Running, Valid, V2Dir, Exit 12.7 Mbit/s | 816.0 Kbit/s 12.7 Mbit/s | 200.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.8d | 8d 2.8d | 63.4d 2.9d | 3.3d 100.0% | 98.0% 2.8d | 1.0d 2026-03-28 19:16:52 12.7 Kbit/s
dannenberg (DE) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Exit 12.7 Mbit/s | 816.0 Kbit/s 12.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.8d | 8d 2.8d | 17.9d 2.9d | 3.3d 100.0% | 98.0% 2.8d | 1.0d 2026-03-28 19:16:52 12.7 Kbit/s
dizum (NL) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Exit 12.7 Mbit/s | 816.0 Kbit/s 12.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.2d | 8d 2.2d | 42.9d 2.9d | 3.4d 100.0% | 98.0% 2.2d | 1.0d 2026-03-28 19:16:52 12.7 Kbit/s
faravahar (US) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Exit 12.7 Mbit/s | 816.0 Kbit/s 12.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.8d | 8d 2.8d | 56.4d 2.9d | 3.4d 100.0% | 98.0% 2.8d | 1.0d 2026-03-28 19:16:52 12.7 Kbit/s
gabelmoo (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 12.7 Mbit/s | 816.0 Kbit/s 12.7 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.8d | 8d 2.8d | 62.1d 2.9d | 3.4d 100.0% | 98.0% 2.8d | 1.0d 2026-03-28 19:16:52 8 bit/s
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 12.7 Mbit/s | 816.0 Kbit/s 12.7 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.8d | 8d 2.8d | 62.6d 2.9d | 3.3d 100.0% | 98.0% 2.8d | 1.0d 2026-03-28 19:16:52 12.7 Kbit/s
maatuska (SE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 12.7 Mbit/s | 816.0 Kbit/s 12.7 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.8d | 8d 2.8d | 50.7d 2.9d | 3.3d 100.0% | 98.0% 2.8d | 1.0d 2026-03-28 19:16:52 2320 bit/s
moria1 (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 12.7 Mbit/s | 8.4 Mbit/s 12.7 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.4d | 8d 2.8d | 291.4d 2.9d | 4.1d 100.0% | 98.0% 2.4d | 9.9d 2026-03-28 19:16:52 6880 bit/s
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 12.7 Mbit/s | 816.0 Kbit/s 12.7 Mbit/s | 264.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.8d | 8d 2.8d | 58.6d 2.9d | 3.9d 100.0% | 98.0% 2.8d | 1.0d 2026-03-28 19:16:52 8 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.