View Relay "Hermes"

Fingerprint: 0ED4CA8A8E6CE2D28D6D23B20815AE3982646FCB | Family: 5 relays | contact(at)greektor(dot)net | AS53667 | Luxembourg | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Fast, Exit (5)
DNS Health
Healthy (16.1s, 70th percentile) (via exitdnshealth.1aeo.com)
BW Verified
7/8 BW Auths Measured 440 Kbit/s Median
Stability
Overloaded | UP 6d 17h 38m ago | UP 50% (1M)
Reachability
IPv4: 9/9 | v6: 8/8 (Directory Auths)
First Seen
5y 1w 2d ago
BW Weight
0.03% of Network | 229 Mbit/s Observed By Relay
Version
0.4.9.11 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: WFU below threshold : Weighted Fractional Uptime 97.7% 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 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: WFU below threshold : WFU 97.7% below 98% required for HSDir
    Suggestion: HSDir requires ≥98% WFU, Stable flag, and Time Known ≥25 hours (or ~10 days for moria1). Improve uptime consistency.
  • 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-07-23 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
tor-exit-hermes.greektor.net
104.244.72.115:443
[2605:6400:30:f858:2704:73e1:7085:12ef]:443
Exit Address
104.244.72.115
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
Location
Country
Luxembourg Luxembourg
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS53667
AS Name
FranTech Solutions (BGP.tools)
AS Rarity
Emerging (score: 1/5, 1.61% consensus weight, 74 operators)

Flags and Eligibility

