View Relay "leonardo"

Fingerprint: 88EF3F81A4936A3D5C619F852C70A2A673FA754A | Family: 1 relay | donatello@cocaine.ninja | AS207656 | Ukraine | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Fast, Exit (5)
DNS Health
Not Tested (via exitdnshealth.1aeo.com)
BW Verified
2/7 BW Auths Measured 160 Kbit/s Median
Stability
Not Overloaded | UP 4h 12m 22s ago
Reachability
IPv4: 9/9 | v6: 8/8 (Directory Auths)
First Seen
3h 45m 39s ago
BW Weight
0.00% of Network | 2 Mbit/s Observed By Relay
Version
0.4.9.11 Not 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 : 0/9 authorities credit this relay with enough bandwidth for Guard (5 needed): at least 16.8 Mbit/s (AuthDirGuardBWGuarantee) or a place in their top 25% (80.0 Mbit/s – 280.0 Mbit/s). gabelmoo and tor26 measured this relay at 2.4 Mbit/s – 3.1 Mbit/s. dizum, longclaw and maatuska used the relay-reported 2.1 Mbit/s. bastet, dannenberg and moria1 counted this relay as 0 (no measurement, relay-reported bandwidth ignored).
    Suggestion: Guard requires a bandwidth of at least AuthDirGuardBWGuarantee (16.8 Mbit/s by default) or one in the top 25% of relays, judged by each authority the same way as for Fast. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx.
  • Guard: WFU below threshold : Weighted Fractional Uptime 0.5% is below 98% requirement
    Suggestion: WFU measures recent uptime (recent downtime weighs more heavily). To improve: 1) Minimize restarts, 2) Use systemd with Restart=always, 3) Monitor for OOM kills, 4) Schedule updates during low-traffic periods.
  • 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.
  • Low bandwidth authority measurements : Only 2/7 bandwidth authorities measured this relay. Minimum 3 measurements needed for accurate consensus weight.
    Suggestion: Low measurement count can indicate connectivity issues. Check: 1) Relay is reachable from multiple geographic locations, 2) ORPort accepts connections from bandwidth scanners, 3) RelayBandwidthRate in torrc matches actual capacity. New relays may take 1-2 days to be measured by all authorities.
  • Tor version not recommended : Running Tor version 0.4.9.11 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.

Connectivity and Location

Addresses
OR Address
193.218.118.89:443
[2a0f:e586:f:f:baa4:d491:90be:dca5]:443
Exit Address
193.218.118.89
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
Location
Country
Ukraine Ukraine
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS207656
AS Name
Epinatura LLC (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 4 operators)

Flags and Eligibility

Current Flags (5): Running, Valid, V2Dir, Fast, Exit
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 5/9 | Stable: 1/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
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 Partial (5/9 DA) 2.4 Mbit/s – 3.1 Mbit/s (2 DA measured)
2.1 Mbit/s (3 DA relay-reported)
0 bit/s (3 DA unmeasured, counted as 0)
faravahar: not published		 ≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (0/9 DA) Median: 0.2d (1/9 DA above threshold)
Min/Max: 0.2d / 157.3d (9/9 DA, Voting / Total Eligible)		 ≥6.2d - 8.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10253.2d
Uptime Below (0/9 DA) 0.2d (R) ≥5.8d - 5.8d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (5/9 DA) 5/9 DA assigned Fast
2.4 Mbit/s – 3.1 Mbit/s (2 DA measured)
2.1 Mbit/s (3 DA relay-reported)
0 bit/s (3 DA unmeasured, counted as 0)
faravahar: not published		 ≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (1/9 DA) 1/9 DA assigned Stable ≥6.2d - 8.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10253.2d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Uptime Below (0/9 DA) 0.2d (R) ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA)
[Stricter] moria1: ≥98% WFU and ≥9.9d Time Known
Guard Prereq: Fast Meets (5/9 DA) 5/9 DA assigned Fast
2.4 Mbit/s – 3.1 Mbit/s (2 DA measured)
2.1 Mbit/s (3 DA relay-reported)
0 bit/s (3 DA unmeasured, counted as 0)
faravahar: not published		 ≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (1/9 DA) 1/9 DA assigned Stable ≥6.2d - 8.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10253.2d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 0.4% (0/9 DA above threshold)
Min/Max: 0.3% / 1.4% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 43.5d (9/9 DA above threshold)
Min/Max: 9.7d / 46.9d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 2.4 Mbit/s – 3.1 Mbit/s (2 DA measured)
2.1 Mbit/s (3 DA relay-reported)
0 bit/s (3 DA unmeasured, counted as 0)
faravahar: not published		 ≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-280.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-10-18 17:15:05).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
2.09 Mbit/s
Advertised Bandwidth
2.09 Mbit/s
Rate Limit
50.33 Mbit/s
Burst Limit
58.72 Mbit/s
Total Data
N/A
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-10-18 17:15:05

