View Relay "DrevixExit02"

Fingerprint: 7E8C02EBAF4D35627D22CBF76004C3CE72A656F1 | Family: 3 relays | tor@drevix.de | AS8560 | Germany | Linux

Consensus
In Consensus (9/9 Directory Auths)
DNS Health
Healthy (15.4s, 50th percentile) (via exitdnshealth.1aeo.com)
BW Verified
6/7 BW Auths Measured 73 Mbit/s Median
Stability
Not Overloaded | UP 3d 16h 8m ago
Reachability
IPv4: 9/9 | v6: None configured(Directory Auths)
BW Weight
0.00% of Network | 59 Mbit/s Observed By Relay
Version
0.4.9.15 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: Time Known below threshold : 0/9 authorities meet guard-tk (≥8 days; E30CF7B3: ≥5 days 10 hours 41 minutes 56 seconds; 5 needed). E30CF7B3, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 have known this relay for 2.8 days–3.6 days.
    Suggestion: Time Known tracks how long authorities have observed your relay. This resets if: 1) Identity key changes, 2) Long downtime makes authorities forget you. Just keep running stably.
  • Not eligible for Stable flag : 1/9 authorities meet Stable (uptime or MTBF at or above their own median; 5 needed). E30CF7B3, dannenberg, dizum, faravahar, gabelmoo, longclaw, 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 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.
  • 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
217.154.92.188:9001
Exit Address
217.154.92.188
Reachability (Directory Authorities)
IPv4
9/9
IPv6
None configured
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS8560
AS Name
IONOS SE (BGP.tools)
AS Rarity
Emerging (score: 1/5, 3.28% consensus weight, 150 operators)

