View Relay "yomi"

Fingerprint: 892A827BF67DB270E303677A33FE577069DDE558 | Operator: katawaredoki.net v3 (4 relays) ✓ Validated | Family: 4 relays | url:katawaredoki.net... | AS53667 | Luxembourg | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Fast, Stable, HSDir, Exit (7)
DNS Health
Healthy (16.3s, 69th percentile) (via exitdnshealth.1aeo.com)
BW Verified
5/7 BW Auths Measured 49 Mbit/s Median
Stability
Not Overloaded | UP 6d 2h 5m ago | UP 85% (1M)
Reachability
IPv4: 9/9 | v6: 8/8(Directory Auths)
First Seen
8y 8mo 1w ago
BW Weight
0.00% of Network | 76 Mbit/s Observed By Relay
Version
0.4.9.15 Recommended
Issues Detected:
  • Guard: WFU below threshold : 0/9 authorities meet guard-wfu (≥98%; dizum: ≥97.84099999999999%; 5 needed). bastet, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 measured 87.8%–90.9%.
    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.
  • 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
tor-exit.yomi.katawaredoki.net
104.244.74.97:443
[2605:6400:30:f8b5:620c:dc25:c624:aafd]:443
Exit Address
104.244.74.97
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
Location
Country
Luxembourg Luxembourg
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS53667
AS Name
FranTech Solutions (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.40% consensus weight, 30 operators)

Flags and Eligibility

Current Flags (7): Running, Valid, V2Dir, Fast, Stable, HSDir, Exit
Eligible Flags (7): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 8/9 | HSDir: 7/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 Meets (9/9 DA) 38.4 Mbit/s – 73.6 Mbit/s (5 DA measured)
33.6 Mbit/s (4 DA relay-reported)		 ≥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: 7.5d (1/9 DA above threshold)
Min/Max: 1.6d / 6553.5d (9/9 DA, Voting / Total Eligible)		 ≥2.4d - 9.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7607.5d
Uptime Meets (9/9 DA) 6.1d (R) ≥5.2d - 5.3d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
38.4 Mbit/s – 73.6 Mbit/s (5 DA measured)
33.6 Mbit/s (4 DA relay-reported)		 ≥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 (8/9 DA) 8/9 DA assigned Stable ≥2.4d - 9.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7607.5d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Uptime Partial (8/9 DA) 6.1d (R) ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA)
[Stricter] moria1: ≥98% WFU and ≥9.8d Time Known
Guard Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
38.4 Mbit/s – 73.6 Mbit/s (5 DA measured)
33.6 Mbit/s (4 DA relay-reported)		 ≥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 (8/9 DA) 8/9 DA assigned Stable ≥2.4d - 9.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7607.5d
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: 90.5% (0/9 DA above threshold)
Min/Max: 87.8% / 90.9% (9/9 DA, Voting / Total Eligible)		 ≥98%; dizum: ≥97.84099999999999% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 14.6d (9/9 DA above threshold)
Min/Max: 9.7d / 15.2d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 38.4 Mbit/s – 73.6 Mbit/s (5 DA measured)
33.6 Mbit/s (4 DA relay-reported)		 ≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-272.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-11-04 12:45:10).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
76.88 Mbit/s
Advertised Bandwidth
33.55 Mbit/s
Rate Limit
33.55 Mbit/s
Burst Limit
134.22 Mbit/s
Total Data
728 TB (5 years)
1mo: 7.4 TB | 6mo: 70 TB | 1y: 126 TB | 5y: 728 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-04 12:45:10

