View Relay "HappyToServeYou09"
Fingerprint: 4EA10A7A7F5F3C16DB3269426B178C780BABCB37 |
Family: 9 relays
|
torcontactemail AT proton.me |
AS36352
|
United States of America
|
Linux
- Consensus
- Not In Consensus (1/10 Directory Auths, need 6)
- BW Verified
- 0/8 BW Auths Measured 160 Kbit/s Median
- Stability
- Not Overloaded | DOWN 3d 5h 45m ago | UP 79% (1M)
- Reachability
- IPv4: 1/10 | v6: None configured(Directory Auths)
- BW Weight
- 0.00% of Network | 28 Mbit/s Observed By Relay
- Version
- 0.4.9.16 Recommended
-
Not in consensus
: Only 1/10 authorities voted for this relay (need 6)
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/10 authorities can reach this relay
Suggestion: Authorities that cannot reach you: E30CF7B3, 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: bandwidth below threshold
: 1/10 authorities credit this relay with enough bandwidth for Guard (6 needed): at least 16.8 Mbit/s (AuthDirGuardBWGuarantee) or a place in their top 25% (80.0 Mbit/s).
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
: 1/10 authorities meet guard-wfu (≥98%; 6 needed).
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. -
Guard: Time Known below threshold
: 1/10 authorities meet guard-tk (≥37 minutes 34 seconds; 6 needed).
Suggestion: Time Known tracks how long authorities have observed your relay. This resets if: 1) Identity key changes, 2) Long downtime makes authorities forget you. Just keep running stably. -
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 -
Low bandwidth authority measurements
: Only 0/8 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
-
23-94-73-74-host.colocrossing.com
23.94.73.74:9001
Reachability (Directory Authorities)
- IPv4
- 1/10
- IPv6
- None configured
Location
- Country
-
United States of America
- Interactive Map
- View in RouteFluxMap
Eligibility Flag Vote Details
| Flag | Metric | Status | Relay Value | Threshold Required |
|---|---|---|---|---|
| Running | IPv4 Reachability | Below (1/10 DA) | 1/10 authorities reached relay | ≥6/10 DA ORPort reachable |
| Valid | Descriptor | Partial (1/10 DA) | 1/10 authorities assigned Valid | Not blacklisted + valid descriptor (≥6/10 DA) |
| V2Dir | DirPort Available | Below (0/10 DA) | No DirPort, no tunnelled-dir-server (R) | Tunnelled directory via ORPort or DirPort (≥6/10 DA) |
| Fast | Speed | Below (1/10 DA) | 29.0 Mbit/s (1 DA relay-reported) | ≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥6/10 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Stable | MTBF | Below (0/10 DA) | Median: 0.0d (0/10 DA above threshold) | ≥0.0d - 7.5d (varies) (≥6/10 DA) [Stricter] moria1: ≥11846.6d |
| Uptime | Meets (10/10 DA) | 11.0d (R) | ≥2.1d - 2.1d (varies) (≥6/10 DA) [Stricter] 5947BB57: ≥5.9d |
|
| HSDir | Prereq: Fast | Below (1/10 DA) | 1/10 DA assigned Fast 29.0 Mbit/s (1 DA relay-reported) |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥6/10 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Below (1/10 DA) | 1/10 DA assigned Stable | ≥0.0d - 7.5d (varies) (≥6/10 DA) [Stricter] moria1: ≥11846.6d |
|
| Prereq: V2Dir | Below (0/10 DA) | 0/10 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥6/10 DA) | |
| Uptime | Below (1/10 DA) | 11.0d (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥6/10 DA) [Stricter] moria1: ≥98% WFU and ≥9.6d Time Known |
|
| Guard | Prereq: Fast | Below (1/10 DA) | 1/10 DA assigned Fast 29.0 Mbit/s (1 DA relay-reported) |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥6/10 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Below (1/10 DA) | 1/10 DA assigned Stable | ≥0.0d - 7.5d (varies) (≥6/10 DA) [Stricter] moria1: ≥11846.6d |
|
| Prereq: V2Dir | Below (0/10 DA) | 0/10 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥6/10 DA) | |
| WFU | Below (1/10 DA) | Median: 100.0% (1/10 DA above threshold) | ≥98% (≥6/10 DA) | |
| Time Known | Below (1/10 DA) | Median: 0.0d (1/10 DA above threshold) | ≥37 minutes 34 seconds (≥6/10 DA) | |
| Bandwidth | Below (1/10 DA) | 29.0 Mbit/s (1 DA relay-reported) | ≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-256.0 Mbit/s) (≥6/10 DA) | |
| Exit | Exit Policy | Below (0/10 DA) | Port 80: No | Port 443: No (R) | Allows ≥1 /8 on ports 80 AND 443 (≥6/10 DA) |
(DA) = Dir. Auth. Measured |
(R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-11-16 06:45:06).
Capacity (Relay Reported)
- Observed Bandwidth
- 28.99 Mbit/s
- Advertised Bandwidth
- 28.99 Mbit/s
- Rate Limit
- 503.32 Mbit/s
- Burst Limit
- 671.09 Mbit/s
- Total Data
- 799 GB (1 month)
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-16 06:45:06
- Measured By
-
0/8
Bandwidth Authorities
Not measured by: 5947BB57, E30CF7B3, dannenberg, faravahar, gabelmoo, longclaw, moria1, tor26 - Consensus Weight
- 160.0 Kbit/s (Unmeasured)
- Measured Min / Max
- N/A / N/A
History
Uptime Metrics
- Current Status
- DOWN 3d 5h 45m ago
- Overall Uptime (1M/6M/1Y/5Y)
- 79.7%/0.0%/0.0%/0.0%
- Flag Uptime (1M/6M/1Y/5Y)
- 79.4%/—/—/—
- Hibernating
- No
Timestamps
- First Seen
- 2w 1d 5h ago (2026-11-01 01:00:00)
- Last Seen
- 3d 5h 45m ago (2026-11-13 01:00:00)
- Last Restarted
- 1w 4d 24m ago (2026-11-05 06:20:43)
- Last Changed Address
- 2026-11-01 01:00:00
Evaluated 2026-11-16 06:45 UTC. /details snapshot 2026-11-16 05:00:00 UTC (cached 45s ago). /bandwidth snapshot 2026-11-15 21:00:00 UTC (cached 8h 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
Operator Identity
Source: AROI Validation API — 2026-11-15 22:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- torcontactemail AT proton.me
Family Configuration
- Family Support
- MyFamily Only (9) — Legacy only. Consider migrating to Happy Families. | View Full Family (9)
- Effective Members: 0
- none
- Effective Members: 9
1B2A99E3E1109BBA34C3A57F81FEB3F0301C670A 429C3B51BA58582E2D8DD53BD564BC6F29EBB3C4 4EA10A7A7F5F3C16DB3269426B178C780BABCB37 (this relay) 6A1D4C69F9D34FC788F23AC60B17A68A3E7FB841 8D7ECC837EC1E9F58D895B06A0042CAB1792343F A655EF84E8A1D300ED1BEC1E16F43EBCC0BCA53A B4585C074652A791D4C3892BDC6084984D39312C C8712ADF7B45FD9B0B552E37819609C18F81C183 D36DB14A83CEFC9C0AC7EB4E5F396058B74B83E1
- Alleged Member: 1
-
(they don't list you back)
584D3E72779ABB474C33A56A4FD9BC2985EF9997 (not in the network) - Indirect Members: 0
- none
DNS Health
Not an exit relay — DNS health testing does not apply.Last fetch was at Mon, 16 Nov 2026 06:45:38 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-16 06:45:06).
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 (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) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 5947BB57 | Yes | Yes | No | — | Y | Yes | Running, Valid, Fast, Stable | 29.0 Mbit/s (R) | 816.0 Kbit/s | 29.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 0.0d | 0d | 0.0d | 0.0d | 11.0d | 5.9d | 2026-11-12 18:21:44 | 29.0 Mbit/s (R) |
| E30CF7B3 | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — |
| dannenberg (DE) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — |
| dizum (NL) | No | — | — | — | N | No | — | — | — | — | — | — | — | — | — |
| faravahar (US) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — |
| gabelmoo (DE) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — |
| longclaw (US) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — |
| maatuska (SE) | No | — | — | — | N | No | — | — | — | — | — | — | — | — | — |
| moria1 (US) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — |
| tor26 (AT) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — |
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
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.
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.

