View Relay "flachmon"

Fingerprint: 8E5B1326F580D02E539FDAABF99A3BDE1077252E | Family: 11 relays | 0xFFFFFFFF <tormaster AT kkb-clan dot de> | AS15943 | Germany | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Fast (4)
BW Verified
5/6 BW Auths Measured 168 Kbit/s Median
Stability
Not Overloaded | UP 9h 44m 12s ago | UP 97% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
3y 10mo 3w ago
BW Weight
0.02% of Network | 147 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 92.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 92.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.

Connectivity and Location

Addresses
OR Address
134.101.172.168.dynamic-pppoe.dt.ipv4.wtnet.de
134.101.172.168:9001
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS15943
AS Name
wilhelm.tel GmbH (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 7 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Fast
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 1/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
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) 148.0 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: 0.9d (1/9 DA above threshold)
Min/Max: 0.9d / 18551.2d (9/9 DA, Voting / Total Eligible)		 ≥11.3d - 55.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥347.6d
Uptime Below (0/9 DA) 0.4d (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 (1/9 DA) 1/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 Below (0/9 DA) Median: 92.8% (0/9 DA above threshold)
Min/Max: 92.5% / 93.3% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 10.1d (9/9 DA above threshold)
Min/Max: 9.6d / 10.5d (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 (1/9 DA) 1/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 Below (0/9 DA) Median: 92.8% (0/9 DA above threshold)
Min/Max: 92.5% / 93.3% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 10.1d (9/9 DA above threshold)
Min/Max: 9.6d / 10.5d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 148.0 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 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-03-15 16:15:07).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
147.96 Mbit/s
Advertised Bandwidth
147.96 Mbit/s
Rate Limit
209.72 Mbit/s
Burst Limit
262.14 Mbit/s
Total Data
1.8 PB (5 years)
1mo: 23 TB | 6mo: 62 TB | 1y: 190 TB | 5y: 1.8 PB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-15 16:15:07

Measured By
5/6 Bandwidth Authorities
Not measured by: longclaw
Median Measurement
168.0 Kbit/s
Min / Max
80.0 Kbit/s / 480.0 Kbit/s
Deviation
400.0 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0172% of network (77th pctl) | Guard: N/A | Middle: 0.0516% (96th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 9h 44m 12s ago
Overall Uptime (1M/6M/1Y/5Y)
97.8%/70.0%/75.6%/85.5%
Flag Uptime (1M/6M/1Y/5Y)
—/69.8%/75.2%/85.3%
Hibernating
No
Timestamps
First Seen
3y 10mo 3w ago (2022-04-23 00:00:00)
Last Seen
1h 45m 55s ago (2026-03-15 15:00:00)
Last Restarted
9h 44m 12s ago (2026-03-15 07:01:43)
Last Changed Address
2026-03-15 12:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-03-15 09:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
0xFFFFFFFF <tormaster AT kkb-clan dot de>
Family Configuration
Family Support
MyFamily Only (11) — Legacy only. Consider migrating to Happy Families. | View Full Family (11)
Happy Families (family-cert)
Effective Members: 0
none

Software and Version

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

Exit Health & Policy

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 Sun, 15 Mar 2026 16:45:53 GMT.

Consensus Evaluation

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

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 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 No — Y Yes Running, Valid, V2Dir, Fast 148.0 Mbit/s | 816.0 Kbit/s 148.0 Mbit/s | 208.0 Mbit/s OR 16.0 Mbit/s 92.8% | 98% 10.1d | 8d 0.9d | 59.7d 0.4d | 13.6d 92.8% | 98.0% 10.1d | 1.0d 2026-03-15 01:14:43 168.0 Kbit/s
dannenberg (DE) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 148.0 Mbit/s | 816.0 Kbit/s 148.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 92.9% | 98% 10.0d | 8d 0.9d | 11.3d 0.4d | 14.3d 92.9% | 98.0% 10.0d | 1.0d 2026-03-15 01:14:43 80.0 Kbit/s
dizum (NL) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 148.0 Mbit/s | 816.0 Kbit/s 148.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 93.1% | 98% 10.1d | 8d 0.9d | 45.8d 0.4d | 12.0d 93.1% | 98.0% 10.1d | 1.0d 2026-03-15 01:14:43 80.0 Kbit/s
faravahar (US) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 148.0 Mbit/s | 816.0 Kbit/s 148.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 92.6% | 98% 10.5d | 8d 0.9d | 55.1d 0.4d | 14.5d 92.6% | 98.0% 10.5d | 1.0d 2026-03-15 01:14:43 80.0 Kbit/s
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 148.0 Mbit/s | 816.0 Kbit/s 148.0 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 92.5% | 98% 10.1d | 8d 0.9d | 61.4d 0.4d | 14.4d 92.5% | 98.0% 10.1d | 1.0d 2026-03-15 01:14:43 480.0 Kbit/s
longclaw (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 148.0 Mbit/s | 816.0 Kbit/s 148.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 93.3% | 98% 9.6d | 8d 0.9d | 62.0d 0.4d | 14.5d 93.3% | 98.0% 9.6d | 1.0d 2026-03-15 01:14:43 80.0 Kbit/s
maatuska (SE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 148.0 Mbit/s | 816.0 Kbit/s 148.0 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 93.3% | 98% 10.1d | 8d 1.0d | 40.2d 0.4d | 14.3d 93.3% | 98.0% 10.1d | 1.0d 2026-03-15 01:14:43 288.0 Kbit/s
moria1 (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, Stable 148.0 Mbit/s | 8.4 Mbit/s 148.0 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 92.6% | 98% 9.8d | 8d 18551.2d | 347.6d 0.4d | 15.5d 92.6% | 98.0% 9.81d | 9.85d 2026-03-15 01:14:43 208.0 Kbit/s
tor26 (AT) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 148.0 Mbit/s | 816.0 Kbit/s 148.0 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 92.8% | 98% 10.5d | 8d 0.9d | 55.7d 0.4d | 14.5d 92.8% | 98.0% 10.5d | 1.0d 2026-03-15 01:14:43 368.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.