Tor Relays :: EhrenRelay

View Relay "EhrenRelay"

Fingerprint: `C683052FD8BACF5230103F794E9694BEED1ED0B4` | Operator: habedieeh.re v2 (1 relay) ⚠ Misconfigured | Family: 1 relay | email:33dayg3k[]4wrd.cc... | AS47172 | Netherlands | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, V2Dir, Fast, Stable, HSDir, Guard (7)
BW Verified: 6/7 BW Auths Measured 120 Kbit/s Median
Stability: Overloaded | UP 1w 6d 9h ago | UP 100% (1M)

Reachability: IPv4: 9/9 (Directory Auths)
First Seen: 1y 9mo 1w ago
BW Weight: 0.01% of Network | 103 Mbit/s Observed By Relay
Version: 0.4.9.9 Recommended

Issues Detected:

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.
General Overload Active : Relay reported general overload at 2026-06-12 22:00 UTC. This indicates OOM killer invocation, onionskin queue saturation, or TCP port exhaustion.
Suggestion: Check CPU/memory with htop. Review logs for "out of memory" or "onionskins" warnings. Consider increasing MaxMemInQueues in torrc. Verify TCP ports available.

Connectivity and Location

Addresses

OR Address: relay.habedieeh.re
37.218.245.79:443

Reachability (Directory Authorities)

IPv4: 9/9

Location

Country: Netherlands
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS47172
AS Name: Greenhost BV (BGP.tools)
AS Rarity: Epic (score: 3/5, 0.07% consensus weight, 4 operators)

Flags and Eligibility

Current Flags (7): Running, Valid, V2Dir, Fast, Stable, HSDir, Guard

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	Meets (9/9 DA)	103.9 Mbit/s (R)	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s
Stable	MTBF	Partial (8/9 DA)	Median: 124.7d (8/9 DA above threshold) Min/Max: 35.7d / 125.1d (9/9 DA, Voting / Total Eligible)	≥30.8d - 54.8d (varies) (≥5/9 DA) [Stricter] moria1: ≥297.6d
Stable	Uptime	Meets (9/9 DA)	13.4d (R)	≥8.7d - 8.9d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (9/9 DA)	9/9 DA assigned Fast	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Meets (9/9 DA)	9/9 DA assigned Stable	≥30.8d - 54.8d (varies) (≥5/9 DA) [Stricter] moria1: ≥297.6d
	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% (7/9 DA) Min/Med/Max: 100.0% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Meets (8/9 DA)	Median: 121.4d (9/9 DA above threshold) Min/Max: 9.5d / 125.1d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.8d
Guard	Prereq: Fast	Meets (9/9 DA)	9/9 DA assigned Fast	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Meets (9/9 DA)	9/9 DA assigned Stable	≥30.8d - 54.8d (varies) (≥5/9 DA) [Stricter] moria1: ≥297.6d
	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% (7/9 DA) Min/Med/Max: 100.0% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 121.4d (9/9 DA above threshold) Min/Max: 9.5d / 125.1d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Meets (9/9 DA)	103.9 Mbit/s (R)	≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-320.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-06-15 13:15:07).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 103.85 Mbit/s
Advertised Bandwidth: 92.27 Mbit/s
Rate Limit: 92.27 Mbit/s
Burst Limit: 251.66 Mbit/s
Total Data: 1.0 PB (5 years)
1mo: 40 TB | 6mo: 212 TB | 1y: 393 TB | 5y: 1.0 PB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-06-15 13:15:07

