View Relay "yomi"

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

Consensus
In Consensus (9/9 Directory Auths)
DNS Health
Healthy (16.8s, 71st percentile) (via exitdnshealth.1aeo.com)
BW Verified
5/6 BW Auths Measured 77 Kbit/s Median
Stability
Not Overloaded | UP 1w 3d 6h ago | UP 99% (1M)
Reachability
IPv4: 9/9 | v6: 8/8 (Directory Auths)
BW Weight
0.01% of Network | 78 Mbit/s Observed By Relay
Version
0.4.9.5 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: WFU below threshold : Weighted Fractional Uptime 97.8% 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.
  • HSDir: WFU below threshold : WFU 97.8% below 98% required for HSDir
    Suggestion: HSDir requires ≥98% WFU, Stable flag, and Time Known ≥25 hours (or ~10 days for moria1). Improve uptime consistency.
  • 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.

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
Emerging (score: 1/5, 2.14% consensus weight, 74 operators)

Current Flags (5): Running, Valid, V2Dir, Fast, Exit
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 2/9 | HSDir: 1/9 | Guard: 2/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) 78.1 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 (1/9 DA) Median: 3.3d (1/9 DA above threshold)
Min/Max: 1.6d / 15415.7d (9/9 DA, Voting / Total Eligible)
≥11.3d - 55.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥347.6d
Uptime Below (0/9 DA) 10.3d (R) ≥12.0d - 14.4d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/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 (2/9 DA) 2/9 DA assigned Stable ≥11.3d - 55.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥347.6d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (8/9 DA) Median: 98.8% (8/9 DA above threshold)
Min/Max: 97.8% / 99.3% (9/9 DA, Voting / Total Eligible)
≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 13.2d (9/9 DA above threshold)
Min/Max: 9.7d / 14.8d (9/9 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Meets (9/9 DA) 9/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 (2/9 DA) 2/9 DA assigned Stable ≥11.3d - 55.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥347.6d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (8/9 DA) Median: 98.8% (8/9 DA above threshold)
Min/Max: 97.8% / 99.3% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 13.2d (9/9 DA above threshold)
Min/Max: 9.7d / 14.8d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 78.1 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-296.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-03-15 14:45:07).

Capacity (Relay Reported)
Observed Bandwidth
78.06 Mbit/s
Advertised Bandwidth
67.11 Mbit/s
Rate Limit
67.11 Mbit/s
Burst Limit
134.22 Mbit/s
Total Data
851 TB (5 years)
1mo: 4.8 TB | 6mo: 55 TB | 1y: 97 TB | 5y: 851 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-15 14:45:07

Measured By
5/6 Bandwidth Authorities
Not measured by: longclaw
Median Measurement
77.6 Kbit/s
Min / Max
67.1 Kbit/s / 128.0 Kbit/s
Deviation
60.9 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0066% of network (55th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0197% (37th pctl)

Uptime Metrics
Current Status
UP 1w 3d 6h ago
Overall Uptime (1M/6M/1Y/5Y)
99.0%/99.7%/98.0%/94.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (99.0%/99.7%/98.0%/94.0%)
Hibernating
No
Timestamps
First Seen
7y 3w 6d ago (2019-02-18 00:00:00)
Last Seen
2h 16m 23s ago (2026-03-15 13:00:00)
Last Restarted
1w 3d 6h ago (2026-03-05 08:58:49)
Last Changed Address
2024-01-29 19:00:00
Overload Status: Not Overloaded — No overload conditions reported.

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

DNS Health
Status
Healthy (avg. 16.8s, 71st percentile)
Query Domain
26aa72871bb74701b08daf037c57c4ec.892a827b.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
4/4 instances succeeded
First Hop
bauruine (NO) ECB3B4B74E91B0BC446215EB264479BDAE53E48C
Exit Address Used
104.244.74.97
Per-Instance Results
Cross Validation Attempt 1: Success, 15.8s (cv1_w2)
Cross Validation Attempt 2: Success, 16.5s (cv2_w2)
Cross Validation Attempt 3: Success, 17.2s (cv3_w2)
Cross Validation Attempt 4: Success, 17.8s (cv4_w2)
Tested: 2026-03-15 07:12:39 UTC
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 Sun, 15 Mar 2026 15:16:21 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-03-15 14:45:07).

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 Yes Y Yes Yes Running, Valid, V2Dir, Fast, Exit 78.1 Mbit/s | 816.0 Kbit/s 78.1 Mbit/s | 208.0 Mbit/s OR 16.0 Mbit/s 97.8% | 98% 13.0d | 8d 1.6d | 59.7d 10.3d | 13.6d 97.8% | 98.0% 13.0d | 1.0d 2026-03-14 14:10:14 80.0 Kbit/s
dannenberg (DE) Yes Yes Yes N Yes Yes Running, Valid, V2Dir, Fast, Exit 78.1 Mbit/s | 816.0 Kbit/s 78.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 98.4% | 98% 13.0d | 8d 1.9d | 11.3d 10.3d | 14.3d 98.4% | 98.0% 13.0d | 1.0d 2026-03-14 14:10:14 67.1 Kbit/s
dizum (NL) Yes Yes Yes N Yes Yes Running, Valid, V2Dir, Fast, Exit 78.1 Mbit/s | 816.0 Kbit/s 78.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.1% | 98% 13.6d | 8d 3.4d | 45.8d 10.3d | 12.0d 99.1% | 98.0% 13.6d | 1.0d 2026-03-14 14:10:14 67.1 Kbit/s
faravahar (US) Yes Yes Yes N Yes Yes Running, Valid, V2Dir, Fast, Exit 78.1 Mbit/s | 816.0 Kbit/s 78.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 98.5% | 98% 13.6d | 8d 1.7d | 55.1d 10.3d | 14.5d 98.5% | 98.0% 13.6d | 1.0d 2026-03-14 14:10:14 67.1 Kbit/s
gabelmoo (DE) Yes Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast, Exit 78.1 Mbit/s | 816.0 Kbit/s 78.1 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 98.8% | 98% 14.1d | 8d 2.5d | 61.4d 10.3d | 14.4d 98.8% | 98.0% 14.1d | 1.0d 2026-03-14 14:10:14 120.0 Kbit/s
longclaw (US) Yes Yes Yes Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 78.1 Mbit/s | 816.0 Kbit/s 78.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.2% | 98% 13.2d | 8d 5.6d | 62.0d 10.3d | 14.5d 99.2% | 98.0% 13.2d | 1.0d 2026-03-14 14:10:14 67.1 Kbit/s
maatuska (SE) Yes Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast, Exit 78.1 Mbit/s | 816.0 Kbit/s 78.1 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 99.1% | 98% 13.2d | 8d 3.3d | 40.2d 10.3d | 14.3d 99.1% | 98.0% 13.2d | 1.0d 2026-03-14 14:10:14 128.0 Kbit/s
moria1 (US) Yes Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast, Stable, Guard, Exit 78.1 Mbit/s | 8.4 Mbit/s 78.1 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 98.8% | 98% 9.7d | 8d 15415.7d | 347.6d 10.3d | 15.5d 98.8% | 98.0% 9.7d | 9.8d 2026-03-14 14:10:14 77.6 Kbit/s
tor26 (AT) Yes Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast, Exit 78.1 Mbit/s | 816.0 Kbit/s 78.1 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 99.3% | 98% 14.8d | 8d 4.2d | 55.7d 10.3d | 14.5d 99.3% | 98.0% 14.8d | 1.0d 2026-03-14 14:10:14 104.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). 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.