View Relay "DrevixMiddle01"

Fingerprint: F87C6965DD6C2B72AC750DA26AFF0E09DFD526A8 | Family: 3 relays | info@drevix.de | AS197071 | Germany | Linux

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
6/7 BW Auths Measured 384 Mbit/s Median
Stability
Not Overloaded | UP 2d 20m 23s ago | UP 100% (1M)
Reachability
IPv4: 9/9 | v6: None configured(Directory Auths)
BW Weight
0.03% of Network | 230 Mbit/s Observed By Relay
Version
0.4.9.17 Recommended
Issues Detected:
  • 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 because DirCache 0 is set in torrc.
    Suggestion: Remove DirCache 0 from torrc (DirCache is enabled by default in Tor ≥0.3.3). Restart Tor and verify the descriptor includes tunnelled-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.

Addresses
OR Address
109.230.225.194:9001
Reachability (Directory Authorities)
IPv4
9/9
IPv6
None configured
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS197071
AS Name
active 1 GmbH (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 2 operators)

Current Flags (4): Running, Valid, Fast, Stable
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 9/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 Below (0/9 DA) No DirPort, no tunnelled-dir-server (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 53.6 Mbit/s – 600.0 Mbit/s (6 DA measured)
80.0 Mbit/s (3 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 Partial (8/9 DA) Median: 12.5d (8/9 DA above threshold)
Min/Max: 6.8d / 8287.4d (9/9 DA, Voting / Total Eligible)
≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12669.7d
Uptime Below (0/9 DA) 2.0d (R) ≥5.0d - 5.1d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
53.6 Mbit/s – 600.0 Mbit/s (6 DA measured)
80.0 Mbit/s (3 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 Meets (9/9 DA) 9/9 DA assigned Stable ≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12669.7d
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) 2.0d (R) ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA)
[Stricter] moria1: ≥98% WFU and ≥9.7d Time Known
Guard Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
53.6 Mbit/s – 600.0 Mbit/s (6 DA measured)
80.0 Mbit/s (3 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 Meets (9/9 DA) 9/9 DA assigned Stable ≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12669.7d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (9/9 DA) Median: 100.0% (9/9 DA above threshold)
Min/Med/Max: 98.9% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Partial (8/9 DA) Median: 12.5d (8/9 DA above threshold)
Min/Max: 6.8d / 12.5d (9/9 DA, Voting / Total Eligible)
≥8 days; E30CF7B3: ≥5 days 10 hours 41 minutes 56 seconds (≥5/9 DA)
Bandwidth Meets (9/9 DA) 53.6 Mbit/s – 600.0 Mbit/s (6 DA measured)
80.0 Mbit/s (3 DA relay-reported)
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-248.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-20 08:45:05).

Capacity (Relay Reported)
Observed Bandwidth
230.62 Mbit/s
Advertised Bandwidth
230.62 Mbit/s
Rate Limit
262.14 Mbit/s
Burst Limit
262.14 Mbit/s
Total Data
7.9 TB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-20 08:45:05

Measured By
6/7 Bandwidth Authorities
Not measured by: faravahar
Consensus Weight
384.0 Mbit/s (median of 6 measurements)
Measured Min / Max
53.6 Mbit/s / 600.0 Mbit/s
Deviation
546.4 Mbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0260% of network (90th pctl) | Guard: N/A | Middle: 0.0768% (96th pctl) | Exit: N/A
History
Throughput and write/read, last 30 days

Uptime Metrics
Current Status
UP 2d 20m 23s ago
Overall Uptime (1M/6M/1Y/5Y)
100.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (100.0%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
1w 5d 14h ago (2026-11-07 19:00:00)
Last Seen
1h 45m 32s ago (2026-11-20 08:00:00)
Last Restarted
2d 20m 23s ago (2026-11-18 09:25:09)
Last Changed Address
2026-11-07 19:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Evaluated 2026-11-20 09:45 UTC. /details snapshot 2026-11-20 08:00:00 UTC (cached 37s ago). /bandwidth snapshot 2026-11-20 02:00:00 UTC (cached 6h 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
Uptime, last 30 days

Operator Identity

Source: AROI Validation API — 2026-11-19 23:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
info@drevix.de
Family Configuration
Family Support
Happy Families (3) — Has family-cert in server descriptor (guide) | View Full Family (3)
Happy Families (family-cert)
Effective Members: 3
44088404248A4544A23B07EA559BD6C4F4A3DC7F
7E8C02EBAF4D35627D22CBF76004C3CE72A656F1
F87C6965DD6C2B72AC750DA26AFF0E09DFD526A8 (this relay)
MyFamily (legacy declarations) — none

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

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 Fri, 20 Nov 2026 09:45:32 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-11-20 08: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 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)
E30CF7B3 Yes Yes No — Y Yes Running, Valid, Fast, Stable 256.0 Mbit/s (M) | 816.0 Kbit/s 256.0 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 6.8d | 5d 6.8d | 3.9d 2.0d | 5.1d 2026-11-20 06:47:15 256.0 Mbit/s (M)
dannenberg (DE) Yes Yes No — Y Yes Running, Valid, Fast, Stable 384.0 Mbit/s (M) | 816.0 Kbit/s 384.0 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 12.4d | 8d 12.4d | 8.2d 2.0d | 5.1d 2026-11-20 06:47:15 384.0 Mbit/s (M)
dizum (NL) 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 100.0% | 98% 12.5d | 8d 12.5d | 6.8d 2.0d | 5.1d 2026-11-20 06:47:15 80.0 Mbit/s (R)
faravahar (US) Yes Yes No — Y 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 100.0% | 98% 12.5d | 8d 12.5d | 7.0d 2.0d | 5.1d 2026-11-20 06:47:15 80.0 Mbit/s (R)
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid, Fast, Stable 600.0 Mbit/s (M) | 816.0 Kbit/s 600.0 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 12.5d | 8d 12.5d | 8.3d 2.0d | 5.1d 2026-11-20 06:47:15 600.0 Mbit/s (M)
longclaw (US) Yes Yes No — Y Yes Running, Valid, Fast, Stable 440.0 Mbit/s (M) | 816.0 Kbit/s 440.0 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 12.5d | 8d 12.5d | 9.1d 2.0d | 5.1d 2026-11-20 06:47:15 440.0 Mbit/s (M)
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 99.1% | 98% 11.5d | 8d 8.6d | 2.3d 2.0d | 5.1d 2026-11-20 06:47:15 80.0 Mbit/s (R)
moria1 (US) Yes Yes No — Y Yes Running, Valid, Fast, Stable 53.6 Mbit/s (M) | 8.4 Mbit/s 53.6 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s 98.9% | 98% 7.2d | 8d 8287.4d | 12669.7d 2.0d | 5.0d 2026-11-20 06:47:15 53.6 Mbit/s (M)
tor26 (AT) Yes Yes No — Y Yes Running, Valid, Fast, Stable 528.0 Mbit/s (M) | 816.0 Kbit/s 528.0 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 12.5d | 8d 12.5d | 8.2d 2.0d | 5.1d 2026-11-20 06:47:15 528.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 (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.