View Relay "HappyToServeYou01"

Fingerprint: 584D3E72779ABB474C33A56A4FD9BC2985EF9997 | Family: 1 relay | torcontactemail AT proton DOT me | AS36352 | United States of America | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid (2)
BW Verified
3/7 BW Auths Measured 8 Kbit/s Median
Stability
Not Overloaded | UP 4h 16s ago
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
3h 45m 14s ago
BW Weight
0 Kbit/s Observed By Relay
Version
0.4.9.11 Not Recommended
Issues Detected:
  • Not getting the Fast flag : Only 0/9 authorities vote Fast (5 needed). gabelmoo, moria1 and tor26 measured this relay at 8.0 Kbit/s, below the Fast threshold (816.0 Kbit/s; moria1: 8.4 Mbit/s). dizum, longclaw and maatuska used the relay-reported unknown, below the Fast threshold (816.0 Kbit/s). bastet and dannenberg 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 – 280.0 Mbit/s). gabelmoo, moria1 and tor26 measured this relay at 8.0 Kbit/s. dizum, longclaw and maatuska used the relay-reported unknown. bastet and dannenberg 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: Time Known below threshold : Time Known 0.1 days is below 8 days requirement (7.9 more days 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.
  • 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
  • Tor version not recommended : Running Tor version 0.4.9.11 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
107-173-144-73-host.colocrossing.com
107.173.144.73:9001
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
United States of America United States of America
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS36352
AS Name
HostPapa (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.16% consensus weight, 50 operators)

Flags and Eligibility

Current Flags (2): Running, Valid
Eligible Flags (3): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 0/9 | Stable: 0/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
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.1d (0/9 DA above threshold)
Min/Max: 0.1d / 0.1d (9/9 DA, Voting / Total Eligible)		 ≥6.0d - 8.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10181.4d
Uptime Below (0/9 DA) 0.2d (R) ≥5.6d - 5.7d (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 (0/9 DA) 0/9 DA assigned Stable ≥6.0d - 8.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10181.4d
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 ≥9.7d 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 (0/9 DA) 0/9 DA assigned Stable ≥6.0d - 8.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10181.4d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (9/9 DA) Majority: 100.0% (9/9 DA) ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 7.9 more days) Median: 0.1d (0/9 DA above threshold)
Min/Max: 0.1d / 0.1d (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-280.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-10-20 22:45:05).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
0.00 Kbit/s
Advertised Bandwidth
Unknown
Rate Limit
50.33 Mbit/s
Burst Limit
50.33 Mbit/s
Total Data
N/A
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-10-20 22:45:05

Measured By
3/7 Bandwidth Authorities
Not measured by: bastet, dannenberg, faravahar, longclaw
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: N/A | Guard: N/A | Middle: N/A | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 4h 16s 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 14s ago (2026-10-20 19:00:00)
Last Seen
1h 45m 14s ago (2026-10-20 21:00:00)
Last Restarted
4h 16s ago (2026-10-20 18:44:58)
Last Changed Address
2026-10-20 19:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-10-20 15:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
torcontactemail AT proton DOT me
Family Configuration
Family Support
MyFamily Only (1) — Legacy only. Consider migrating to Happy Families.
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
584D3E72779ABB474C33A56A4FD9BC2985EF9997 (this relay)
Alleged Members: 9
(they don't list you back) 
1B2A99E3E1109BBA34C3A57F81FEB3F0301C670A (not in the network)
429C3B51BA58582E2D8DD53BD564BC6F29EBB3C4 (not in the network)
4EA10A7A7F5F3C16DB3269426B178C780BABCB37 (not in the network)
6A1D4C69F9D34FC788F23AC60B17A68A3E7FB841 (not in the network)
8D7ECC837EC1E9F58D895B06A0042CAB1792343F (not in the network)
A655EF84E8A1D300ED1BEC1E16F43EBCC0BCA53A (not in the network)
B4585C074652A791D4C3892BDC6084984D39312C (not in the network)
C8712ADF7B45FD9B0B552E37819609C18F81C183 (not in the network)
D36DB14A83CEFC9C0AC7EB4E5F396058B74B83E1 (not in the network)
Indirect Members: 0
none

Software and Version

Platform
Linux — Tor 0.4.9.11 on Linux
Version
0.4.9.11 — 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: 
  1-65535
IPv6 Exit Policy Summary
None
Full Exit Policy
reject *:*

Last fetch was at Tue, 20 Oct 2026 22:45:13 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-10-20 22: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 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 — Y Yes Running, Valid 0 bit/s (U) | 816.0 Kbit/s 0 bit/s (U) | 184.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 8.4d 0.2d | 5.6d 2026-10-20 18:46:29 —
dannenberg (DE) Yes Yes No — Y Yes Running, Valid 0 bit/s (U) | 816.0 Kbit/s 0 bit/s (U) | 280.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 6.0d 0.2d | 5.7d 2026-10-20 18:46:29 —
dizum (NL) Yes Yes No — N Yes Running, Valid 0 bit/s (R) | 816.0 Kbit/s 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 8.3d 0.2d | 5.7d 2026-10-20 18:46:29 —
faravahar (US) Yes Yes No — Y Yes Running, Valid not published | 816.0 Kbit/s not published | 256.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 8.7d 0.2d | 6.5d 2026-10-20 18:46:29 —
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid 8.0 Kbit/s (M) | 816.0 Kbit/s 8.0 Kbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 8.4d 0.2d | 5.7d 2026-10-20 18:46:29 8.0 Kbit/s (M)
longclaw (US) Yes Yes No — Y Yes Running, Valid 0 bit/s (R) | 816.0 Kbit/s 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 8.6d 0.2d | 5.6d 2026-10-20 18:46:29 —
maatuska (SE) Yes Yes No — N Yes Running, Valid 0 bit/s (R) | 816.0 Kbit/s 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 8.3d 0.2d | 5.6d 2026-10-20 18:46:29 —
moria1 (US) Yes Yes No — Y Yes Running, Valid 8.0 Kbit/s (M) | 8.4 Mbit/s 8.0 Kbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 10181.4d 0.2d | 5.7d 2026-10-20 18:46:29 8.0 Kbit/s (M)
tor26 (AT) Yes Yes No — Y Yes Running, Valid 8.0 Kbit/s (M) | 816.0 Kbit/s 8.0 Kbit/s (M) | 264.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 8.6d 0.2d | 5.8d 2026-10-20 18:46:29 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.