View Relay "KinkyTronicBG"

Fingerprint: 33E99986AF5865EAD039BEFE8C89FE0A7F3943FD | Family: 3 relays | kinkytronic@proton.me | AS211507 | Bulgaria | Linux

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
4/7 BW Auths Measured 104 Mbit/s Median
Stability
Not Overloaded | UP 1mo 1w 6d ago | UP 100% (1M)
Reachability
IPv4: 9/9 | v6: 8/8(Directory Auths)
BW Weight
0.01% of Network | 92 Mbit/s Observed By Relay
Version
0.4.9.12 Not Recommended
Issues Detected:
  • HSDir: requires V2Dir (tunnelled-dir-server) : HSDir requires the relay to support tunnelled directory requests (V2Dir flag). This relay is missing V2Dir — the descriptor likely does not include tunnelled-dir-server, usually because DirCache 0 is set in torrc.
    Suggestion: Remove DirCache 0 from torrc (DirCache is enabled by default in Tor ≥0.3.3). Restart Tor and verify the descriptor includes tunnelled-dir-server. You can check with: grep tunnelled-dir-server /var/lib/tor/cached-descriptors
  • Tor version not recommended : Running Tor version 0.4.9.12 which is not on the recommended list.
    Suggestion: Update to the latest stable Tor version. Outdated versions may have security vulnerabilities and could eventually be rejected by the network. See torproject.org/download for latest releases.

Addresses
OR Address
bg.kinkytronic.foo
45.137.201.113:443
[2a14:c380:90:18::a]:443
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
Location
Country
Bulgaria Bulgaria
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS211507
AS Name
Julian Achter (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.19% consensus weight, 17 operators)

Current Flags (4): Running, Valid, Fast, Stable
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 8/9 | Stable: 9/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
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 Below (0/9 DA) No DirPort, no tunnelled-dir-server (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Partial (8/9 DA) 88.0 Mbit/s – 112.0 Mbit/s (4 DA measured)
80.0 Mbit/s (4 DA relay-reported)
0 bit/s (1 DA unmeasured, counted as 0)
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Meets (9/9 DA) Median: 40.9d (9/9 DA above threshold)
Min/Max: 9.7d / 20733.1d (9/9 DA, Voting / Total Eligible)
≥2.3d - 9.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7858.2d
Uptime Meets (9/9 DA) 43.8d (R) ≥5.0d - 5.1d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (8/9 DA) 8/9 DA assigned Fast
88.0 Mbit/s – 112.0 Mbit/s (4 DA measured)
80.0 Mbit/s (4 DA relay-reported)
0 bit/s (1 DA unmeasured, counted as 0)
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Meets (9/9 DA) 9/9 DA assigned Stable ≥2.3d - 9.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7858.2d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Uptime Partial (8/9 DA) 43.8d (R) ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA)
[Stricter] moria1: ≥98% WFU and ≥9.9d Time Known
Guard Prereq: Fast Meets (8/9 DA) 8/9 DA assigned Fast
88.0 Mbit/s – 112.0 Mbit/s (4 DA measured)
80.0 Mbit/s (4 DA relay-reported)
0 bit/s (1 DA unmeasured, counted as 0)
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Meets (9/9 DA) 9/9 DA assigned Stable ≥2.3d - 9.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7858.2d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Partial (8/9 DA) Median: 100.0% (8/9 DA above threshold)
Min/Max: 0.0% / 100.0% (9/9 DA, Voting / Total Eligible)
≥98%; dizum: ≥97.756% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 53.7d (9/9 DA above threshold)
Min/Max: 8.9d / 103.1d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Partial (8/9 DA) 88.0 Mbit/s – 112.0 Mbit/s (4 DA measured)
80.0 Mbit/s (4 DA relay-reported)
0 bit/s (1 DA unmeasured, counted as 0)
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-272.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-11-04 08:15:15).