Current Flags (5): Running, Valid, V2Dir, Fast, Exit
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 8/9 | Stable: 1/9 | HSDir: 1/9 | Guard: 0/9 | Exit: 9/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 Partial (8/9 DA) 8.0 Kbit/s – 184.0 Mbit/s (6 DA measured)
59.7 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 Below (1/9 DA) Median: 3.6d (0/9 DA above threshold)
Min/Max: 2.8d / 3.6d (9/9 DA, Voting / Total Eligible)
≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12669.7d
Uptime Below (0/9 DA) 3.7d (R) ≥5.0d - 5.1d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (8/9 DA) 8/9 DA assigned Fast
8.0 Kbit/s – 184.0 Mbit/s (6 DA measured)
59.7 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 Below (1/9 DA) 1/9 DA assigned Stable ≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12669.7d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Uptime Below (1/9 DA) 3.7d (R) ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA)
[Stricter] moria1: ≥98% WFU and ≥9.7d Time Known
Guard Prereq: Fast Meets (8/9 DA) 8/9 DA assigned Fast
8.0 Kbit/s – 184.0 Mbit/s (6 DA measured)
59.7 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 Below (1/9 DA) 1/9 DA assigned Stable ≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12669.7d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (9/9 DA) Majority: 100.0% (9/9 DA above threshold) ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) Median: 3.6d (0/9 DA above threshold)
Min/Max: 2.8d / 3.6d (9/9 DA, Voting / Total Eligible)
≥8 days; E30CF7B3: ≥5 days 10 hours 41 minutes 56 seconds (≥5/9 DA)
Bandwidth Partial (8/9 DA) 8.0 Kbit/s – 184.0 Mbit/s (6 DA measured)
59.7 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 Meets (9/9 DA) Port 80: Yes | Port 443: Yes (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
59.68 Mbit/s
Advertised Bandwidth
59.68 Mbit/s
Rate Limit
256.00 Mbit/s
Burst Limit
256.00 Mbit/s
Total Data
26 GB (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
73.6 Mbit/s (median of 6 measurements)
Measured Min / Max
8.0 Kbit/s / 184.0 Mbit/s
Deviation
184.0 Mbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0050% of network (47th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0155% (30th pctl)
History
Throughput and write/read, last 30 days

Uptime Metrics
Current Status
UP 3d 16h 8m 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
3d 15h 45m ago (2026-11-16 18:00:00)
Last Seen
1h 45m 32s ago (2026-11-20 08:00:00)
Last Restarted
3d 16h 8m ago (2026-11-16 17:36:53)
Last Changed Address
2026-11-16 18: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
tor@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 (this relay)
F87C6965DD6C2B72AC750DA26AFF0E09DFD526A8
MyFamily (legacy declarations) — none

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

DNS Health
Status
Healthy (avg. 15.4s, 50th percentile)
Query Domain
3d54a023f0e542f0bce7de46dbba66ba.7e8c02eb.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Upstream Resolver
Not enough data
Local AS 100% (~8 estimated queries)
Cross-Validation
4/4 instances succeeded
First Hop
poneymagic (CA) D99276A647B27BE5FFE0356244D7625985F82A84
Exit Address Used
217.154.92.188
Per-Instance Results
Cross Validation Attempt 1: Success, 12.7s (cv1_w2)
Cross Validation Attempt 2: Success, 14.8s (cv2_w2)
Cross Validation Attempt 3: Success, 14.6s (cv3_w2)
Cross Validation Attempt 4: Success, 19.5s (cv4_w2)
Tested: 2026-11-19 20:10:41 UTC
IPv4 Exit Policy Summary
accept: 
  43
  53
  80
  443
  853
  1194
  3690
  5222-5223
  5228
  8000
  8008
  8080
  8082
  8087-8088
  8443
  8888
  9418
  11371
  64738
IPv6 Exit Policy Summary
None
Full 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 217.154.92.188:*
accept *:43
accept *:53
accept *:80
accept *:443
accept *:853
accept *:1194
accept *:3690
accept *:5222-5223
accept *:5228
accept *:8000
accept *:8008
accept *:8080
accept *:8082
accept *:8087-8088
accept *:8443
accept *:8888
accept *:9418
accept *:11371
accept *:64738
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 Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 80.0 Mbit/s (M) | 816.0 Kbit/s 80.0 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 2.8d | 5d 2.8d | 3.9d 3.7d | 5.1d 2026-11-20 01:39:33 80.0 Mbit/s (M)
dannenberg (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 54.4 Mbit/s (M) | 816.0 Kbit/s 54.4 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 3.6d | 8d 3.6d | 8.2d 3.7d | 5.1d 2026-11-20 01:39:33 54.4 Mbit/s (M)
dizum (NL) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Exit 59.7 Mbit/s (R) | 816.0 Kbit/s 59.7 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 3.6d | 8d 3.6d | 6.8d 3.7d | 5.1d 2026-11-20 01:39:33 59.7 Mbit/s (R)
faravahar (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 59.7 Mbit/s (R) | 816.0 Kbit/s 59.7 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 3.6d | 8d 3.6d | 7.0d 3.7d | 5.1d 2026-11-20 01:39:33 59.7 Mbit/s (R)
gabelmoo (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 73.6 Mbit/s (M) | 816.0 Kbit/s 73.6 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 3.6d | 8d 3.6d | 8.3d 3.7d | 5.1d 2026-11-20 01:39:33 73.6 Mbit/s (M)
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 104.0 Mbit/s (M) | 816.0 Kbit/s 104.0 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 3.6d | 8d 3.6d | 9.1d 3.7d | 5.1d 2026-11-20 01:39:33 104.0 Mbit/s (M)
maatuska (SE) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 59.7 Mbit/s (R) | 816.0 Kbit/s 59.7 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 3.6d | 8d 3.6d | 2.3d 3.7d | 5.1d 2026-11-20 01:39:33 59.7 Mbit/s (R)
moria1 (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 8.0 Kbit/s (M) | 8.4 Mbit/s 8.0 Kbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 3.0d | 8d 3.6d | 12669.7d 3.7d | 5.0d 2026-11-20 01:39:33 8.0 Kbit/s (M)
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 184.0 Mbit/s (M) | 816.0 Kbit/s 184.0 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 3.6d | 8d 3.6d | 8.2d 3.7d | 5.1d 2026-11-20 01:39:33 184.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.