Measured By: 6/7 Bandwidth Authorities
Not measured by: dannenberg
Median Measurement: 120.0 Kbit/s
Min / Max: 80.0 Kbit/s / 168.0 Kbit/s
Deviation: 88.0 Kbit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0079% of network (58th pctl) | Guard: 0.0133% (51th pctl) | Middle: 0.0103% (63th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics

Current Status: UP 1w 6d 9h ago
Overall Uptime (1M/6M/1Y/5Y): 100.0%/99.7%/99.8%/96.1%
Flag Uptime (1M/6M/1Y/5Y): —/—/95.5%/90.7%
Hibernating: No

Timestamps

First Seen: 1y 9mo 1w ago (2024-09-09 00:00:00)
Last Seen: 1h 46m 39s ago (2026-06-15 12:00:00)
Last Restarted: 1w 6d 9h ago (2026-06-02 04:29:09)
Last Changed Address: 2026-04-06 23:00:00

[Warning] OVERLOADED — General overload at 2026-06-12 22:00 UTC

General Overload (from /details)

Status: Reported
When: 2026-06-12 22:00 UTC (2 days ago)

OOM killer, onionskin queue saturation, or TCP port exhaustion. Flag remains 72h after last event (Tor spec 328).

File Descriptor Exhaustion (from /bandwidth)

Status: Not Reported

Rate Limits (from /bandwidth)

No rate limit data from /bandwidth endpoint.

Recommendations

Check CPU/memory: htop
Review MaxMemInQueues in torrc

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-06-15 06:00 UTC

AROI Domain (?): habedieeh.re
Operator Validation: Unvalidated
This Relay: Unvalidated
Error: URI-RSA: HTTP error 404 for www.habedieeh.re at URL: https://www.habedieeh.re/.well-known/tor-relay/rsa-fingerprint.txt
Contact: email:33dayg3k[]4wrd.cc url:https://www.habedieeh.re proof:uri-rsa pgp:4F306C4A27371138540674F288D4301D96F75504 xmr:48irQEGKU9HYpXkjMrbffKgcSWg4s43ExJdYtCB8CcNN3jeHqX54NxVBqym2pinRZPESagVbmjFa5Dv3Kvu5dfsQ9u76v12 ciissversion:2

Family Configuration

Family Support: None — No family membership configured

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Member: 1

C683052FD8BACF5230103F794E9694BEED1ED0B4 (this relay)

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

Platform: Linux — Tor 0.4.9.9 on Linux
Version: 0.4.9.9 — Recommended
Version Status: Recommended

Exit Health & Policy

DNS Health

Not an exit relay — DNS health testing does not apply.

IPv4 Exit Policy Summary

reject: 
  1-65535

Full Exit Policy

reject *:*

Last fetch was at Mon, 15 Jun 2026 13:46:37 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-06-15 13:15:07).

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	Flags	Fast (Relay\|T)	Guard BW (Relay\|Threshold)	Guard WFU (M\|T)	Guard TK (M\|T)	Stable MTBF (M\|T)	Stable Uptime (Relay\|T)	HSDir WFU (M\|T)	HSDir TK (M\|T)	Desc Published	Cons Wt (Authority)
bastet (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard	103.9 Mbit/s \| 816.0 Kbit/s	103.9 Mbit/s \| 248.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	125.1d \| 8d	125.1d \| 57.4d	13.4d \| 9.6d	100.0% \| 98.0%	125.1d \| 1.0d	2026-06-14 22:31:35	120.0 Kbit/s
dannenberg (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard	103.9 Mbit/s \| 816.0 Kbit/s	103.9 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	96.7d \| 8d	96.7d \| 30.8d	13.4d \| 8.7d	100.0% \| 98.0%	96.7d \| 1.0d	2026-06-14 22:31:35	80.0 Kbit/s
dizum (NL)	Yes	Yes	No	—	N	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard	103.9 Mbit/s \| 816.0 Kbit/s	103.9 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	36.5d \| 8d	35.7d \| 34.4d	13.4d \| 8.9d	100.0% \| 98.0%	36.5d \| 1.0d	2026-06-14 22:31:35	80.0 Kbit/s
faravahar (US)	Yes	Yes	No	—	N	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard	103.9 Mbit/s \| 816.0 Kbit/s	103.9 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	125.1d \| 8d	125.1d \| 52.6d	13.4d \| 8.9d	100.0% \| 98.0%	125.1d \| 1.0d	2026-06-14 22:31:35	80.0 Kbit/s
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard	103.9 Mbit/s \| 816.0 Kbit/s	103.9 Mbit/s \| 304.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	125.1d \| 8d	125.1d \| 55.0d	13.4d \| 9.0d	100.0% \| 98.0%	125.1d \| 1.0d	2026-06-14 22:31:35	128.0 Kbit/s
longclaw (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard	103.9 Mbit/s \| 816.0 Kbit/s	103.9 Mbit/s \| 240.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	121.4d \| 8d	121.4d \| 60.4d	13.4d \| 8.9d	100.0% \| 98.0%	121.4d \| 1.0d	2026-06-14 22:31:35	136.0 Kbit/s
maatuska (SE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard	103.9 Mbit/s \| 816.0 Kbit/s	103.9 Mbit/s \| 320.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	55.9d \| 8d	55.6d \| 31.2d	13.4d \| 8.9d	100.0% \| 98.0%	55.9d \| 1.0d	2026-06-14 22:31:35	168.0 Kbit/s
moria1 (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast, Stable, Guard	103.9 Mbit/s \| 8.4 Mbit/s	103.9 Mbit/s \| 240.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	9.5d \| 8d	125.1d \| 297.6d	13.4d \| 9.1d	100.0% \| 98.0%	9.5d \| 9.8d	2026-06-14 22:31:35	120.0 Kbit/s
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard	103.9 Mbit/s \| 816.0 Kbit/s	103.9 Mbit/s \| 312.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	124.7d \| 8d	124.7d \| 54.8d	13.4d \| 9.0d	100.0% \| 98.0%	124.7d \| 1.0d	2026-06-14 22:31:35	128.0 Kbit/s

— = not tested/available • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known

Bandwidth Values Explained:
Relay Reported = Your relay's self-reported bandwidth from its descriptor (observed_bandwidth). Used for flag eligibility (Guard, Fast).
Authority Measured = Bandwidth measured by authority's sbws scanner. Used for consensus weight (path selection probability).
Why different? Authorities verify your reported bandwidth independently. 6 of 9 authorities run bandwidth scanners; 3 use relay-reported values directly.

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.