View Relay "Hormuz"

Fingerprint: DFE69F153172111298D39BBBC6DF6D4F5F965EDB | Family: 1 relay | AS24940 | Germany | Linux

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
6/7 BW Auths Measured 48 Mbit/s Median
Stability
Not Overloaded | UP 1mo 24m 36s ago | UP 100% (1M)
Reachability
IPv4: 9/9 | v6: 8/8(Directory Auths)
BW Weight
0.00% of Network | 60 Mbit/s Observed By Relay
Version
0.4.9.14 Not 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.
  • BadExit flag assigned : This relay has been flagged as a bad exit by directory authorities. BadExit means authorities detected malicious behavior (traffic modification, SSL stripping, etc.).
    Suggestion: Contact bad-relays@lists.torproject.org to understand and resolve this issue.
  • MiddleOnly restriction active : This relay has been restricted to middle position only by directory authorities. MiddleOnly removes Guard, Exit, HSDir, and V2Dir flags, and adds BadExit. This significantly limits the relay's role in the network.
    Suggestion: This may indicate suspicious behavior patterns, Sybil risk indicators, or policy violations. Contact bad-relays@lists.torproject.org for more information.
  • Tor version not recommended : Running Tor version 0.4.9.14 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
static.208.187.76.144.clients.your-server.de
144.76.187.208:9001
[2a01:4f8:173:1763:73da:a392:c19b:9aa3]:9001
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS24940
AS Name
Hetzner Online GmbH (BGP.tools)
AS Rarity
Common (score: 0/5, 8.01% consensus weight, 252 operators)

