View Relay "SCSRelay"

Fingerprint: `6340BEF93C264B61EBB2B5341BF46FB3EE70DE40` | Family: 1 relay | admin@stare.network | AS398924 | United States of America | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, Exit (3)
DNS Health: Not Tested (via exitdnshealth.1aeo.com)
BW Verified: 4/6 BW Auths Measured
Stability: Not Overloaded | UP 3h 15m 53s ago

Reachability: IPv4: 9/9 (Directory Auths)
First Seen: 2h 15m 53s ago
BW Weight: 0.00% of Network | 0 Kbit/s Observed By Relay
Version: 0.4.8.10 Not Recommended

Issues Detected:

Guard: requires Fast flag : Guard flag requires having the Fast flag first
Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
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 2.2% 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 Fast flag : HSDir flag requires having the Fast flag first
Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
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
HSDir: WFU below threshold : WFU 2.2% 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.
Tor version not recommended : Running Tor version 0.4.8.10 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.

Connectivity and Location

Addresses

OR Address: mail.stare.network, ns1.stare.network, relay-001.stare.network
142.248.222.1:9001

Reachability (Directory Authorities)

IPv4: 9/9

Location

Country: United States of America
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS398924
AS Name: APPBASE.AI INC. (BGP.tools)
AS Rarity: Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

Flags and Eligibility

Current Flags (3): Running, Valid, Exit

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)	0 bit/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: 0.5d (1/9 DA above threshold) Min/Max: 0.5d / 1556.9d (9/9 DA, Voting / Total Eligible)	≥11.5d - 15.8d (varies) (≥5/9 DA) [Stricter] moria1: ≥6054.3d
Stable	Uptime	Below (0/9 DA)	0.1d (R)	≥6.2d - 6.5d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Below (4/9 DA)	4/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	≥11.5d - 15.8d (varies) (≥5/9 DA) [Stricter] moria1: ≥6054.3d
	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: 2.2% (0/9 DA above threshold) Min/Max: 2.0% / 4.4% (9/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 26.4d (9/9 DA above threshold) Min/Max: 10.0d / 26.5d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.8d
Guard	Prereq: Fast	Below (4/9 DA)	4/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	≥11.5d - 15.8d (varies) (≥5/9 DA) [Stricter] moria1: ≥6054.3d
	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: 2.2% (0/9 DA above threshold) Min/Max: 2.0% / 4.4% (9/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 26.4d (9/9 DA above threshold) Min/Max: 10.0d / 26.5d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Below (0/9 DA)	0 bit/s (R)	≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-312.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-09-01 03:15:10).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 0.00 Kbit/s
Advertised Bandwidth: Unknown
Rate Limit: 41.94 Mbit/s
Burst Limit: 83.89 Mbit/s
Total Data: N/A

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-09-01 03:15:10

Measured By: 4/6 Bandwidth Authorities
Not measured by: faravahar, longclaw
Median Measurement: 0 bit/s
Min / Max: 0 bit/s / 80.0 Kbit/s

Network Participation: Consensus Weight: 0.0038% of network (50th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0116% (41th pctl)

Uptime and Stability

Uptime Metrics

Current Status: UP 3h 15m 53s 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: 2h 15m 53s ago (2026-09-01 01:00:00)
Last Seen: 1h 15m 53s ago (2026-09-01 02:00:00)
Last Restarted: 3h 15m 53s ago (2026-09-01 00:00:00)
Last Changed Address: 2026-09-01 01:00:00

Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-08-31 20:00 UTC

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: admin@stare.network

Family Configuration

Family Support: None — No family membership configured

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Member: 1

6340BEF93C264B61EBB2B5341BF46FB3EE70DE40 (this relay)

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

Platform: Linux — Tor 0.4.8.10 on Linux
Version: 0.4.8.10 — Not Recommended
Version Status: Obsolete — Update urgently. See torproject.org/download

Exit Health & Policy

DNS Health

Status: Not Tested

Source: exitdnshealth.1aeo.com

IPv4 Exit Policy Summary

accept: 
  80
  443
  8080
  8443

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 142.248.222.1:*
accept *:80
accept *:443
accept *:8080
accept *:8443
reject *:*

Last fetch was at Tue, 01 Sep 2026 03:15:51 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-09-01 03:15: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	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	—	N	Yes	Running, Valid, Exit	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	2.2% \| 98%	26.5d \| 8d	0.5d \| 14.4d	0.1d \| 6.3d	2.2% \| 98.0%	26.5d \| 1.0d	2026-09-01 00:08:58	—
dannenberg (DE)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, Fast, Exit	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 312.0 Mbit/s OR 16.0 Mbit/s	2.1% \| 98%	25.2d \| 8d	0.5d \| 15.8d	0.1d \| 10.6d	2.1% \| 98.0%	25.2d \| 1.0d	2026-09-01 00:08:58	80.0 Kbit/s
dizum (NL)	Yes	Yes	Yes	—	N	Yes	Running, Valid, Exit	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	2.2% \| 98%	26.3d \| 8d	0.5d \| 14.6d	0.1d \| 6.5d	2.2% \| 98.0%	26.3d \| 1.0d	2026-09-01 00:08:58	—
faravahar (US)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, Exit	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	2.0% \| 98%	26.5d \| 8d	0.5d \| 15.9d	0.1d \| 6.6d	2.0% \| 98.0%	26.5d \| 1.0d	2026-09-01 00:08:58	—
gabelmoo (DE)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, Fast, Exit	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	2.0% \| 98%	26.4d \| 8d	0.5d \| 15.8d	0.1d \| 6.3d	2.0% \| 98.0%	26.4d \| 1.0d	2026-09-01 00:08:58	66.4 Kbit/s
longclaw (US)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, Exit	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	2.5% \| 98%	26.1d \| 8d	0.6d \| 18.0d	0.1d \| 6.6d	2.5% \| 98.0%	26.1d \| 1.0d	2026-09-01 00:08:58	—
maatuska (SE)	Yes	Yes	Yes	—	N	Yes	Running, Valid, Exit	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	2.2% \| 98%	26.4d \| 8d	0.5d \| 11.5d	0.1d \| 6.5d	2.2% \| 98.0%	26.4d \| 1.0d	2026-09-01 00:08:58	—
moria1 (US)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, Fast, Stable, Exit	0 bit/s \| 8.4 Mbit/s	0 bit/s \| 200.0 Mbit/s OR 16.0 Mbit/s	4.4% \| 98%	10.0d \| 8d	1556.9d \| 6054.3d	0.1d \| 6.4d	4.4% \| 98.0%	10.0d \| 9.8d	2026-09-01 00:08:58	67.2 Kbit/s
tor26 (AT)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, Fast, Exit	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 280.0 Mbit/s OR 16.0 Mbit/s	2.0% \| 98%	26.4d \| 8d	0.5d \| 16.2d	0.1d \| 6.2d	2.0% \| 98.0%	26.4d \| 1.0d	2026-09-01 00:08:58	60.8 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.