Measured By
2/7 Bandwidth Authorities
Not measured by: bastet, dannenberg, faravahar, longclaw, moria1
Consensus Weight
160.0 Kbit/s (Unmeasured)
Measured Min / Max
2.4 Mbit/s / 3.1 Mbit/s
Network Participation: Consensus Weight: 0.0000% of network (3th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0000% (1th pctl)

Uptime and Stability

Uptime Metrics
Current Status
UP 4h 12m 22s ago
Overall Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
N/A
Hibernating
No
Timestamps
First Seen
3h 45m 39s ago (2026-10-18 14:00:00)
Last Seen
1h 45m 39s ago (2026-10-18 16:00:00)
Last Restarted
4h 12m 22s ago (2026-10-18 13:33:17)
Last Changed Address
2026-10-18 14:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-10-18 09:00 UTC

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

Software and Version

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

Exit Health & Policy

DNS Health
Status
Not Tested
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 
  20-22
  43
  53
  79-81
  194
  389
  443
  464-465
  531
  543-544
  554
  563
  636
  706
  853
  902-904
  981
  989-991
  994
  1194
  5222-5223
  5228
  6660-6669
  6679
  6697
  9418
  11371
  19294
  64738
IPv6 Exit Policy Summary
accept: 
  20-22
  43
  53
  79-81
  194
  389
  443
  464-465
  531
  543-544
  554
  563
  636
  706
  853
  902-904
  981
  989-991
  994
  1194
  5222-5223
  5228
  6660-6669
  6679
  6697
  9418
  11371
  19294
  64738
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 193.218.118.89:*
accept *:20-21
accept *:22
accept *:43
accept *:53
accept *:79
accept *:80-81
accept *:194
accept *:389
accept *:443
accept *:464
accept *:465
accept *:531
accept *:543-544
accept *:554
accept *:563
accept *:636
accept *:706
accept *:853
accept *:902-904
accept *:981
accept *:989-990
accept *:991
accept *:994
accept *:1194
accept *:5222-5223
accept *:5228
accept *:6660-6669
accept *:6679
accept *:6697
accept *:9418
accept *:11371
accept *:19294
accept *:64738
reject *:*

Last fetch was at Sun, 18 Oct 2026 17:45:38 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-10-18 17:15:05).

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 (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 Yes — Y Yes Yes Running, Valid, V2Dir, Exit 0 bit/s (U) | 816.0 Kbit/s 0 bit/s (U) | 184.0 Mbit/s OR 16.8 Mbit/s 0.5% | 98% 43.5d | 8d 0.2d | 8.9d 0.2d | 5.8d 2026-10-18 13:33:28 2.1 Mbit/s (R)
dannenberg (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 0 bit/s (U) | 816.0 Kbit/s 0 bit/s (U) | 280.0 Mbit/s OR 16.8 Mbit/s 1.3% | 98% 34.1d | 8d 0.4d | 6.2d 0.2d | 6.2d 2026-10-18 13:33:28 2.1 Mbit/s (R)
dizum (NL) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Exit 2.1 Mbit/s (R) | 816.0 Kbit/s 2.1 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 1.0% | 98% 37.0d | 8d 0.3d | 8.8d 0.2d | 5.8d 2026-10-18 13:33:28 2.1 Mbit/s (R)
faravahar (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit not published | 816.0 Kbit/s not published | 264.0 Mbit/s OR 16.8 Mbit/s 0.4% | 98% 44.5d | 8d 0.2d | 9.3d 0.2d | 6.4d 2026-10-18 13:33:28 2.1 Mbit/s (R)
gabelmoo (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 2.4 Mbit/s (M) | 816.0 Kbit/s 2.4 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s 0.3% | 98% 46.9d | 8d 0.2d | 8.9d 0.2d | 6.0d 2026-10-18 13:33:28 2.1 Mbit/s (R)
longclaw (US) Yes Yes Yes — Y Yes — Running, Valid, V2Dir, Fast, Exit 2.1 Mbit/s (R) | 816.0 Kbit/s 2.1 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 0.3% | 98% 44.6d | 8d 0.2d | 9.1d 0.2d | 5.8d 2026-10-18 13:33:28 2.1 Mbit/s (R)
maatuska (SE) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Exit 2.1 Mbit/s (R) | 816.0 Kbit/s 2.1 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 0.4% | 98% 46.2d | 8d 0.2d | 8.8d 0.2d | 5.8d 2026-10-18 13:33:28 2.1 Mbit/s (R)
moria1 (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Stable, Exit 0 bit/s (U) | 8.4 Mbit/s 0 bit/s (U) | 192.0 Mbit/s OR 16.8 Mbit/s 1.4% | 98% 9.7d | 8d 157.3d | 10253.2d 0.2d | 5.8d 2026-10-18 13:33:28 2.1 Mbit/s (R)
tor26 (AT) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 3.1 Mbit/s (M) | 816.0 Kbit/s 3.1 Mbit/s (M) | 264.0 Mbit/s OR 16.8 Mbit/s 0.4% | 98% 42.2d | 8d 0.2d | 9.2d 0.2d | 6.3d 2026-10-18 13:33:28 2.1 Mbit/s (R)

— = not tested/available • 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.