Current Flags (6): Running, Valid, Fast, Stable, MiddleOnly, BadExit
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 8/9 | HSDir: 2/9 | Guard: 2/9 | Exit: 2/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 (2/9 DA) No DirPort, no tunnelled-dir-server (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 32.8 Mbit/s – 96.0 Mbit/s (6 DA measured)
58.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 Partial (7/9 DA) Median: 29.8d (7/9 DA above threshold)
Min/Max: 1.4d / 29.9d (9/9 DA, Voting / Total Eligible)
≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12669.7d
Uptime Meets (9/9 DA) 30.0d (R) ≥5.0d - 5.1d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
32.8 Mbit/s – 96.0 Mbit/s (6 DA measured)
58.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 Meets (8/9 DA) 8/9 DA assigned Stable ≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12669.7d
Prereq: V2Dir Below (2/9 DA) 2/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Uptime Meets (9/9 DA) 30.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
32.8 Mbit/s – 96.0 Mbit/s (6 DA measured)
58.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 Meets (8/9 DA) 8/9 DA assigned Stable ≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12669.7d
Prereq: V2Dir Below (2/9 DA) 2/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.5% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 23.5d (9/9 DA above threshold)
Min/Max: 6.8d / 29.9d (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) 32.8 Mbit/s – 96.0 Mbit/s (6 DA measured)
58.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 Partial (2/9 DA) Port 80: Yes | Port 443: Yes (R) Allows ≥1 /8 on ports 80 AND 443 (≥5/9 DA)
MiddleOnly Restriction (by DA) Flagged (7/9 DA) 7/9 authorities assigned MiddleOnly Suspicious behavior, Sybil risk, or policy violation
BadExit Restriction (by DA) Flagged (5/9 DA) 5/9 authorities assigned BadExit Exit traffic manipulation, SSL stripping, or policy violation

(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
60.11 Mbit/s
Advertised Bandwidth
58.72 Mbit/s
Rate Limit
58.72 Mbit/s
Burst Limit
100.66 Mbit/s
Total Data
22 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
48.0 Mbit/s (median of 6 measurements)
Measured Min / Max
32.8 Mbit/s / 96.0 Mbit/s
Deviation
63.2 Mbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0033% of network (34th pctl) | Guard: N/A | Middle: 0.0096% (66th pctl) | Exit: N/A
History
Throughput and write/read, last 30 days

Uptime Metrics
Current Status
UP 1mo 24m 36s 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
4w 1d 23h ago (2026-10-21 10:00:00)
Last Seen
1h 45m 32s ago (2026-11-20 08:00:00)
Last Restarted
1mo 24m 36s ago (2026-10-21 09:20:56)
Last Changed Address
2026-10-21 10: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
none
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1
DFE69F153172111298D39BBBC6DF6D4F5F965EDB (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Platform
Linux — Tor 0.4.9.14 on Linux
Version
0.4.9.14 — 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: 
  20-23
  43
  53
  80-81
  88
  110
  143
  194
  220
  389
  443
  853
  873
  902-904
  993-995
  1194
  1723
  2082-2083
  2086-2087
  2095-2096
  3128
  3389
  5190
  5222-5223
  5900
  8000
  8008
  8080
  8443
  8888
  10000
IPv6 Exit Policy Summary
accept: 
  20-23
  43
  53
  80-81
  88
  110
  143
  194
  220
  389
  443
  853
  873
  902-904
  993-995
  1194
  1723
  2082-2083
  2086-2087
  2095-2096
  3128
  3389
  5190
  5222-5223
  5900
  8000
  8008
  8080
  8443
  8888
  10000
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 144.76.187.208:*
accept *:20-23
accept *:43
accept *:53
accept *:80-81
accept *:88
accept *:110
accept *:143
accept *:194
accept *:220
accept *:389
accept *:443
accept *:853
accept *:873
accept *:902-904
accept *:993
accept *:994
accept *:995
accept *:1194
accept *:1723
accept *:2082
accept *:2083
accept *:2086-2087
accept *:2095-2096
accept *:3128
accept *:3389
accept *:5190
accept *:5222-5223
accept *:5900
accept *:8000
accept *:8008
accept *:8080
accept *:8443
accept *:8888
accept *:10000
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 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)
E30CF7B3 Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 48.0 Mbit/s (M) | 816.0 Kbit/s 48.0 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 6.8d | 5d 6.8d | 3.9d 30.0d | 5.1d 2026-11-19 21:21:09 48.0 Mbit/s (M)
dannenberg (DE) Yes Yes No Yes Y Yes Yes Running, Valid, Fast, Stable, MiddleOnly 74.4 Mbit/s (M) | 816.0 Kbit/s 74.4 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 29.8d | 8d 29.8d | 8.2d 30.0d | 5.1d 2026-11-19 21:21:09 74.4 Mbit/s (M)
dizum (NL) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 58.7 Mbit/s (R) | 816.0 Kbit/s 58.7 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.8% | 98% 23.5d | 8d 21.5d | 6.8d 30.0d | 5.1d 2026-11-19 21:21:09 58.7 Mbit/s (R)
faravahar (US) Yes Yes No Yes Y Yes Yes Running, Valid, Fast, Stable, MiddleOnly, BadExit 58.7 Mbit/s (R) | 816.0 Kbit/s 58.7 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 21.7d | 8d 19.3d | 7.0d 30.0d | 5.1d 2026-11-19 21:21:09 58.7 Mbit/s (R)
gabelmoo (DE) Yes Yes No Yes Y Yes Yes Running, Valid, Fast, Stable, MiddleOnly, BadExit 96.0 Mbit/s (M) | 816.0 Kbit/s 96.0 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 29.9d | 8d 29.9d | 8.3d 30.0d | 5.1d 2026-11-19 21:21:09 96.0 Mbit/s (M)
longclaw (US) Yes Yes No Yes Y Yes N/T Running, Valid, Fast, Stable, MiddleOnly, BadExit 32.8 Mbit/s (M) | 816.0 Kbit/s 32.8 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 29.9d | 8d 29.9d | 9.1d 30.0d | 5.1d 2026-11-19 21:21:09 32.8 Mbit/s (M)
maatuska (SE) Yes Yes No Yes N Yes Yes Running, Valid, Fast, MiddleOnly 58.7 Mbit/s (R) | 816.0 Kbit/s 58.7 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 98.5% | 98% 13.9d | 8d 1.4d | 2.3d 30.0d | 5.1d 2026-11-19 21:21:09 58.7 Mbit/s (R)
moria1 (US) Yes Yes No Yes Y Yes Yes Running, Valid, Fast, Stable, MiddleOnly, BadExit 37.6 Mbit/s (M) | 8.4 Mbit/s 37.6 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 9.4d | 8d 29.9d | 12669.7d 30.0d | 5.0d 2026-11-19 21:21:09 37.6 Mbit/s (M)
tor26 (AT) Yes Yes No Yes Y Yes Yes Running, Valid, Fast, Stable, MiddleOnly, BadExit 59.2 Mbit/s (M) | 816.0 Kbit/s 59.2 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 29.9d | 8d 29.9d | 8.2d 30.0d | 5.1d 2026-11-19 21:21:09 59.2 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.