Tor Relays :: KinkyTronicNL

View Relay "KinkyTronicNL"

Family: 4 relays | kinkytronic@proton.me | AS211507 | Netherlands | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Fast, Running, Valid (3)
BW Verified: 5/6 BW Auths Measured 160 Kbit/s Median
Stability: Not Overloaded | UP 1mo 4w 7h ago | UP 88% (1M)

Reachability: IPv4: 9/9 | v6: 7/7 (Directory Auths)
First Seen: 1mo 4w 11h ago
BW Weight: 0.02% of Network | 155 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: nl.kinkytronic.foo
185.132.53.156:443
[2a14:c380:50:3b::a]:443

Reachability (Directory Authorities)

IPv4: 9/9
IPv6: 7/7 (2 don't test)

Location

Country: Netherlands
Interactive Map: View on Interactive Map

Autonomous System

AS Number: AS211507
AS Name: Julian Achter (BGP.tools)

Flags and Eligibility

Current Flags (3): Running, Valid, Fast

Eligibility Flag Vote Details

Flag	Metric	Status	Relay Value	Threshold Required
Fast	Speed	Meets (≥100 KB/s)	155.8 Mbit/s (R)	≥800.0 Kbit/s (guarantee) OR top 7/8 [Stricter] moria1: ≥8.4 Mbit/s
Stable	MTBF	Below	Median: 1.2d (1/9 DA above threshold) Min/Max: 0.1d / 18667.3d (9/9 DA, Voting / Total Eligible)	≥22.0d - 54.1d (varies) [Stricter] moria1: ≥405.3d
Stable	Uptime	Meets	58.3d (R)	≥9.3d - 10.0d (varies)
HSDir	Prereq: Stable	Below	3/9 authorities assigned Stable flag	≥5/9 authorities
	Prereq: Fast	Meets	9/9 authorities assigned Fast flag	≥5/9 authorities
	WFU	Meets	Median: 99.0% (7/9 DA above threshold) Min/Max: 25.2% / 99.7% (9/9 DA, Voting / Total Eligible)	≥98.0%
	Time Known	Meets	Median: 15.6d (9/9 DA above threshold) Min/Max: 9.7d / 16.6d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) [Stricter] moria1: ≥9.9d
Guard	Prereq: Fast	Meets	9/9 authorities assigned Fast flag	≥5/9 authorities
	Prereq: Stable	Below	3/9 authorities assigned Stable flag	≥5/9 authorities
	Prereq: V2Dir	Below	0/9 authorities assigned V2Dir flag	≥5/9 authorities
	WFU	Meets	Median: 99.0% (7/9 DA above threshold) Min/Max: 25.2% / 99.7% (9/9 DA, Voting / Total Eligible)	≥98% (all authorities)
	Time Known	Meets	Median: 15.6d (9/9 DA above threshold) Min/Max: 9.7d / 16.6d (9/9 DA, Voting / Total Eligible)	≥8 days (all authorities)
	Bandwidth	Meets (≥2 MB/s)	155.8 Mbit/s (R)	≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-01-29 16:15:07).

Last fetch was at Thu, 29 Jan 2026 16:15:44 GMT.

Nickname

KinkyTronicNL

Fingerprint

32F4A8C1E9B4F04578EFC372E8243E45B80D96AE

AROI (?)

none

Contact

kinkytronic@proton.me

IPv4 Exit Policy Summary

reject: 
  1-65535

IPv6 Exit Policy Summary

none

Exit Policy

reject *:*

Effective Family Members: 4 (View)

32F4A8C1E9B4F04578EFC372E8243E45B80D96AE
33E99986AF5865EAD039BEFE8C89FE0A7F3943FD
5C31B868E0F5854D29D93A18497C2CA92766AB2C
D5F36470AB954FD252B73F0CEB8AA58CF406DF2D

Alleged Family Member: 1

1FCB2F23382BFF9579A3AC563098064A4F7EE4F0

Indirect Family Members: 0

none

Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit): 155.79 Mbit/s | 155.79 Mbit/s| 1.05 Gbit/s| 1.58 Gbit/s Measured
Network Participation (Consensus Weight | Guard | Middle | Exit): 0.02% | N/A | 0.05% | N/A
OR Address: nl.kinkytronic.foo | 185.132.53.156:443, [2a14:c380:50:3b::a]:443
Exit Address: none
Dir Address: none
Country: Netherlands
Interactive Map: View on Interactive Map
Autonomous System (AS Number | AS Name): AS211507 | Julian Achter (BGP.tools)
Flags: 3: Fast Running Valid
Flag Uptime (1M/6M/1Y/5Y): —/92.5%/—/—
Uptime (1M/6M/1Y/5Y): 88.6%/93.4%/0.0%/0.0%
Uptime / Downtime: UP 1mo 4w 7h ago
Seen (First | Last): 1mo 4w 11h ago (2025-12-02 05:00:00) | 1h 17m ago (2026-01-29 15:00:00)
Last Restarted: 1mo 4w 7h ago (2025-12-02 09:05:57)
Last Changed Address or Port: 2025-12-02 05: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-29 16:15:07).

