Tor Relays :: RelayGeek13

View Relay "RelayGeek13"

Fingerprint: `328FEDDF567A363191AED1AC2EB2B6FD66F3BFDD` | Family: 24 relays | tor@relaygeek.com | AS44570 | New Zealand | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, V2Dir, Fast (4)
BW Verified: 5/6 BW Auths Measured 9 Kbit/s Median
Stability: Not Overloaded | UP 13h 26m 56s ago

Reachability: IPv4: 9/9 | v6: 8/8 (Directory Auths)
First Seen: 12h 45m 38s ago
BW Weight: 0.00% of Network | 11 Mbit/s Observed By Relay
Version: 0.4.9.8 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: Time Known below threshold : Time Known 0.5 days is below 8 days requirement (7.5 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: Time Known below threshold : Time Known 12.5 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.

Connectivity and Location

Addresses

OR Address: 185.121.170.52:443
[2a06:9f80:a000::52:1]:443

Reachability (Directory Authorities)

IPv4: 9/9
IPv6: 8/8 (1 don't test)

Location

Country: New Zealand
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS44570
AS Name: Cloudie Networks, LLC. (BGP.tools)
AS Rarity: Legendary (score: 4/5, <0.05% consensus weight, 2 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Fast

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
Running	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	Meets (9/9 DA)	11.3 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: 0.5d (0/9 DA above threshold) Min/Max: 0.5d / 0.5d (9/9 DA, Voting / Total Eligible)	≥19.7d - 51.8d (varies) (≥5/9 DA) [Stricter] moria1: ≥328.3d
Stable	Uptime	Below (0/9 DA)	0.6d (R)	≥6.6d - 6.6d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (8/9 DA)	8/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	≥19.7d - 51.8d (varies) (≥5/9 DA) [Stricter] moria1: ≥328.3d
	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	Below (0/9 DA)	Median: 0.5d (0/9 DA above threshold) Min/Max: 0.5d / 0.5d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.8d
Guard	Prereq: Fast	Meets (8/9 DA)	8/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	≥19.7d - 51.8d (varies) (≥5/9 DA) [Stricter] moria1: ≥328.3d
	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 7.5 more days)	Median: 0.5d (0/9 DA above threshold) Min/Max: 0.5d / 0.5d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Below (0/9 DA)	11.3 Mbit/s (R)	≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-336.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-05-14 22:45:07).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 11.26 Mbit/s
Advertised Bandwidth: 11.26 Mbit/s
Rate Limit: 8.59 Gbit/s
Burst Limit: 8.59 Gbit/s
Total Data: N/A

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-05-14 22:45:07

Measured By: 5/6 Bandwidth Authorities
Not measured by: moria1
Median Measurement: 9.6 Kbit/s
Min / Max: 1280 bit/s / 11.2 Kbit/s
Deviation: 10.0 Kbit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0001% of network (8th pctl) | Guard: N/A | Middle: 0.0003% (9th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics

Current Status: UP 13h 26m 56s 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 45m 38s ago (2026-05-14 10:00:00)
Last Seen: 1h 45m 38s ago (2026-05-14 21:00:00)
Last Restarted: 13h 26m 56s ago (2026-05-14 09:18:42)
Last Changed Address: 2026-05-14 10:00:00

Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-05-14 15:00 UTC

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: tor@relaygeek.com

Family Configuration

Family Support: MyFamily Only (24) — Legacy only. Consider migrating to Happy Families. | View Full Family (24)

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Members: 24

2499F6177C1BDDBDBDD7EFE576199EC2F652F59B
2C9F0876EC20D0D4898F6CC1EFE4A07D4B2BA013
328FEDDF567A363191AED1AC2EB2B6FD66F3BFDD (this relay)
35FAD795094A78664FCD9D44F01B94772911FF47
37B7BEB48E2BAEB0F985DF7C456C91DA49C49977
3A1E0802617A0BC588B617B7C867D37FF4DD8A88
65520CA442774A11AF3267A6F3721A32EDBB37CA
65C843E4644D6AE900FC01F9D401E73FB5E98262
6AD96EDE398A0DA22222B87B18FB1B9352ED289B
866170841FA61C66140027A7C4BDDAC78C70EC7A
87A1F0F9484EA4DDEA551B710B92A5FFC2E70359
95AC8E845B287DE65457E233B0B755435951FDBF
96174A2DDBEBAC256547AE54D4C792E8F9BBFE6C
99026807D13EDC4DA47F6F5C73DAE34C1F84231A
9D7102BB215E4C2F3FDF03BCE123A0C1A1E32B73
BC0C205221978C9F238EC4E939EAC1487AD1C030
C048A2E67775FC03CF942FB4F7F9D86CDE518DE7
C689126C98C348299AE81FC9DA71EB1FC09B0463
CFEF3B1CFB1FAD25A613021F33603CF68B6D4731
D1B18F3BE0A6A3135DB8CAD8D2A805D9F1793EA4
D921E1F73BA8808F3AB87796F708B749A99261BC
DB65ED61E0FC93AB0236D50D761C7B886D37EEA7
F6A497B0A962B7945436A866BD796BEF9E316F2D
FCF4B67D3DAE102967B60D949C00D82C6BC585CA

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

Platform: Linux — Tor 0.4.9.8 on Linux
Version: 0.4.9.8 — 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

Full Exit Policy

reject *:*

Last fetch was at Thu, 14 May 2026 22:45:38 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-05-14 22:45: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	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, Fast	11.3 Mbit/s \| 816.0 Kbit/s	11.3 Mbit/s \| 224.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.5d \| 8d	0.5d \| 51.0d	0.6d \| 6.6d	100.0% \| 98.0%	0.5d \| 1.0d	2026-05-14 09:20:20	9.6 Kbit/s
dannenberg (DE)	Yes	Yes	No	—	N	Yes	Yes	Running, Valid, V2Dir, Fast	11.3 Mbit/s \| 816.0 Kbit/s	11.3 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.5d \| 8d	0.5d \| 49.9d	0.6d \| 6.6d	100.0% \| 98.0%	0.5d \| 1.0d	2026-05-14 09:20:20	11.2 Kbit/s
dizum (NL)	Yes	Yes	No	—	N	Yes	Yes	Running, Valid, V2Dir, Fast	11.3 Mbit/s \| 816.0 Kbit/s	11.3 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.5d \| 8d	0.5d \| 19.7d	0.6d \| 6.6d	100.0% \| 98.0%	0.5d \| 1.0d	2026-05-14 09:20:20	11.2 Kbit/s
faravahar (US)	Yes	Yes	No	—	N	Yes	Yes	Running, Valid, V2Dir, Fast	11.3 Mbit/s \| 816.0 Kbit/s	11.3 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.5d \| 8d	0.5d \| 51.8d	0.6d \| 6.6d	100.0% \| 98.0%	0.5d \| 1.0d	2026-05-14 09:20:20	11.2 Kbit/s
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast	11.3 Mbit/s \| 816.0 Kbit/s	11.3 Mbit/s \| 320.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.5d \| 8d	0.5d \| 52.3d	0.6d \| 6.6d	100.0% \| 98.0%	0.5d \| 1.0d	2026-05-14 09:20:20	1600 bit/s
longclaw (US)	Yes	Yes	No	—	Y	Yes	—	Running, Valid, V2Dir, Fast	11.3 Mbit/s \| 816.0 Kbit/s	11.3 Mbit/s \| 256.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.5d \| 8d	0.5d \| 58.6d	0.6d \| 6.6d	100.0% \| 98.0%	0.5d \| 1.0d	2026-05-14 09:20:20	1920 bit/s
maatuska (SE)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast	11.3 Mbit/s \| 816.0 Kbit/s	11.3 Mbit/s \| 336.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.5d \| 8d	0.5d \| 23.2d	0.6d \| 6.6d	100.0% \| 98.0%	0.5d \| 1.0d	2026-05-14 09:20:20	1280 bit/s
moria1 (US)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir	11.3 Mbit/s \| 8.4 Mbit/s	11.3 Mbit/s \| 232.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.5d \| 8d	0.5d \| 328.3d	0.6d \| 6.6d	100.0% \| 98.0%	0.5d \| 9.8d	2026-05-14 09:20:20	11.2 Kbit/s
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast	11.3 Mbit/s \| 816.0 Kbit/s	11.3 Mbit/s \| 304.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.5d \| 8d	0.5d \| 55.0d	0.6d \| 6.7d	100.0% \| 98.0%	0.5d \| 1.0d	2026-05-14 09:20:20	1760 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.