View Relay "GermanCraft15"
Fingerprint: 011142D1B78B218D44F1377FC9307C5910B6D36C |
Operator: germancraft.net v2
(24 relays)
✓ Validated
🚫 this relay: Unauthorized|
Family: 1 relay
|
ContactInfo email:knight AT... |
AS21336
|
Germany
|
Linux
- Consensus
- In Consensus (10/10 Directory Auths)
- BW Verified
- 5/8 BW Auths Measured 112 Mbit/s Median
- Stability
- Not Overloaded | UP 3d 20h 39m ago | UP 88% (1M)
- Reachability
- IPv4: 10/10 | v6: None configured(Directory Auths)
- BW Weight
- 0.01% of Network | 118 Mbit/s Observed By Relay
- Version
- 0.4.9.16 Recommended
Issues Detected:
-
Guard: WFU below threshold
: 2/10 authorities meet guard-wfu (≥98%; maatuska: ≥96.954%; 6 needed). dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 measured 76.0%–94.5%.
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. -
HSDir: requires V2Dir (tunnelled-dir-server)
: HSDir requires the relay to support tunnelled directory requests (V2Dir flag). This relay is missing V2Dir — the descriptor likely does not include
tunnelled-dir-server, usually becauseDirCache 0is set in torrc.
Suggestion: RemoveDirCache 0from torrc (DirCache is enabled by default in Tor ≥0.3.3). Restart Tor and verify the descriptor includestunnelled-dir-server. You can check with:grep tunnelled-dir-server /var/lib/tor/cached-descriptors
Addresses
- OR Address
-
ip-212-27-159-3.ip-addr.treudler.net
212.27.159.3:443
Reachability (Directory Authorities)
- IPv4
- 10/10
- IPv6
- None configured
Location
- Country
-
Germany
- Interactive Map
- View in RouteFluxMap
Eligible Flags (4):
Running: 10/10 | Valid: 10/10 | V2Dir: 10/10 | Fast: 10/10 | Stable: 5/10 | HSDir: 0/10 | Guard: 0/10 | Exit: 0/10
Eligibility Flag Vote Details
| Flag | Metric | Status | Relay Value | Threshold Required |
|---|---|---|---|---|
| Running | IPv4 Reachability | Meets (10/10 DA) | 10/10 authorities reached relay | ≥6/10 DA ORPort reachable |
| Valid | Descriptor | Meets (10/10 DA) | 10/10 authorities assigned Valid | Not blacklisted + valid descriptor (≥6/10 DA) |
| V2Dir | DirPort Available | Below (0/10 DA) | No DirPort, no tunnelled-dir-server (R) | Tunnelled directory via ORPort or DirPort (≥6/10 DA) |
| Fast | Speed | Meets (10/10 DA) | 88.0 Mbit/s – 144.0 Mbit/s (5 DA measured) 80.0 Mbit/s (5 DA relay-reported) |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥6/10 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Stable | MTBF | Below (4/10 DA) | Median: 4.0d (1/10 DA above threshold) Min/Max: 0.0d / 14327.1d (10/10 DA, Voting / Total Eligible) |
≥0.0d - 9.3d (varies) (≥6/10 DA) [Stricter] moria1: ≥10647.1d |
| Uptime | Partial (9/10 DA) | 3.9d (R) | ≥2.9d - 3.1d (varies) (≥6/10 DA) | |
| HSDir | Prereq: Fast | Meets (10/10 DA) | 10/10 DA assigned Fast 88.0 Mbit/s – 144.0 Mbit/s (5 DA measured) 80.0 Mbit/s (5 DA relay-reported) |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥6/10 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Below (5/10 DA) | 5/10 DA assigned Stable | ≥0.0d - 9.3d (varies) (≥6/10 DA) [Stricter] moria1: ≥10647.1d |
|
| Prereq: V2Dir | Below (0/10 DA) | 0/10 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥6/10 DA) | |
| Uptime | Below (0/10 DA) | 3.9d (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥6/10 DA) [Stricter] moria1: ≥98% WFU and ≥9.8d Time Known |
|
| Guard | Prereq: Fast | Meets (10/10 DA) | 10/10 DA assigned Fast 88.0 Mbit/s – 144.0 Mbit/s (5 DA measured) 80.0 Mbit/s (5 DA relay-reported) |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥6/10 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Below (5/10 DA) | 5/10 DA assigned Stable | ≥0.0d - 9.3d (varies) (≥6/10 DA) [Stricter] moria1: ≥10647.1d |
|
| Prereq: V2Dir | Below (0/10 DA) | 0/10 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥6/10 DA) | |
| WFU | Below (2/10 DA) | Median: 89.6% (2/10 DA above threshold) Min/Max: 76.0% / 100.0% (10/10 DA, Voting / Total Eligible) |
≥98%; maatuska: ≥96.954% (≥6/10 DA) | |
| Time Known | Meets (10/10 DA) | Median: 13.9d (10/10 DA above threshold) Min/Max: 0.0d / 19.0d (10/10 DA, Voting / Total Eligible) |
≥8 days; 5947BB57: ≥37 minutes 34 seconds; E30CF7B3: ≥1 day 4 hours 12 minutes 33 seconds (≥6/10 DA) | |
| Bandwidth | Meets (10/10 DA) | 88.0 Mbit/s – 144.0 Mbit/s (5 DA measured) 80.0 Mbit/s (5 DA relay-reported) |
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-256.0 Mbit/s) (≥6/10 DA) | |
| Exit | Exit Policy | Below (0/10 DA) | Port 80: No | Port 443: No (R) | Allows ≥1 /8 on ports 80 AND 443 (≥6/10 DA) |
(DA) = Dir. Auth. Measured |
(R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-11-14 01:45:06).
Capacity (Relay Reported)
- Observed Bandwidth
- 118.01 Mbit/s
- Advertised Bandwidth
- 118.01 Mbit/s
- Rate Limit
- 314.57 Mbit/s
- Burst Limit
- 419.43 Mbit/s
- Total Data
-
74 TB
(6 months)
1mo: 58 TB | 6mo: 74 TB
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-14 01:45:06
- Measured By
-
5/8
Bandwidth Authorities
Not measured by: 5947BB57, faravahar, longclaw - Consensus Weight
- 112.0 Mbit/s (median of 5 measurements)
- Measured Min / Max
- 88.0 Mbit/s / 144.0 Mbit/s
Network Participation:
Consensus Weight:
0.0077% of network
(59th pctl)
|
Guard:
N/A |
Middle:
0.0226% (83th pctl) |
Exit:
N/A
History
Uptime Metrics
- Current Status
- UP 3d 20h 39m ago
- Overall Uptime (1M/6M/1Y/5Y)
- 88.6%/90.0%/0.0%/0.0%
- Flag Uptime (1M/6M/1Y/5Y)
- 86.7%/88.4%/—/—
- Hibernating
- No
Timestamps
- First Seen
- 1mo 5d 12h ago (2026-10-09 14:00:00)
- Last Seen
- 1h 15m 39s ago (2026-11-14 01:00:00)
- Last Restarted
- 3d 20h 39m ago (2026-11-10 05:35:44)
- Last Changed Address
- 2026-11-06 04:00:00
Overload Status:
Not Overloaded — No overload conditions reported.
Evaluated 2026-11-14 02:15 UTC. /details snapshot 2026-11-14 01:00:00 UTC (cached 30s ago). /bandwidth snapshot 2026-11-13 19: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
Operator Identity
Source: AROI Validation API — 2026-11-13 15:00 UTC
- AROI Domain (?)
- germancraft.net
- Operator Validation
- Validated (17/24 relays)
- This Relay
-
Unvalidated
Error: DNS-RSA: TXT record has invalid proof content. Expected 'we-run-this-tor-relay', found: 4cedd9e3be24c15f8a274b06b408595084fe1ed6; v=spf1 mx -all - Contact
- ContactInfo email:knight AT germancraft dot net url:germancraft.net proof:dns-rsa abuse:knight AT germancraft dot net pgp:4cf76925833e2e24 twitter:knightyyyy1 btc:1MTXtuSCCTf6J3TiUnk1ePwgaHt9h6uQaU Updateofflinemasterkey:y sandbox:y os:Debian aesni:y autoupdate:y confmgmt:Ansible ciissversion:2 trafficacct:unmetered ciissversion:2
Family Configuration
- Family Support
- Happy Families (8) — Has family-cert in server descriptor (guide)
Happy Families (family-cert)
- Effective Members: 8
011142D1B78B218D44F1377FC9307C5910B6D36C (this relay) 335D44B4BCABF78DAE584193CEBB687AA18D6DFD 485463A9B192A7E38DDB7D2280BD91098B490C3D 485E171AE98B8ED36205B5ACCA0318F8DD6EA383 5665A3904C89E22E971305EE8C1997BCA4123C69 58AD098F4A6FE7964F63A0C990D02C12B9722D91 590303772AB13A55548042FC3501C029529F50C6 5F96CDCAEED3A18CDBAB2B5AFC85334B12E5FD73
MyFamily (legacy declarations) — none
DNS Health
Not an exit relay — DNS health testing does not apply.Last fetch was at Sat, 14 Nov 2026 02:15:38 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-14 01:45:06).
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 (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) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 5947BB57 | Yes | Yes | No | — | Y | Yes | Running, Valid, Fast | 80.0 Mbit/s (R) | 816.0 Kbit/s | 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 0.0d | 0d | 0.0d | 0.0d | 3.9d | 5.9d | 2026-11-12 09:45:53 | 80.0 Mbit/s (R) |
| E30CF7B3 | Yes | Yes | No | — | Y | Yes | Running, Valid, Fast | 96.0 Mbit/s (M) | 816.0 Kbit/s | 96.0 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 1.2d | 1d | 1.2d | 1.2d | 3.9d | 3.4d | 2026-11-13 23:15:59 | 96.0 Mbit/s (M) |
| dannenberg (DE) | Yes | Yes | No | — | Y | Yes | Running, Valid, Fast, Stable | 144.0 Mbit/s (M) | 816.0 Kbit/s | 144.0 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s | 94.3% | 98% | 18.9d | 8d | 6.4d | 9.3d | 3.9d | 3.1d | 2026-11-13 23:15:59 | 144.0 Mbit/s (M) |
| dizum (NL) | Yes | Yes | No | — | N | Yes | Running, Valid, Fast | 80.0 Mbit/s (R) | 816.0 Kbit/s | 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 79.1% | 98% | 13.4d | 8d | 3.1d | 7.2d | 3.9d | 3.2d | 2026-11-13 23:15:59 | 80.0 Mbit/s (R) |
| faravahar (US) | Yes | Yes | No | — | Y | Yes | Running, Valid, Fast | 80.0 Mbit/s (R) | 816.0 Kbit/s | 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 80.2% | 98% | 14.4d | 8d | 3.2d | 6.9d | 3.9d | 3.1d | 2026-11-13 23:15:59 | 80.0 Mbit/s (R) |
| gabelmoo (DE) | Yes | Yes | No | — | Y | Yes | Running, Valid, Fast, Stable | 136.0 Mbit/s (M) | 816.0 Kbit/s | 136.0 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s | 94.5% | 98% | 18.7d | 8d | 6.5d | 9.5d | 3.9d | 3.1d | 2026-11-13 23:15:59 | 136.0 Mbit/s (M) |
| longclaw (US) | Yes | Yes | No | — | Y | Yes | Running, Valid, Fast | 80.0 Mbit/s (R) | 816.0 Kbit/s | 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 84.9% | 98% | 18.6d | 8d | 4.7d | 10.1d | 3.9d | 3.1d | 2026-11-13 23:15:59 | 80.0 Mbit/s (R) |
| maatuska (SE) | Yes | Yes | No | — | N | Yes | Running, Valid, 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 | 83.3% | 97% | 13.4d | 8d | 1.7d | 1.5d | 3.9d | 2.9d | 2026-11-13 23:15:59 | 80.0 Mbit/s (R) |
| moria1 (US) | Yes | Yes | No | — | Y | Yes | Running, Valid, Fast, Stable | 88.0 Mbit/s (M) | 8.4 Mbit/s | 88.0 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s | 76.0% | 98% | 9.7d | 8d | 14327.1d | 10647.1d | 3.9d | 3.4d | 2026-11-13 23:15:59 | 88.0 Mbit/s (M) |
| tor26 (AT) | Yes | Yes | No | — | Y | Yes | Running, Valid, Fast, Stable | 112.0 Mbit/s (M) | 816.0 Kbit/s | 112.0 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s | 94.5% | 98% | 19.0d | 8d | 6.5d | 9.7d | 3.9d | 2.9d | 2026-11-13 23:15:59 | 112.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 (
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.