Measured By
5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Consensus Weight
49.6 Mbit/s (median of 5 measurements)
Measured Min / Max
38.4 Mbit/s / 73.6 Mbit/s
Deviation
35.2 Mbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0031% of network (38th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0102% (15th pctl)
History
Throughput and write/read, last 6 months Throughput and write/read, last year Throughput and write/read, last 5 years Throughput and write/read, last 30 days
1M 6M 1Y 5Y

Uptime and Stability

Uptime Metrics
Current Status
UP 6d 2h 5m ago
Overall Uptime (1M/6M/1Y/5Y)
85.2%/96.7%/98.2%/93.7%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (85.2%/96.7%/98.2%/93.7%)
Hibernating
No
Timestamps
First Seen
8y 8mo 1w ago (2018-03-01 23:00:00)
Last Seen
2h 45m 39s ago (2026-11-04 11:00:00)
Last Restarted
6d 2h 5m ago (2026-10-29 11:40:18)
Last Changed Address
2026-04-06 23:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Evaluated 2026-11-04 13:45 UTC. /details snapshot 2026-11-04 11:00:00 UTC (cached 42s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 6h 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 5 years Uptime, last 30 days
1M 6M 1Y 5Y

Operator and Family

Operator Identity

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

AROI Domain (?)
katawaredoki.net
Operator Validation
Validated (4/4 relays)
This Relay
Validated (dns-familyid-ed25519)
Contact
url:katawaredoki.net proof:dns-familyid-ed25519 ciissversion:3 btc:bc1qkclqn6kelhkyryllhzdax46j2xs75khjmr39va xmr:89YVk9wBcre1wLt641VWA1SgUxN6XczVR8iNcYxNgTdNc88jyfVmkeXaX3vdhMod57WkUGVsh3PFGaqoteLpmoV5DYJD2Dv
Family Configuration
Family Support
Happy Families (4) — Has family-cert in server descriptor (guide) | View Full Family (4)
MyFamily (legacy declarations) — none

Software and Version

Platform
Linux — Tor 0.4.9.15 on Linux
Version
0.4.9.15 — Recommended
Version Status
Recommended

Exit Health & Policy

DNS Health
Status
Healthy (avg. 16.3s, 69th percentile)
Query Domain
e2f6c38ed28c41b09c251c16d1785106.892a827b.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Upstream Resolver
Local /24 (exit's own network)
Local /24 100% (~86 estimated queries)
Cross-Validation
3/3 instances succeeded
First Hop
iedittedtheconfig (FI) 56B75ED7BE25B6C3C761A69315E442C72459EA42
Exit Address Used
104.244.74.97
Per-Instance Results
Cross Validation Attempt 1: Success, 17.9s (cv1_w2)
Cross Validation Attempt 2: Success, 11.3s (cv2_w2)
Cross Validation Attempt 3: Success, 19.8s (cv3_w2)
Tested: 2026-11-03 20:10:02 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 
  43
  53
  80
  443
  554
  1080
  1194
  1293
  1723
  1935-1936
  3690
  4321
  5222-5223
  8080
  8233
  8333
  8443
  9333
  9418
  11371
  18080-18081
  18083
  18089
  50001-50002
IPv6 Exit Policy Summary
accept: 
  43
  53
  80
  443
  554
  1080
  1194
  1293
  1723
  1935-1936
  3690
  4321
  5222-5223
  8080
  8233
  8333
  8443
  9333
  9418
  11371
  18080-18081
  18083
  18089
  50001-50002
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 104.244.74.97:*
accept *:43
accept *:53
accept *:80
accept *:443
accept *:554
accept *:1080
accept *:1194
accept *:1293
accept *:1723
accept *:1935
accept *:1936
accept *:3690
accept *:4321
accept *:5222
accept *:5223
accept *:8080
accept *:8443
accept *:9418
accept *:11371
accept *:8233
accept *:8333
accept *:9333
accept *:18080
accept *:18081
accept *:18083
accept *:18089
accept *:50001
accept *:50002
reject *:*

Last fetch was at Wed, 04 Nov 2026 13:45:39 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-11-04 12:45:10).

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, Fast, Stable, HSDir, Exit 38.4 Mbit/s (M) | 816.0 Kbit/s 38.4 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 90.5% | 98% 14.7d | 8d 7.7d | 8.4d 6.1d | 5.2d 2026-11-03 17:40:35 38.4 Mbit/s (M)
dannenberg (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 49.6 Mbit/s (M) | 816.0 Kbit/s 49.6 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s 90.9% | 98% 15.2d | 8d 7.1d | 9.3d 6.1d | 5.3d 2026-11-04 11:40:36 49.6 Mbit/s (M)
dizum (NL) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 33.6 Mbit/s (R) | 816.0 Kbit/s 33.6 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 88.4% | 98% 13.4d | 8d 6.2d | 6.7d 6.1d | 5.3d 2026-11-04 11:40:36 33.6 Mbit/s (R)
faravahar (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 33.6 Mbit/s (R) | 816.0 Kbit/s 33.6 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 89.1% | 98% 12.9d | 8d 5.0d | 6.5d 6.1d | 5.3d 2026-11-04 11:40:36 33.6 Mbit/s (R)
gabelmoo (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 73.6 Mbit/s (M) | 816.0 Kbit/s 73.6 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 90.9% | 98% 14.6d | 8d 7.5d | 10.8d 6.1d | 5.3d 2026-11-04 11:40:36 73.6 Mbit/s (M)
longclaw (US) Yes Yes Yes — Y Yes N/T Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 33.6 Mbit/s (R) | 816.0 Kbit/s 33.6 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 90.5% | 98% 14.7d | 8d 7.7d | 10.9d 6.1d | 5.3d 2026-11-03 17:40:35 33.6 Mbit/s (R)
maatuska (SE) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Exit 33.6 Mbit/s (R) | 816.0 Kbit/s 33.6 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 87.8% | 98% 11.7d | 8d 1.6d | 2.4d 6.1d | 5.3d 2026-11-04 11:40:36 33.6 Mbit/s (R)
moria1 (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, Exit 45.6 Mbit/s (M) | 8.4 Mbit/s 45.6 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 88.7% | 98% 9.7d | 8d 6553.5d | 7607.5d 6.1d | 5.3d 2026-11-04 11:40:36 45.6 Mbit/s (M)
tor26 (AT) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 68.0 Mbit/s (M) | 816.0 Kbit/s 68.0 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s 90.5% | 98% 14.7d | 8d 7.8d | 10.6d 6.1d | 5.3d 2026-11-04 11:40:36 68.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.