Consensus Status (need ≥5/9): In Consensus — 9/9 authorities voted.
Flag Eligibility (need ≥5/9 for flag): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 3/9 | HSDir: 0/9 | Guard: 0/9
Reachability: IPv4: 9/9 | IPv6: 7/7 (2 don't test)
Consensus Weight (Dir. Auth.): Median: 160.0 Kbit/s | Min: 80.0 Kbit/s | Max: 352.0 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.)	160.0 Kbit/s (median)	N/A (no threshold, used for path selection)	—
Guard WFU (Dir. Auth., guard-wfu)	99.0%	≥98% (all authorities)	MEETS
Guard TK (Dir. Auth., tk)	15.6 days	≥8 days (all authorities)	MEETS
Guard BW (Relay Reported)	155.8 Mbit/s	≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s	MEETS - ≥2 MB/s guarantee
Stable Uptime (Relay Reported)	58.3d	≥9.3d - 10.0d (typical)	MEETS - all authorities
Stable MTBF (Dir. Auth., mtbf)	1 days	≥22.0d - 54.1d (typical) [Stricter] moria1: ≥405.3d	BELOW - 1/9
Fast Speed (Relay Reported)	155.8 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.0%	≥98.0% (from all auths)	BELOW - 0/9
HSDir TK (Dir. Auth., tk)	15.6 days	≥1.0d (8/9 auths) [Stricter] moria1: ≥9.9d	BELOW - 0/9
IPv6 Reachable (Dir. Auth.)	7/7 tested	≥4/7 (majority)	REACHABLE

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	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	Y	Yes	Yes	Running, Valid, Fast	155.8 Mbit/s \| 816.0 Kbit/s	155.8 Mbit/s \| 232.0 Mbit/s OR 16.0 Mbit/s	99.0% \| 98%	14.9d \| 8d	1.1d \| 49.8d	58.3d \| 10.2d	99.0% \| 98.0%	14.9d \| 1.0d	2026-01-29 10:06:11	176.0 Kbit/s
dannenberg (DE)	Yes	Yes	N	Yes	Yes	Running, Valid, Fast	155.8 Mbit/s \| 816.0 Kbit/s	155.8 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	99.2% \| 98%	15.6d \| 8d	1.2d \| 22.0d	58.3d \| 10.0d	99.2% \| 98.0%	15.6d \| 1.0d	2026-01-29 10:06:11	80.0 Kbit/s
dizum (NL)	Yes	Yes	N	Yes	—	Running, Valid, Fast, Stable	155.8 Mbit/s \| 816.0 Kbit/s	155.8 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	86.0% \| 98%	15.9d \| 8d	8.5d \| 34.7d	58.3d \| 10.0d	86.0% \| 98.0%	15.9d \| 1.0d	2026-01-29 10:06:11	80.0 Kbit/s
faravahar (US)	Yes	Yes	N	Yes	Yes	Running, Valid, Fast	155.8 Mbit/s \| 816.0 Kbit/s	155.8 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	99.7% \| 98%	15.9d \| 8d	4.3d \| 47.2d	58.3d \| 9.3d	99.7% \| 98.0%	15.9d \| 1.0d	2026-01-29 10:06:11	80.0 Kbit/s
gabelmoo (DE)	Yes	Yes	Y	Yes	Yes	Running, Valid, Fast	155.8 Mbit/s \| 816.0 Kbit/s	155.8 Mbit/s \| 304.0 Mbit/s OR 16.0 Mbit/s	98.4% \| 98%	15.4d \| 8d	1.2d \| 54.1d	58.3d \| 10.0d	98.4% \| 98.0%	15.4d \| 1.0d	2026-01-29 10:06:11	312.0 Kbit/s
longclaw (US)	Yes	Yes	Y	Yes	—	Running, Valid, Fast, Stable	155.8 Mbit/s \| 816.0 Kbit/s	155.8 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	99.7% \| 98%	16.6d \| 8d	10.9d \| 54.7d	58.3d \| 9.6d	99.7% \| 98.0%	16.6d \| 1.0d	2026-01-29 10:06:11	80.0 Kbit/s
maatuska (SE)	Yes	Yes	Y	Yes	Yes	Running, Valid, Fast	155.8 Mbit/s \| 816.0 Kbit/s	155.8 Mbit/s \| 312.0 Mbit/s OR 16.0 Mbit/s	25.2% \| 98%	11.3d \| 8d	0.1d \| 54.9d	58.3d \| 9.5d	25.2% \| 98.0%	11.3d \| 1.0d	2026-01-29 10:06:11	272.0 Kbit/s
moria1 (US)	Yes	Yes	Y	Yes	Yes	Running, Valid, Fast, Stable	155.8 Mbit/s \| 8.4 Mbit/s	155.8 Mbit/s \| 240.0 Mbit/s OR 16.0 Mbit/s	98.6% \| 98%	9.7d \| 8d	18667.3d \| 405.3d	58.3d \| 9.9d	98.6% \| 98.0%	9.7d \| 9.9d	2026-01-29 10:06:11	160.0 Kbit/s
tor26 (AT)	Yes	Yes	Y	Yes	Yes	Running, Valid, Fast	155.8 Mbit/s \| 816.0 Kbit/s	155.8 Mbit/s \| 288.0 Mbit/s OR 16.0 Mbit/s	99.2% \| 98%	15.8d \| 8d	1.2d \| 55.9d	58.3d \| 10.8d	99.2% \| 98.0%	15.8d \| 1.0d	2026-01-29 10:06:11	352.0 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.