View Relay "mixminion"
Fingerprint: 38F732DD349A2E59078434651162A2F4201934A5 |
Family: 1 relay
|
email:minionrelay@protonmail.com... |
AS24940
|
Germany
|
Linux
- Consensus
- Not In Consensus (2/9 Directory Auths, need 5)
- BW Verified
- 1/7 BW Auths Measured 160 Kbit/s Median
- Stability
- Not Overloaded | DOWN 1d 3h 45m ago | UP 95% (1M)
- Reachability
- IPv4: 2/9 | v6: 2/2(Directory Auths)
- BW Weight
- 0.07% of Network | 479 Mbit/s Observed By Relay
- Version
- 0.4.9.15 Recommended
Issues Detected:
-
Not in consensus
: Only 2/9 authorities voted for this relay (need 5)
Suggestion: Verify your relay is reachable from multiple geographic locations. Check firewall rules allow incoming connections on your ORPort from all directory authority IP addresses. -
IPv4 reachability issues
: Only 2/9 authorities can reach this relay
Suggestion: Authorities that cannot reach you: bastet, faravahar, gabelmoo, longclaw, maatuska, moria1, tor26. Check: 1) Firewall allows incoming TCP on ORPort, 2) No ISP-level blocking, 3) Tor is running and listening. Use 'nc -zv your-ip your-orport' from external hosts to test. -
Low bandwidth authority measurements
: Only 1/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.
Notes:
- Guard: WFU near threshold: Weighted Fractional Uptime is just under the Guard bar at dizum (97.9%, need ≥98%). Recent downtime weighs more than older downtime. Avoid restarts while it is this close; a short outage can drop the Guard flag.
Suggestion: Recent downtime weighs more than older downtime. Minimize restarts, use systemd Restart=always, and watch for OOM kills until each authority has more room above its own guard-wfu.
Addresses
- OR Address
-
static.198.81.76.144.clients.your-server.de
144.76.81.198:8443
[2a01:4f8:192:3c5::2]:8443
Reachability (Directory Authorities)
- IPv4
- 2/9
- IPv6
- 2/2
Location
- Country
-
Germany
- Interactive Map
- View in RouteFluxMap
Eligible Flags (0):
Running: 2/9 | Valid: 2/9 | V2Dir: 2/9 | Fast: 2/9 | Stable: 2/9 | HSDir: 0/9 | Guard: 1/9 | Exit: 0/9
Eligibility Flag Vote Details
| Flag | Metric | Status | Relay Value | Threshold Required |
|---|---|---|---|---|
| Running | IPv4 Reachability | Below (2/9 DA) | 2/9 authorities reached relay | ≥5/9 DA ORPort reachable |
| IPv6 Reachability | Meets (2/2 DA) | 2/2 tested authorities reached relay | ≥2/2 tested (majority) (≥2/2 DA) | |
| Valid | Descriptor | Partial (2/9 DA) | 2/9 authorities assigned Valid | Not blacklisted + valid descriptor (≥5/9 DA) |
| V2Dir | DirPort Available | Meets (2/9 DA) | Tunnelled: Yes (no DirPort) (R) | Tunnelled directory via ORPort or DirPort (≥5/9 DA) |
| Fast | Speed | Below (2/9 DA) | 1.4 Gbit/s (1 DA measured) 80.0 Mbit/s (1 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.0d (0/9 DA above threshold) Min/Max: 6.5d / 7.5d (2/9 DA, Voting / Total Eligible) |
≥2.6d - 10.0d (varies) (≥5/9 DA) [Stricter] moria1: ≥7246.1d |
| Uptime | Below (0/9 DA) | 1.6d (R) | ≥5.5d - 5.5d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Below (2/9 DA) | 2/9 DA assigned Fast 1.4 Gbit/s (1 DA measured) 80.0 Mbit/s (1 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 | Below (2/9 DA) | 2/9 DA assigned Stable | ≥2.6d - 10.0d (varies) (≥5/9 DA) [Stricter] moria1: ≥7246.1d |
|
| Prereq: V2Dir | Below (2/9 DA) | 2/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| Uptime | Below (0/9 DA) | 1.6d (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.8d Time Known |
|
| Guard | Prereq: Fast | Below (2/9 DA) | 2/9 DA assigned Fast 1.4 Gbit/s (1 DA measured) 80.0 Mbit/s (1 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 | Below (2/9 DA) | 2/9 DA assigned Stable | ≥2.6d - 10.0d (varies) (≥5/9 DA) [Stricter] moria1: ≥7246.1d |
|
| Prereq: V2Dir | Below (2/9 DA) | 2/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Below (1/9 DA) | Median: 98.7% (1/9 DA above threshold) Min/Max: 97.9% / 99.5% (2/9 DA, Voting / Total Eligible) |
≥98% (≥5/9 DA) | |
| Time Known | Below (2/9 DA) | Median: 14.7d (2/9 DA above threshold) Min/Max: 13.9d / 15.5d (2/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Below (2/9 DA) | 1.4 Gbit/s (1 DA measured) 80.0 Mbit/s (1 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 | 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-05 15:45:05).
Capacity (Relay Reported)
- Observed Bandwidth
- 479.93 Mbit/s
- Advertised Bandwidth
- 479.93 Mbit/s
- Rate Limit
- 8.59 Gbit/s
- Burst Limit
- 8.59 Gbit/s
- Total Data
-
9.8 PB
(5 years)
1mo: 205 TB | 6mo: 1.2 PB | 1y: 2.2 PB | 5y: 9.8 PB
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-05 15:45:05
- Measured By
-
1/7
Bandwidth Authorities
Not measured by: bastet, faravahar, gabelmoo, longclaw, moria1, tor26 - Consensus Weight
- 160.0 Kbit/s (Unmeasured)
- Measured Min / Max
- 1.4 Gbit/s / 1.4 Gbit/s
Network Participation:
Consensus Weight:
0.0719% of network
(99th pctl)
|
Guard:
N/A |
Middle:
N/A |
Exit:
N/A
History
Uptime Metrics
- Current Status
- DOWN 1d 3h 45m ago
- Overall Uptime (1M/6M/1Y/5Y)
- 95.7%/98.6%/99.4%/86.2%
- Flag Uptime (1M/6M/1Y/5Y)
- 81.3%/93.2%/96.7%/85.5%
- Hibernating
- No
Timestamps
- First Seen
- 3y 12mo 2d ago (2022-11-09 00:00:00)
- Last Seen
- 1d 3h 45m ago (2026-11-04 13:00:00)
- Last Restarted
- 1d 14h 24m ago (2026-11-04 02:20:59)
- Last Changed Address
- 2026-04-06 23:00:00
Overload Status:
Not Overloaded — No overload conditions reported.
Evaluated 2026-11-05 16:45 UTC. /details snapshot 2026-11-05 15:00:00 UTC (cached 23s ago). /bandwidth snapshot 2026-11-05 08:00:00 UTC (cached 7h 29m 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
Operator Identity
Source: AROI Validation API — 2026-11-05 07:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- email:minionrelay@protonmail.com ciissversion:2
Family Configuration
- Family Support
- None — No family membership configured
Happy Families (family-cert)
- Effective Members: 0
- none
MyFamily (legacy declarations)
- Effective Member: 1
38F732DD349A2E59078434651162A2F4201934A5 (this relay)
- Alleged Members: 0
- none
- Indirect Members: 0
- none
DNS Health
Not an exit relay — DNS health testing does not apply.Last fetch was at Thu, 05 Nov 2026 16:45:20 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-05 15:45:05).
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) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — |
| dannenberg (DE) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, Guard | 1.4 Gbit/s (M) | 816.0 Kbit/s | 1.4 Gbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s | 99.5% | 98% | 15.5d | 8d | 7.5d | 10.0d | 1.6d | 5.6d | 2026-11-05 12:14:05 | 80.0 Mbit/s (R) |
| dizum (NL) | Yes | Yes | No | — | N | Yes | Yes | Running, Valid, V2Dir, 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 | 97.9% | 98% | 13.9d | 8d | 6.5d | 7.3d | 1.6d | 5.5d | 2026-11-05 12:14:05 | 80.0 Mbit/s (R) |
| faravahar (US) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — |
| gabelmoo (DE) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — |
| longclaw (US) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — |
| maatuska (SE) | No | — | — | — | N | No | — | — | — | — | — | — | — | — | — | — |
| moria1 (US) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — |
| tor26 (AT) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — |
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 (
Relay-reported (R) = The bandwidth your relay advertises: the lower of its observed bandwidth and its rate limit, capped at 10 MB/s (
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.
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.
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.