View Relay "iDIDedittheconfig"

Fingerprint: 0858C3E9183DC93C3E31026220BA6BA92273E7C4 | Family: 1 relay | AS215730 | Germany | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, MiddleOnly, BadExit (4)
BW Verified
3/7 BW Auths Measured 8 Kbit/s Median
Stability
Not Overloaded | UP 4h 36m 50s ago
Reachability
IPv4: 9/9 | v6: 8/8 (Directory Auths)
First Seen
3h 45m 33s ago
BW Weight
0.00% of Network | 0 Kbit/s Observed By Relay
Version
0.4.9.10 Not Recommended
Issues Detected:
  • Not getting the Fast flag : Only 0/9 authorities vote Fast (5 needed). dannenberg, gabelmoo and tor26 measured this relay at 8.0 Kbit/s, below the Fast threshold (816.0 Kbit/s). dizum, longclaw and maatuska used the relay-reported unknown, below the Fast threshold (816.0 Kbit/s). bastet and moria1 counted this relay as 0 (no measurement, relay-reported bandwidth ignored). faravahar judged it by bandwidth not shown in the votes. Its consensus weight, the median of the 3 bandwidth-scanner measurements, is 8.0 Kbit/s.
    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. A low measurement means the scanners see your relay underperforming compared with other relays that report a similar speed. Clients only build circuits through Fast relays, so a relay near the threshold can gain and lose most of its traffic from one hourly consensus to the next.
  • 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 – 272.0 Mbit/s). dannenberg, gabelmoo and tor26 measured this relay at 8.0 Kbit/s. dizum, longclaw and maatuska used the relay-reported unknown. bastet and moria1 counted this relay as 0 (no measurement, relay-reported bandwidth ignored).
    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 : Weighted Fractional Uptime 0.2% is below 98% requirement
    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 : Uptime or MTBF below network median for most authorities
    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 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
  • 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.10 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.
Notes:

Connectivity and Location

Addresses
OR Address
128197.h2.nexus
94.159.98.53:9001
[2a0b:4142:218::2]: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
AS215730
AS Name
H2NEXUS CLOUD SERVICES - FZCO (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 2 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, MiddleOnly, BadExit
Eligible Flags (3): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 0/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 Below (0/9 DA) 8.0 Kbit/s (3 DA measured)
0 bit/s (3 DA relay-reported)
0 bit/s (2 DA unmeasured, counted as 0)
faravahar: not published		 ≥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: 0.2d (0/9 DA above threshold)
Min/Max: 0.2d / 5.3d (9/9 DA, Voting / Total Eligible)		 ≥6.2d - 9.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10374.1d
Uptime Below (0/9 DA) 0.2d (R) ≥6.1d - 6.1d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (0/9 DA) 0/9 DA assigned Fast
8.0 Kbit/s (3 DA measured)
0 bit/s (3 DA relay-reported)
0 bit/s (2 DA unmeasured, counted as 0)
faravahar: not published		 ≥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 ≥6.2d - 9.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10374.1d
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) 0.2d (R) ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA)
[Stricter] moria1: ≥98% WFU and ≥10.0d Time Known
Guard Prereq: Fast Below (0/9 DA) 0/9 DA assigned Fast
8.0 Kbit/s (3 DA measured)
0 bit/s (3 DA relay-reported)
0 bit/s (2 DA unmeasured, counted as 0)
faravahar: not published		 ≥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 ≥6.2d - 9.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10374.1d
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: 0.2% (0/9 DA above threshold)
Min/Max: 0.2% / 1.6% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 81.8d (9/9 DA above threshold)
Min/Max: 9.8d / 81.9d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 8.0 Kbit/s (3 DA measured)
0 bit/s (3 DA relay-reported)
0 bit/s (2 DA unmeasured, counted as 0)
faravahar: not published		 ≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-272.0 Mbit/s) (≥5/9 DA)
Exit Exit Policy Partial (0/9 DA) (only port 80) Port 80: Yes | Port 443: Yes (R) Allows ≥1 /8 on ports 80 AND 443 (≥5/9 DA)
MiddleOnly Restriction (by DA) Flagged (9/9 DA) 9/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-10-18 09:45:05).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
0.00 Kbit/s
Advertised Bandwidth
Unknown
Rate Limit
52.43 Mbit/s
Burst Limit
131.07 Mbit/s
Total Data
148 TB (1 year)
1mo: 22 TB | 6mo: 112 TB | 1y: 148 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-10-18 09:45:05

Measured By
3/7 Bandwidth Authorities
Not measured by: bastet, faravahar, longclaw, moria1
Consensus Weight
8.0 Kbit/s (median of 3 measurements)
Measured Min / Max
8.0 Kbit/s / 8.0 Kbit/s
Network Participation: Consensus Weight: 0.0000% of network (0th pctl) | Guard: N/A | Middle: 0.0000% (0th pctl) | Exit: N/A
History
Throughput and write/read, last year Throughput and write/read, last 6 months
6M 1Y