Capacity (Relay Reported)
Observed Bandwidth
92.41 Mbit/s
Advertised Bandwidth
92.41 Mbit/s
Rate Limit
1.05 Gbit/s
Burst Limit
1.58 Gbit/s
Total Data
365 TB (1 year)
1mo: 39 TB | 6mo: 185 TB | 1y: 365 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-04 08:15:15

Measured By
4/7 Bandwidth Authorities
Not measured by: faravahar, longclaw, moria1
Consensus Weight
104.0 Mbit/s (median of 4 measurements)
Measured Min / Max
88.0 Mbit/s / 112.0 Mbit/s
Network Participation: Consensus Weight: 0.0066% of network (57th pctl) | Guard: N/A | Middle: 0.0189% (80th pctl) | Exit: N/A
History
Throughput and write/read, last 6 months Throughput and write/read, last year Throughput and write/read, last 30 days
1M 6M 1Y

Uptime Metrics
Current Status
UP 1mo 1w 6d ago
Overall Uptime (1M/6M/1Y/5Y)
100.0%/97.2%/98.5%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
—/—/98.3%/—
Hibernating
No
Timestamps
First Seen
11mo 1w 4h ago (2025-12-02 05:00:00)
Last Seen
1h 15m 43s ago (2026-11-04 08:00:00)
Last Restarted
1mo 1w 6d ago (2026-09-21 13:09:35)
Last Changed Address
2026-04-06 23:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Evaluated 2026-11-04 09:15 UTC. /details snapshot 2026-11-04 08:00:00 UTC (cached 11s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 1h 30m ago).

General Overload (from /details)
Status
No general overload report in available data
File Descriptor Exhaustion (from /bandwidth)
Status
No file-descriptor exhaustion report in available data
Rate Limits (from /bandwidth)
Status
No rate-limit report in available data
Rate Limit
—
Burst Limit
—
Write counter
—
Read counter
—
About these reports and MetricsPort

Allium’s eligibility windows are applied to the reported timestamps: 72 hours for general overload and file-descriptor exhaustion, 24 hours for a rate-limit hit. A report at the cutoff is historical. An older report can remain visible after Onionoo or Allium’s cache still has it. The cutoff does not prove the relay recovered at that moment. Allium caches the bandwidth document for 12 hours by default. The snapshot time is when Onionoo published that document. It is not the relay’s event time, and it is not necessarily the extra-info publication time. Cache age is how old Allium’s copy is.

MetricsPort counters are cumulative. Compare samples, and account for process restarts. A nonzero total alone does not show ongoing activity. Gauges describe current values. An unavailable metric is unknown, not zero. Allium does not have this relay’s MetricsPort readings and does not invent them.

The port below is an example for an endpoint you have already configured. MetricsPort must be enabled with restricted access and must not be exposed publicly. Setup stays in the Tor overload troubleshooting guide.

curl http://127.0.0.1:9035/metrics
History
Uptime, last 6 months Uptime, last year Uptime, last 30 days
1M 6M 1Y

Operator Identity

