View Relay "eclipse32"
Fingerprint: 0ED62BCD8A7DC5DEB0D5C5CE7D1C33B6C2480041 |
Family: 21 relays
|
freiraum_TK AT protonmail DOT ch |
AS214481
|
Netherlands
|
Linux
- Consensus
- Not In Consensus (1/9 Directory Auths, need 5)
- BW Verified
- 1/6 BW Auths Measured 78 Kbit/s Median
- Stability
- Not Overloaded | DOWN 21h 46m 5s ago | UP 69% (1M)
- Reachability
- IPv4: 1/9 | v6: 1/9 (Directory Auths)
- BW Weight
- 0.01% of Network | 62 Mbit/s Observed By Relay
- Version
- 0.4.9.6 Recommended
Issues Detected:
-
Not in consensus
: Only 1/9 authorities voted for this relay (need 5)
Suggestion: Verify your relay is reachable from multiple geographic locations. Check firewall rules allow incoming connections on your ORPort from all directory authority IP addresses. -
IPv4 reachability issues
: Only 1/9 authorities can reach this relay
Suggestion: Authorities that cannot reach you: dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1, tor26. Check: 1) Firewall allows incoming TCP on ORPort, 2) No ISP-level blocking, 3) Tor is running and listening. Use 'nc -zv your-ip your-orport' from external hosts to test. -
Guard: WFU below threshold
: Weighted Fractional Uptime 84.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. -
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 becauseDirCache 0is set in torrc.
Suggestion: RemoveDirCache 0from torrc (DirCache is enabled by default in Tor ≥0.3.3). Restart Tor and verify the descriptor includestunnelled-dir-server. You can check with:grep tunnelled-dir-server /var/lib/tor/cached-descriptors -
HSDir: WFU below threshold
: WFU 84.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. -
Low bandwidth authority measurements
: Only 1/6 bandwidth authorities measured this relay. Minimum 3 measurements needed for accurate consensus weight.
Suggestion: Low measurement count can indicate connectivity issues. Check: 1) Relay is reachable from multiple geographic locations, 2) ORPort accepts connections from bandwidth scanners, 3) RelayBandwidthRate in torrc matches actual capacity. New relays may take 1-2 days to be measured by all authorities.
Addresses
- OR Address
-
31.59.129.146:9001
[2a0f:85c1:840:883b::1]:9001
Reachability (Directory Authorities)
- IPv4
- 1/9
- IPv6
- 1/9
Location
- Country
-
Netherlands
- Interactive Map
- View in RouteFluxMap
Eligible Flags (0):
Running: 1/9 | Valid: 1/9 | V2Dir: 1/9 | Fast: 1/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 | Below (1/9 DA) | 1/9 authorities reached relay | ≥5/9 DA ORPort reachable |
| IPv6 Reachability | Partial (1/9 DA) | 1/9 tested authorities reached relay | ≥5/9 tested (majority) (≥5/9 DA) | |
| Valid | Descriptor | Partial (1/9 DA) | 1/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 | Meets (9/9 DA) | 62.2 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 (0/9 DA) | Median: 21.3d (0/9 DA above threshold) | ≥37.3d - 61.6d (varies) (≥5/9 DA) |
| Uptime | Meets (9/9 DA) | 22.6d (R) | ≥8.3d - 9.5d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Below (1/9 DA) | 1/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 | ≥37.3d - 61.6d (varies) (≥5/9 DA) | |
| 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: 84.7% (0/9 DA above threshold) | ≥98.0% (≥5/9 DA) | |
| Time Known | Below (1/9 DA) | Median: 25.2d (1/9 DA above threshold) | ≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.9d |
|
| Guard | Prereq: Fast | Below (1/9 DA) | 1/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 | ≥37.3d - 61.6d (varies) (≥5/9 DA) | |
| 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: 84.7% (0/9 DA above threshold) | ≥98% (≥5/9 DA) | |
| Time Known | Meets (1/9 DA) | Median: 25.2d (1/9 DA above threshold) | ≥8 days (≥5/9 DA) | |
| Bandwidth | Meets (9/9 DA) | 62.2 Mbit/s (R) | ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-312.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-04-18 19:15:08).
Capacity (Relay Reported)
- Observed Bandwidth
- 62.16 Mbit/s
- Advertised Bandwidth
- 62.16 Mbit/s
- Rate Limit
- 62.91 Mbit/s
- Burst Limit
- 83.89 Mbit/s
- Total Data
-
300 TB
(5 years)
1mo: 17 TB | 6mo: 101 TB | 1y: 196 TB | 5y: 300 TB
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-04-18 19:15:08
- Measured By
-
1/6
Bandwidth Authorities
Not measured by: gabelmoo, longclaw, maatuska, moria1, tor26 - Median Measurement
- 78.4 Kbit/s
- Min / Max
- 78.4 Kbit/s / 78.4 Kbit/s
Network Participation:
Consensus Weight:
0.0051% of network
(50th pctl)
|
Guard:
N/A |
Middle:
N/A |
Exit:
N/A
Uptime Metrics
- Current Status
- DOWN 21h 46m 5s ago
- Overall Uptime (1M/6M/1Y/5Y)
- 69.7%/81.5%/78.4%/82.6%
- Flag Uptime (1M/6M/1Y/5Y)
- 65.7%/80.8%/77.7%/82.1%
- Hibernating
- No
Timestamps
- First Seen
- 1w 4d 20h ago (2026-04-06 23:00:00)
- Last Seen
- 21h 46m 5s ago (2026-04-17 22:00:00)
- Last Restarted
- 3w 1d 14h ago (2026-03-27 05:32:46)
- Last Changed Address
- 2026-04-06 23:00:00
Overload Status:
Not Overloaded — No overload conditions reported.
Operator Identity
Source: AROI Validation API — 2026-04-18 12:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- freiraum_TK AT protonmail DOT ch
Family Configuration
- Family Support
- MyFamily Only (21) — Legacy only. Consider migrating to Happy Families. | View Full Family (21)
Happy Families (family-cert)
- Effective Members: 0
- none
MyFamily (legacy declarations)
- Effective Members: 21
0ED62BCD8A7DC5DEB0D5C5CE7D1C33B6C2480041 (this relay) 18D20E4FC4FEF79E9A94C536ED6467F7D3011E0C 2400279341C3802A8810D3E806B4ACA1C9EB1491 28A9CEC4C740F08B95DE922BE9BD86B81E76D0FE 2B23DEA9443219E1F9783C6DB5586D09D02A2677 44689828532CCEB9B598E1DABDBE28BD815517EB 4BD5349190008EBF00CAAAC5DF5067FE26847F47 5485531D473962D3C577A828FC5F2C3C19CCAF6B 5E411311DB3B7130A729891E1946EA911BA06E27 65F86FD8B92C3AC01887D86B2171E657D5C19F79 69B53A5AE5025DA8947F7C32F69CA90375ED2A4E 6F87B99ABF7E00837A90C2E7AA38A4A6D85FA91F 83B33A296504D303FB481C3932949188F4AC21D0 965A86DC8650843DC7665792552F18E62FE952EF 9EE639870FDE7D40A60F7E1C9B912977D1AED712 A4DE3FC1ACEC3767F5C4049BCEF57317E7B0583C B86F28E63E7972C533D1F20CB94F0F0AAFF3DC5B E1C428EA28B7E8CADBD4B514FC55388FE80231C4 E861C61D4D48763FBD320645D872296D3F1B7BF3 E90F52D29788BD86B5C057EE23383467920FC175 F886436A34497BB0A3DE235B2EC3B5358E87C3B6
- Alleged Members: 3
-
(they don't list you back)
517A936F70849A15C1399E1FB060076C4EF87E84 6EF66E8E6E2E07FEB96AD89C058A39CA0E5842CB EC9C4CDB403204731122C9D3FA44DFAE667DC82D
- Indirect Members: 0
- none
DNS Health
Not an exit relay — DNS health testing does not apply.Last fetch was at Sat, 18 Apr 2026 19:46:04 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-04-18 19:15:08).
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 | No | — | Y | Yes | Yes | Running, Valid, Fast, Stable | 62.2 Mbit/s | 816.0 Kbit/s | 62.2 Mbit/s | 200.0 Mbit/s OR 16.0 Mbit/s | 84.7% | 98% | 25.2d | 8d | 21.3d | 62.2d | 22.6d | 8.3d | 84.7% | 98.0% | 25.2d | 1.0d | 2026-04-16 19:04:06 | 78.4 Kbit/s |
| dannenberg (DE) | No | — | — | — | N | No | — | — | — | — | — | — | — | — | — | — | — | — |
| dizum (NL) | No | — | — | — | N | No | — | — | — | — | — | — | — | — | — | — | — | — |
| faravahar (US) | No | — | — | — | N | No | — | — | — | — | — | — | — | — | — | — | — | — |
| gabelmoo (DE) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — | — | — |
| longclaw (US) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — | — | — |
| maatuska (SE) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — | — | — |
| moria1 (US) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — | — | — |
| tor26 (AT) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — | — | — |
— = 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.
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.
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.