View Relay "DerEine"
Fingerprint: 31327848122BB83C306ED2AE65C0CFFD4D6FAC0A |
Family: 1 relay
|
98340E3D12219D607CA0251771C08DB62E690... |
AS6724
|
Germany
|
Linux
- Consensus
- In Consensus (9/9 Directory Auths)
- BW Verified
- 5/7 BW Auths Measured 800 Kbit/s Median
- Stability
- Not Overloaded | UP 1d 8h 38m ago
- Reachability
- IPv4: 9/9 | v6: 8/8(Directory Auths)
- BW Weight
- 0.00% of Network | 4 Mbit/s Observed By Relay
- Version
- 0.4.9.11 Not Recommended
Issues Detected:
-
Guard: requires Fast flag
: Guard flag requires having the Fast flag first
Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports. -
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: bandwidth below threshold
: 0/9 authorities credit this relay with enough bandwidth for Guard (5 needed): at least 16.8 Mbit/s (AuthDirGuardBWGuarantee) or a place in their top 25% (80.0 Mbit/s – 288.0 Mbit/s). bastet, dannenberg, gabelmoo, moria1 and tor26 measured this relay at 8.0 Kbit/s – 3.5 Mbit/s. dizum, faravahar, longclaw and maatuska used the relay-reported 4.9 Mbit/s.
Suggestion: Guard requires a bandwidth of at least AuthDirGuardBWGuarantee (16.8 Mbit/s by default) or one in the top 25% of relays, judged by each authority the same way as for Fast. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx. -
Guard: WFU below threshold
: 0/9 authorities meet guard-wfu (≥98%; dizum: ≥97.264%; 5 needed). bastet, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 measured 3.5%–15.6%.
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
: 0/9 authorities meet Stable (uptime or MTBF at or above their own median; 5 needed). bastet, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 do not.
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 Fast flag
: HSDir flag requires having the Fast flag first
Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports. -
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: 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 -
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. -
Tor version not recommended
: Running Tor version 0.4.9.11 which is not on the recommended list.
Suggestion: Update to the latest stable Tor version. Outdated versions may have security vulnerabilities and could eventually be rejected by the network. See torproject.org/download for latest releases.
Addresses
- OR Address
-
h2174842.stratoserver.net
85.214.100.39:8080
[2a01:238:437e:cb00:aefa:d0c8:6925:2942]:8080
Reachability (Directory Authorities)
- IPv4
- 9/9
- IPv6
- 8/8 (1 don't test)
Location
- Country
-
Germany
- Interactive Map
- View in RouteFluxMap
Eligible Flags (4):
Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 5/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 |
| 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 | Below (0/9 DA) | No DirPort, no tunnelled-dir-server (R) | Tunnelled directory via ORPort or DirPort (≥5/9 DA) |
| Fast | Speed | Partial (5/9 DA) | 8.0 Kbit/s – 3.5 Mbit/s (5 DA measured) 4.9 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: 1.6d (1/9 DA above threshold) Min/Max: 0.9d / 1464.2d (9/9 DA, Voting / Total Eligible) |
≥2.5d - 8.5d (varies) (≥5/9 DA) [Stricter] moria1: ≥8467.5d |
| Uptime | Below (0/9 DA) | 1.4d (R) | ≥3.2d - 4.0d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Meets (5/9 DA) | 5/9 DA assigned Fast 8.0 Kbit/s – 3.5 Mbit/s (5 DA measured) 4.9 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 | Below (1/9 DA) | 1/9 DA assigned Stable | ≥2.5d - 8.5d (varies) (≥5/9 DA) [Stricter] moria1: ≥8467.5d |
|
| Prereq: V2Dir | Below (0/9 DA) | 0/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| Uptime | Below (0/9 DA) | 1.4d (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.9d Time Known |
|
| Guard | Prereq: Fast | Meets (5/9 DA) | 5/9 DA assigned Fast 8.0 Kbit/s – 3.5 Mbit/s (5 DA measured) 4.9 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 | Below (1/9 DA) | 1/9 DA assigned Stable | ≥2.5d - 8.5d (varies) (≥5/9 DA) [Stricter] moria1: ≥8467.5d |
|
| Prereq: V2Dir | Below (0/9 DA) | 0/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Below (0/9 DA) | Median: 6.8% (0/9 DA above threshold) Min/Max: 3.5% / 15.6% (9/9 DA, Voting / Total Eligible) |
≥98%; dizum: ≥97.264% (≥5/9 DA) | |
| Time Known | Meets (9/9 DA) | Median: 24.5d (9/9 DA above threshold) Min/Max: 9.9d / 26.4d (9/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Below (0/9 DA) | 8.0 Kbit/s – 3.5 Mbit/s (5 DA measured) 4.9 Mbit/s (4 DA relay-reported) |
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-288.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-02 07:45:06).
Capacity (Relay Reported)
- Observed Bandwidth
- 4.96 Mbit/s
- Advertised Bandwidth
- 4.92 Mbit/s
- Rate Limit
- 4.92 Mbit/s
- Burst Limit
- 7.37 Mbit/s
- Total Data
- 128 MB (1 month)
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-02 07:45:06
- Measured By
-
5/7
Bandwidth Authorities
Not measured by: faravahar, longclaw - Consensus Weight
- 800.0 Kbit/s (median of 5 measurements)
- Measured Min / Max
- 8.0 Kbit/s / 3.5 Mbit/s
- Deviation
- 3.5 Mbit/s [Warning] High variation
Network Participation:
Consensus Weight:
0.0000% of network
(6th pctl)
|
Guard:
N/A |
Middle:
0.0001% (7th pctl) |
Exit:
N/A
History
Uptime Metrics
- Current Status
- UP 1d 8h 38m ago
- Overall Uptime (1M/6M/1Y/5Y)
- 0.0%/0.0%/0.0%/0.0%
- Flag Uptime (1M/6M/1Y/5Y)
- Matches Overall Uptime (0.0%/0.0%/0.0%/0.0%)
- Hibernating
- No
Timestamps
- First Seen
- 1d 7h 45m ago (2026-11-01 00:00:00)
- Last Seen
- 1h 45m 28s ago (2026-11-02 06:00:00)
- Last Restarted
- 1d 8h 38m ago (2026-10-31 23:06:59)
- Last Changed Address
- 2026-11-01 00:00:00
Overload Status:
Not Overloaded — No overload conditions reported.
Evaluated 2026-11-02 07:45 UTC. /details snapshot 2026-11-02 06:00:00 UTC (cached 24s ago). /bandwidth snapshot 2026-11-02 05:00:00 UTC (cached 1h 30m 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-01 22:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- 98340E3D12219D607CA0251771C08DB62E69060D tmheinz@gmx.net
Family Configuration
- Family Support
- None — No family membership configured
Happy Families (family-cert)
- Effective Members: 0
- none
MyFamily (legacy declarations)
- Effective Member: 1
31327848122BB83C306ED2AE65C0CFFD4D6FAC0A (this relay)
- Alleged Members: 0
- none
- Indirect Members: 0
- none
- Platform
- Linux — Tor 0.4.9.11 on Linux
- Version
- 0.4.9.11 — Not Recommended
- Version Status
- Obsolete — Update urgently. See torproject.org/download
DNS Health
Not an exit relay — DNS health testing does not apply.IPv4 Exit Policy Summary
accept: 6660-6667
IPv6 Exit Policy Summary
NoneFull 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 85.214.100.39:* accept *:6660-6667 reject *:*
Last fetch was at Mon, 02 Nov 2026 07:45:27 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-02 07: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 | 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 | No | — | Y | Yes | Yes | Running, Valid, Fast | 3.5 Mbit/s (M) | 816.0 Kbit/s | 3.5 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 4.1% | 98% | 26.4d | 8d | 1.0d | 7.1d | 1.4d | 3.4d | 2026-11-01 01:16:11 | 3.5 Mbit/s (M) |
| dannenberg (DE) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid | 800.0 Kbit/s (M) | 816.0 Kbit/s | 800.0 Kbit/s (M) | 288.0 Mbit/s OR 16.8 Mbit/s | 6.8% | 98% | 24.5d | 8d | 1.4d | 8.5d | 1.4d | 4.0d | 2026-11-01 19:16:13 | 800.0 Kbit/s (M) |
| dizum (NL) | Yes | Yes | No | — | N | Yes | Yes | Running, Valid, Fast | 4.9 Mbit/s (R) | 816.0 Kbit/s | 4.9 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 6.5% | 97% | 25.7d | 8d | 1.6d | 5.9d | 1.4d | 4.0d | 2026-11-01 19:16:13 | 4.9 Mbit/s (R) |
| faravahar (US) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, Fast | 4.9 Mbit/s (R) | 816.0 Kbit/s | 4.9 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 6.8% | 98% | 24.5d | 8d | 1.6d | 5.9d | 1.4d | 4.0d | 2026-11-01 19:16:13 | 4.9 Mbit/s (R) |
| gabelmoo (DE) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid | 8.0 Kbit/s (M) | 816.0 Kbit/s | 8.0 Kbit/s (M) | 264.0 Mbit/s OR 16.8 Mbit/s | 6.5% | 98% | 25.7d | 8d | 1.6d | 9.8d | 1.4d | 4.0d | 2026-11-01 19:16:13 | 8.0 Kbit/s (M) |
| longclaw (US) | Yes | Yes | No | — | Y | Yes | N/T | Running, Valid, Fast | 4.9 Mbit/s (R) | 816.0 Kbit/s | 4.9 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 6.8% | 98% | 24.5d | 8d | 1.6d | 9.9d | 1.4d | 4.0d | 2026-11-01 19:16:13 | 4.9 Mbit/s (R) |
| maatuska (SE) | Yes | Yes | No | — | N | Yes | Yes | Running, Valid, Fast | 4.9 Mbit/s (R) | 816.0 Kbit/s | 4.9 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 3.5% | 98% | 26.2d | 8d | 0.9d | 2.5d | 1.4d | 3.2d | 2026-11-01 01:16:11 | 4.9 Mbit/s (R) |
| moria1 (US) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, Stable | 2.9 Mbit/s (M) | 8.4 Mbit/s | 2.9 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 15.6% | 98% | 9.9d | 8d | 1464.2d | 8467.5d | 1.4d | 4.0d | 2026-11-01 19:16:13 | 2.9 Mbit/s (M) |
| tor26 (AT) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid | 632.0 Kbit/s (M) | 816.0 Kbit/s | 632.0 Kbit/s (M) | 264.0 Mbit/s OR 16.8 Mbit/s | 6.8% | 98% | 24.5d | 8d | 1.6d | 9.8d | 1.4d | 4.0d | 2026-11-01 19:16:13 | 632.0 Kbit/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.