Source: AROI Validation API — 2026-11-04 00:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
kinkytronic@proton.me
Family Configuration
Family Support
MyFamily Only (3) — Legacy only. Consider migrating to Happy Families. | View Full Family (3)
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Members: 3
32F4A8C1E9B4F04578EFC372E8243E45B80D96AE
33E99986AF5865EAD039BEFE8C89FE0A7F3943FD (this relay)
D5F36470AB954FD252B73F0CEB8AA58CF406DF2D
Alleged Member: 1
(they don't list you back)
5C31B868E0F5854D29D93A18497C2CA92766AB2C (not in the network)
Indirect Members: 0
none

Platform
Linux — Tor 0.4.9.12 on Linux
Version
0.4.9.12 — Not Recommended
Version Status
Obsolete — Update urgently. See torproject.org/download

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 Wed, 04 Nov 2026 09:15:43 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-11-04 08:15:15).

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 (BW|T) Guard BW (BW|Threshold) Guard WFU (M|T) Guard TK (M|T) Stable MTBF (M|T) Stable Uptime (Relay|T) Desc Published Cons Wt (Authority)
bastet (US) Yes Yes No — Y Yes Yes Running, Valid, Fast, Stable 104.0 Mbit/s (M) | 816.0 Kbit/s 104.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 99.9% | 98% 33.1d | 8d 26.2d | 8.4d 43.8d | 5.2d 2026-11-03 23:09:42 104.0 Mbit/s (M)
dannenberg (DE) Yes Yes No — Y Yes Yes Running, Valid, Fast, Stable 88.0 Mbit/s (M) | 816.0 Kbit/s 88.0 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 47.9d | 8d 33.3d | 9.2d 43.8d | 5.2d 2026-11-03 23:09:42 88.0 Mbit/s (M)
dizum (NL) Yes Yes No — N Yes Yes Running, Valid, Fast, Stable 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.5% | 98% 53.7d | 8d 35.9d | 6.6d 43.8d | 5.1d 2026-11-03 23:09:42 80.0 Mbit/s (R)
faravahar (US) Yes Yes No — Y Yes Yes Running, Valid, Fast, Stable 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 66.7d | 8d 40.9d | 6.4d 43.8d | 5.1d 2026-11-03 23:09:42 80.0 Mbit/s (R)
gabelmoo (DE) Yes Yes No — Y Yes Yes Running, Valid, Fast, Stable 112.0 Mbit/s (M) | 816.0 Kbit/s 112.0 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 102.9d | 8d 102.9d | 10.6d 43.8d | 5.1d 2026-11-03 23:09:42 112.0 Mbit/s (M)
longclaw (US) Yes Yes No — Y Yes N/T Running, Valid, Fast, Stable 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 103.1d | 8d 103.1d | 10.7d 43.8d | 5.0d 2026-11-03 23:09:42 80.0 Mbit/s (R)
maatuska (SE) Yes Yes No — N Yes Yes Running, Valid, Fast, Stable 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.7% | 98% 50.6d | 8d 9.7d | 2.3d 43.8d | 5.1d 2026-11-03 23:09:42 80.0 Mbit/s (R)
moria1 (US) Yes Yes No — Y Yes Yes Valid, Stable 0 bit/s (U) | 8.4 Mbit/s 0 bit/s (U) | 192.0 Mbit/s OR 16.8 Mbit/s 0.0% | 98% 8.9d | 8d 20733.1d | 7858.2d 43.8d | 5.2d 2026-11-03 23:09:42 80.0 Mbit/s (R)
tor26 (AT) Yes Yes No — Y Yes Yes Running, Valid, Fast, Stable 104.0 Mbit/s (M) | 816.0 Kbit/s 104.0 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 103.1d | 8d 103.1d | 10.5d 43.8d | 5.1d 2026-11-03 23:09:42 104.0 Mbit/s (M)

N/T = this authority does not test IPv6 • — = not in this vote • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known • Bandwidth source: (M) bandwidth-scanner measurement, (R) relay-reported, (U) unmeasured, counted as 0

Bandwidth Values Explained:
Measured (M) = An authority's bandwidth-scanner measurement of your relay (Measured= in its vote). An authority that has one uses it for the Fast and Guard flags, and the consensus weight is the median of these measurements when 3 or more authorities have one.
Relay-reported (R) = The bandwidth your relay advertises: the lower of its observed bandwidth and its rate limit, capped at 10 MB/s (Bandwidth= in every vote). An authority without a measurement uses it for flags, unless it has measurements for enough other relays (ignoring-advertised-bws=1); then your relay counts as 0 (U). It sets the consensus weight only when fewer than 3 authorities measured the relay, capped at 20 KB/s (maxunmeasuredbw) while 3 or more authorities publish measurements.
Not published = The authority has no measurement of your relay in its vote and ignores relay-reported bandwidth, yet it voted Fast or its vote has no measurements at all: it judges your relay by a measurement kept from an earlier bandwidth file (0 if none), which its vote doesn't show.
Why different? A low measurement means the bandwidth scanners see your relay underperforming compared with other relays that report a similar speed. Votes list both values in kilobytes per second. Rules: Assigning flags in a vote, Computing a consensus.
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.