Current Flags (5): Running, Valid, V2Dir, Fast, Exit
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 1/9 | HSDir: 0/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
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 Meets (9/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 230.0 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 Below (1/9 DA) Median: 4.3d (1/9 DA above threshold)
Min/Max: 1.1d / 11684.2d (9/9 DA, Voting / Total Eligible)		 ≥8.1d - 12.5d (varies) (≥5/9 DA)
[Stricter] moria1: ≥9049.6d
Uptime Below (0/9 DA) 6.7d (R) ≥7.3d - 7.5d (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 Below (1/9 DA) 1/9 DA assigned Stable ≥8.1d - 12.5d (varies) (≥5/9 DA)
[Stricter] moria1: ≥9049.6d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (2/9 DA) Median: 97.8% (2/9 DA above threshold)
Min/Max: 97.2% / 98.6% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 10.1d (6/9 DA above threshold)
Min/Max: 4.0d / 10.3d (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 Below (1/9 DA) 1/9 DA assigned Stable ≥8.1d - 12.5d (varies) (≥5/9 DA)
[Stricter] moria1: ≥9049.6d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (2/9 DA) Median: 97.8% (2/9 DA above threshold)
Min/Max: 97.2% / 98.6% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Meets (6/9 DA) Median: 10.1d (6/9 DA above threshold)
Min/Max: 4.0d / 10.3d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 230.0 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-304.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-07-25 12:45:10).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
229.97 Mbit/s
Advertised Bandwidth
229.97 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
2.2 PB (5 years)
1mo: 9.6 TB | 6mo: 44 TB | 1y: 590 TB | 5y: 2.2 PB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-07-25 12:45:10

Measured By
7/8 Bandwidth Authorities
Not measured by: bastet
Median Measurement
440.0 Kbit/s
Min / Max
80.0 Kbit/s / 600.0 Kbit/s
Deviation
520.0 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0271% of network (91th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0813% (92th pctl)

Uptime and Stability

Uptime Metrics
Current Status
UP 6d 17h 38m ago
Overall Uptime (1M/6M/1Y/5Y)
50.4%/12.8%/52.5%/86.3%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (50.4%/12.8%/52.5%/86.3%)
Hibernating
No
Timestamps
First Seen
5y 1w 2d ago (2021-07-17 00:00:00)
Last Seen
1h 45m 50s ago (2026-07-25 11:00:00)
Last Restarted
6d 17h 38m ago (2026-07-18 19:07:21)
Last Changed Address
2026-07-10 00:00:00
[Warning] OVERLOADED — General overload at 2026-07-23 22:00 UTC
General Overload (from /details)
Status
Reported
When
2026-07-23 22:00 UTC (1 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-07-25 05:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
contact(at)greektor(dot)net
Family Configuration
Family Support
MyFamily Only (5) — Legacy only. Consider migrating to Happy Families. | View Full Family (5)
Happy Families (family-cert)
Effective Members: 0
none

Software and Version

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

Exit Health & Policy

DNS Health
Status
Healthy (avg. 16.1s, 70th percentile)
Query Domain
f58c863e096c4378aa28509133b32d36.0ed4ca8a.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
4/4 instances succeeded
First Hop
UnredactedLibra (US) 16A8740ECC9785A650876F26A97425C6D8912625
Exit Address Used
104.244.72.115
Per-Instance Results
Cross Validation Attempt 1: Success, 17.5s (cv1_w1)
Cross Validation Attempt 2: Success, 18.2s (cv2_w1)
Cross Validation Attempt 3: Success, 12.0s (cv3_w1)
Cross Validation Attempt 4: Success, 16.6s (cv4_w1)
Tested: 2026-07-25 07:05:54 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
reject: 
  22
  25
  465
  587
IPv6 Exit Policy Summary
reject: 
  22
  25
  465
  587
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 104.244.72.115:*
reject *:22
reject *:25
reject *:465
reject *:587
accept *:*

Last fetch was at Sat, 25 Jul 2026 12:45:49 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-07-25 12:45:10).

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 (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 Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 230.0 Mbit/s | 816.0 Kbit/s 230.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 97.7% | 98% 10.1d | 8d 4.3d | 16.5d 6.7d | 7.3d 97.7% | 98.0% 10.1d | 1.0d 2026-07-25 09:20:04 80.0 Kbit/s
dannenberg (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 230.0 Mbit/s | 816.0 Kbit/s 230.0 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 97.8% | 98% 10.3d | 8d 4.3d | 8.1d 6.7d | 7.4d 97.8% | 98.0% 10.3d | 1.0d 2026-07-25 09:20:04 584.0 Kbit/s
dizum (NL) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Exit 230.0 Mbit/s | 816.0 Kbit/s 230.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 97.8% | 98% 10.1d | 8d 4.3d | 11.7d 6.7d | 7.4d 97.8% | 98.0% 10.1d | 1.0d 2026-07-25 09:20:04 80.0 Kbit/s
faravahar (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 230.0 Mbit/s | 816.0 Kbit/s 230.0 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 97.8% | 98% 10.3d | 8d 4.3d | 11.9d 6.7d | 7.7d 97.8% | 98.0% 10.3d | 1.0d 2026-07-25 09:20:04 600.0 Kbit/s
gabelmoo (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 230.0 Mbit/s | 816.0 Kbit/s 230.0 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 98.6% | 98% 4.0d | 7d 1.1d | 12.2d 6.7d | 7.4d 98.6% | 98.0% 4.0d | 1.0d 2026-07-25 09:20:04 440.0 Kbit/s
longclaw (US) Yes Yes Yes — Y Yes — Running, Valid, V2Dir, Fast, Exit 230.0 Mbit/s | 816.0 Kbit/s 230.0 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 98.5% | 98% 4.4d | 8d 2.3d | 23.1d 6.7d | 7.9d 98.5% | 98.0% 4.4d | 1.0d 2026-07-25 09:20:04 472.0 Kbit/s
maatuska (SE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 230.0 Mbit/s | 816.0 Kbit/s 230.0 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 97.8% | 98% 10.3d | 8d 4.3d | 12.5d 6.7d | 7.9d 97.8% | 98.0% 10.3d | 1.0d 2026-07-25 09:20:04 504.0 Kbit/s
moria1 (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, Exit 230.0 Mbit/s | 8.4 Mbit/s 230.0 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 97.2% | 98% 7.6d | 8d 11684.2d | 9049.6d 6.7d | 7.5d 97.2% | 98.0% 7.6d | 9.8d 2026-07-25 09:20:04 200.0 Kbit/s
tor26 (AT) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 230.0 Mbit/s | 816.0 Kbit/s 230.0 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 97.6% | 98% 10.3d | 8d 4.3d | 16.7d 6.7d | 7.5d 97.6% | 98.0% 10.3d | 1.0d 2026-07-25 09:20:04 176.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.