View Relay "CryptoRebel"

Fingerprint: 60E85A4A09428CE65162C899AA7D908EB5885C98 | Family: 28 relays | +666 13 666 0008 - Crypto Anarchist Manifesto | AS329325 | South Africa | Linux

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
4/6 BW Auths Measured
Stability
Not Overloaded | UP 13h 29m 52s ago
Reachability
IPv4: 9/9 (Directory Auths)
BW Weight
0.00% of Network | 0 Kbit/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: Time Known below threshold : Time Known 0.4 days is below 8 days requirement (7.6 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.
  • HSDir: Time Known below threshold : Time Known 10.6 hours below 25 hours (dir-spec default)
    Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.

Addresses
OR Address
vps25402.maxko-hosting.net
102.211.56.120:9000
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
South Africa South Africa
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS329325
AS Name
Maxko for Gaming Development (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 3 operators)

Current Flags (3): Running, Valid, V2Dir
Eligible Flags (3): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 0/9 | Stable: 0/9 | HSDir: 0/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
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) 0 bit/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: 0.4d (0/9 DA above threshold)
Min/Max: 0.0d / 0.4d (9/9 DA, Voting / Total Eligible)
≥17.9d - 58.6d (varies) (≥5/9 DA)
Uptime Below (0/9 DA) 0.6d (R) ≥3.3d - 3.4d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (0/9 DA) 0/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 (8/9 DA) Majority: 100.0% (8/9 DA)
Min/Med/Max: 0.0% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)
≥98.0% (≥5/9 DA)
Time Known Below (0/9 DA) Median: 0.4d (0/9 DA above threshold)
Min/Max: 0.0d / 0.4d (9/9 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Below (0/9 DA) 0/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 (8/9 DA) Majority: 100.0% (8/9 DA)
Min/Med/Max: 0.0% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 7.6 more days) Median: 0.4d (0/9 DA above threshold)
Min/Max: 0.0d / 0.4d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 0 bit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-296.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-03-29 09:45:08).

Capacity (Relay Reported)
Observed Bandwidth
0.00 Kbit/s
Advertised Bandwidth
Unknown
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
N/A
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-29 09:45:08

Measured By
4/6 Bandwidth Authorities
Not measured by: bastet, moria1
Median Measurement
0 bit/s
Min / Max
0 bit/s / 8 bit/s
Network Participation: Consensus Weight: 0.0000% of network (0th pctl) | Guard: N/A | Middle: 0.0000% (0th pctl) | Exit: N/A

Uptime Metrics
Current Status
UP 13h 29m 52s 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
12h 46m 39s ago (2026-03-28 22:00:00)
Last Seen
2h 46m 39s ago (2026-03-29 08:00:00)
Last Restarted
13h 29m 52s ago (2026-03-28 21:16:47)
Last Changed Address
2026-03-28 22:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator Identity

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

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
+666 13 666 0008 - Crypto Anarchist Manifesto

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 Sun, 29 Mar 2026 10:46:38 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-03-29 09:45:08).

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 No Y Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 200.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.4d | 8d 0.4d | 63.4d 0.6d | 3.3d 100.0% | 98.0% 0.4d | 1.0d 2026-03-28 21:16:53
dannenberg (DE) Yes Yes No N Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.4d | 8d 0.4d | 17.9d 0.6d | 3.3d 100.0% | 98.0% 0.4d | 1.0d 2026-03-28 21:16:53
dizum (NL) Yes Yes No N Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.4d | 8d 0.4d | 42.9d 0.6d | 3.4d 100.0% | 98.0% 0.4d | 1.0d 2026-03-28 21:16:53
faravahar (US) Yes Yes No N Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.4d | 8d 0.4d | 56.4d 0.6d | 3.4d 100.0% | 98.0% 0.4d | 1.0d 2026-03-28 21:16:53
gabelmoo (DE) Yes Yes No Y Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 280.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.4d | 8d 0.4d | 62.1d 0.6d | 3.4d 100.0% | 98.0% 0.4d | 1.0d 2026-03-28 21:16:53 8 bit/s
longclaw (US) Yes Yes No Y Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 232.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.4d | 8d 0.4d | 62.6d 0.6d | 3.3d 100.0% | 98.0% 0.4d | 1.0d 2026-03-28 21:16:53 8 bit/s
maatuska (SE) Yes Yes No Y Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 296.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.4d | 8d 0.4d | 50.7d 0.6d | 3.3d 100.0% | 98.0% 0.4d | 1.0d 2026-03-28 21:16:53 8 bit/s
moria1 (US) Yes Yes No Y Yes Valid, V2Dir 0 bit/s | 8.4 Mbit/s 0 bit/s | 216.0 Mbit/s OR 16.0 Mbit/s 0.0% | 98% 0.0d | 8d 0.0d | 291.4d 0.6d | 4.1d 0.0% | 98.0% 0.0d | 9.9d 2026-03-28 21:16:53
tor26 (AT) Yes Yes No Y Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 264.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.4d | 8d 0.4d | 58.6d 0.6d | 3.9d 100.0% | 98.0% 0.4d | 1.0d 2026-03-28 21:16:53 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.