Uptime and Stability

Uptime Metrics
Current Status
UP 4h 36m 50s ago
Overall Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
N/A
Hibernating
No
Timestamps
First Seen
3h 45m 33s ago (2026-10-18 06:00:00)
Last Seen
1h 45m 33s ago (2026-10-18 08:00:00)
Last Restarted
4h 36m 50s ago (2026-10-18 05:08:43)
Last Changed Address
2026-10-18 06:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-10-18 02: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 
0858C3E9183DC93C3E31026220BA6BA92273E7C4 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

Platform
Linux — Tor 0.4.9.10 on Linux
Version
0.4.9.10 — Not Recommended
Version Status
Obsolete — Update urgently. See torproject.org/download

Exit Health & Policy

DNS Health
Not an exit relay — DNS health testing does not apply.
IPv4 Exit Policy Summary
reject: 
  22
  25
  119
  135-139
  445
  563
  1214
  4661-4666
  6346-6429
  6699
  6881-6999
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 94.159.98.53:*
reject *:22
reject *:25
reject *:119
reject *:135-139
reject *:445
reject *:563
reject *:1214
reject *:4661-4666
reject *:6346-6429
reject *:6699
reject *:6881-6999
accept *:*

Last fetch was at Sun, 18 Oct 2026 09:45:32 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-10-18 09:45:05).

Per-Authority Details

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 Yes Y Yes Yes Running, Valid, MiddleOnly 0 bit/s (U) | 816.0 Kbit/s 0 bit/s (U) | 184.0 Mbit/s OR 16.8 Mbit/s 0.2% | 98% 81.9d | 8d 0.2d | 9.0d 0.2d | 6.1d 2026-10-18 05:08:56 —
dannenberg (DE) Yes Yes No Yes Y Yes Yes Running, Valid, MiddleOnly 8.0 Kbit/s (M) | 816.0 Kbit/s 8.0 Kbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s 0.2% | 98% 81.7d | 8d 0.2d | 6.2d 0.2d | 6.1d 2026-10-18 05:08:56 8.0 Kbit/s (M)
dizum (NL) Yes Yes No Yes N Yes Yes Running, Valid, MiddleOnly 0 bit/s (R) | 816.0 Kbit/s 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 0.2% | 98% 81.6d | 8d 0.2d | 9.0d 0.2d | 6.1d 2026-10-18 05:08:56 —
faravahar (US) Yes Yes No Yes Y Yes Yes Running, Valid, MiddleOnly, BadExit not published | 816.0 Kbit/s not published | 264.0 Mbit/s OR 16.8 Mbit/s 0.2% | 98% 81.8d | 8d 0.2d | 9.5d 0.2d | 6.1d 2026-10-18 05:08:56 —
gabelmoo (DE) Yes Yes No Yes Y Yes Yes Running, Valid, MiddleOnly, BadExit 8.0 Kbit/s (M) | 816.0 Kbit/s 8.0 Kbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 0.2% | 98% 81.9d | 8d 0.2d | 9.0d 0.2d | 6.1d 2026-10-18 05:08:56 8.0 Kbit/s (M)
longclaw (US) Yes Yes No Yes Y Yes — Running, Valid, MiddleOnly, BadExit 0 bit/s (R) | 816.0 Kbit/s 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 0.2% | 98% 81.9d | 8d 0.2d | 9.2d 0.2d | 6.1d 2026-10-18 05:08:56 —
maatuska (SE) Yes Yes No Yes N Yes Yes Running, Valid, MiddleOnly 0 bit/s (R) | 816.0 Kbit/s 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 0.2% | 98% 77.6d | 8d 0.2d | 8.8d 0.2d | 6.1d 2026-10-18 05:08:56 —
moria1 (US) Yes Yes No Yes Y Yes Yes Running, Valid, Stable, MiddleOnly, BadExit 0 bit/s (U) | 8.4 Mbit/s 0 bit/s (U) | 192.0 Mbit/s OR 16.8 Mbit/s 1.6% | 98% 9.8d | 8d 5.3d | 10374.1d 0.2d | 6.1d 2026-10-18 05:08:56 —
tor26 (AT) Yes Yes No Yes Y Yes Yes Running, Valid, MiddleOnly, BadExit 8.0 Kbit/s (M) | 816.0 Kbit/s 8.0 Kbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s 0.2% | 98% 81.8d | 8d 0.2d | 9.2d 0.2d | 6.1d 2026-10-18 05:08:56 8.0 Kbit/s (M)

— = not tested/available • 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.