Tor Relays :: TV8143

View Relay "TV8143"

Family: 1 relay | printerexpert@mail2tor.com | AS20115 | United States of America | Linux

Health Status

Consensus: In Consensus (8/9 Directory Auths)
Flags: Exit, Running, V2Dir, Valid (4)
BW Verified: 0/6 BW Auths Measured
Stability: Not Overloaded | DOWN 1d 15m 43s ago

Reachability: IPv4: 8/9 (Directory Auths)
First Seen: 1d 1h 17m ago
BW Weight: 0 Kbit/s Observed By Relay
Version: 0.4.8.22 Recommended

Issues Detected:

Guard: WFU below threshold : Weighted Fractional Uptime 5.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.
Guard: Time Known below threshold : Time Known 1.0 days is below 8 days requirement (7.0 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.
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: 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.
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: WFU below threshold : WFU 5.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.
HSDir: Time Known below threshold : Time Known 23.3 hours below 25 hours (dir-spec default)
Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.
Low bandwidth authority measurements : Only 0/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.
StaleDesc flag assigned : Relay descriptor is older than 18 hours
Suggestion: Your relay is not publishing fresh descriptors. Check: 1) Tor process is running, 2) Network connectivity, 3) Clock is synchronized (NTP). Restart Tor if needed.

Notes:

Partial IPv4 reachability: 8/9 authorities can reach this relay

Connectivity and Location

Addresses

OR Address: 47.25.208.71:9001

Reachability (Directory Authorities)

IPv4: 8/9

Location

Country: United States of America
Interactive Map: View on Interactive Map

Autonomous System

AS Number: AS20115
AS Name: Charter Communications LLC (BGP.tools)
AS Rarity: Epic (score: 3/5, <0.05% consensus weight, 14 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Exit

Eligibility Flag Vote Details

Flag	Metric	Status	Relay Value	Threshold Required
Fast	Speed	Below	0 bit/s (R)	≥800.0 Kbit/s (guarantee) OR top 7/8 [Stricter] moria1: ≥8.4 Mbit/s
Stable	MTBF	Below	Median: 0.1d (0/9 DA above threshold) Min/Max: 0.1d / 0.1d (8/9 DA, Voting / Total Eligible)	≥22.1d - 51.9d (varies) [Stricter] moria1: ≥451.9d
Stable	Uptime	Below	1.1d (R)	≥6.4d - 7.5d (varies)
HSDir	Prereq: Stable	Below	0/9 authorities assigned Stable flag	≥5/9 authorities
	Prereq: Fast	Below	0/9 authorities assigned Fast flag	≥5/9 authorities
	WFU	Below	Median: 6.2% (0/9 DA above threshold) Min/Max: 5.5% / 9.4% (8/9 DA, Voting / Total Eligible)	≥98.0%
	Time Known	Below	Median: 1.0d (0/9 DA above threshold) Min/Max: 0.7d / 1.0d (8/9 DA, Voting / Total Eligible)	≥1.0d (most) [Stricter] moria1: ≥9.9d
Guard	Prereq: Fast	Below	0/9 authorities assigned Fast flag	≥5/9 authorities
	Prereq: Stable	Below	0/9 authorities assigned Stable flag	≥5/9 authorities
	Prereq: V2Dir	Meets	8/9 authorities assigned V2Dir flag	≥5/9 authorities
	WFU	Below	Median: 6.2% (0/9 DA above threshold) Min/Max: 5.5% / 9.4% (8/9 DA, Voting / Total Eligible)	≥98% (all authorities)
	Time Known	Below (need 7.0 more days)	Median: 1.0d (0/9 DA above threshold) Min/Max: 0.7d / 1.0d (8/9 DA, Voting / Total Eligible)	≥8 days (all authorities)
	Bandwidth	Below	0 bit/s (R)	≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-02-11 21:15:08).

Last fetch was at Wed, 11 Feb 2026 22:15:42 GMT.

Nickname

TV8143

Fingerprint

581A246149728D805F972DC20CBCAACE40A32771

AROI (?)

none

Contact

printerexpert@mail2tor.com

IPv4 Exit Policy Summary

accept: 
  1-65535

IPv6 Exit Policy Summary

none

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 47.25.208.71:*
accept *:*

Effective Family Member: 1

581A246149728D805F972DC20CBCAACE40A32771

Alleged Family Members: 0

none

Indirect Family Members: 0

none

Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit): 0.00 Kbit/s | unknown| 100.00 Mbit/s| 100.00 Mbit/s Not Measured
Network Participation (Consensus Weight | Guard | Middle | Exit): N/A | N/A | N/A | N/A
OR Address: 47.25.208.71:9001
Exit Address: none
Dir Address: none
Country: United States of America
Interactive Map: View on Interactive Map
Autonomous System (AS Number | AS Name): AS20115 | Charter Communications LLC (BGP.tools)
Flags: 4: Exit Running V2Dir Valid
Flag Uptime (1M/6M/1Y/5Y): N/A
Uptime (1M/6M/1Y/5Y): 0.0%/0.0%/0.0%/0.0%
Uptime / Downtime: DOWN 1d 15m 43s ago
Seen (First | Last): 1d 1h 17m ago (2026-02-10 21:00:00) | 1d 17m 30s ago (2026-02-10 22:00:00)
Last Restarted: 1d 2h 5m ago (2026-02-10 20:12:00)
Last Changed Address or Port: 2026-02-10 21:00:00
Hibernating: No
Platform (Short | Long): Linux | Tor 0.4.8.22 on Linux
Version (Running | Recommended | Status): 0.4.8.22 | Yes | recommended

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-02-11 21:15:08).

Consensus Status (need ≥5/9): In Consensus — 8/9 authorities voted.
Flag Eligibility (need ≥5/9 for flag): Running: 8/9 | Valid: 8/9 | V2Dir: 8/9 | Fast: 0/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9
Reachability: IPv4: 8/9
Consensus Weight (Dir. Auth.): Median: 0.0 bit/s | Min: 0 bit/s | Max: 0 bit/s
Identified Issues:
- Guard: WFU below threshold: Weighted Fractional Uptime 5.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.
- Guard: Time Known below threshold: Time Known 1.0 days is below 8 days requirement (7.0 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.
- 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: 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.
- 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: WFU below threshold: WFU 5.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.
- HSDir: Time Known below threshold: Time Known 23.3 hours below 25 hours (dir-spec default)
  - Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.
- Low bandwidth authority measurements: Only 0/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.
- StaleDesc flag assigned: Relay descriptor is older than 18 hours
  - Suggestion: Your relay is not publishing fresh descriptors. Check: 1) Tor process is running, 2) Network connectivity, 3) Clock is synchronized (NTP). Restart Tor if needed.
Notes:
- Partial IPv4 reachability: 8/9 authorities can reach this relay

Summary: Your Relay vs Consensus

Green = meets threshold, Red = below threshold, Yellow = partial.

Metric	Dir Auth Measured	Dir Auth Threshold	Status
In Consensus (Dir. Auth.)	8/9 authorities	≥5/9 (majority)	IN CONSENSUS
Running (IPv4 Reachable)	8/9 authorities reached this relay	≥5/9 (majority)	RUNNING
Valid	8/9 (Running + Valid Descriptor)	≥5/9 (majority)	VALID
Consensus Weight (Dir. Auth.)	0.0 bit/s (median)	N/A (no threshold, used for path selection)	—
Guard WFU (Dir. Auth., guard-wfu)	6.2%	≥98% (all authorities)	BELOW - cannot get Guard
Guard TK (Dir. Auth., tk)	1.0 days	≥8 days (all authorities)	BELOW - need 7.0 more days
Guard BW (Relay Reported)	0 bit/s	≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s	BELOW - need ≥2 MB/s
Stable Uptime (Relay Reported)	1.1d	≥6.4d - 7.5d (typical)	BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf)	0 days	≥22.1d - 51.9d (typical) [Stricter] moria1: ≥451.9d	BELOW - 0/9
Fast Speed (Relay Reported)	0 bit/s	≥800.0 Kbit/s (guarantee) OR ≥816.0 Kbit/s (typical) [Stricter] moria1: ≥8.4 Mbit/s	BELOW - need ≥100 KB/s
HSDir WFU (Dir. Auth., wfu)	6.2%	≥98.0% (from all auths)	BELOW - 0/9
HSDir TK (Dir. Auth., tk)	1.0 days	≥1.0d (8/9 auths) [Stricter] moria1: ≥9.9d	BELOW - 0/9

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	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	Y	Yes	Valid, V2Dir, Exit, StaleDesc	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 224.0 Mbit/s OR 16.0 Mbit/s	5.7% \| 98%	1.0d \| 8d	0.1d \| 51.9d	1.1d \| 7.5d	5.7% \| 98.0%	1.0d \| 1.0d	2026-02-10 20:19:38 [Stale]	—
dannenberg (DE)	Yes	Yes	N	Yes	Valid, V2Dir, Exit, StaleDesc	0 bit/s \| 712.0 Kbit/s	0 bit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	6.6% \| 98%	1.0d \| 6d	0.1d \| 22.1d	1.1d \| 6.5d	6.6% \| 98.0%	1.0d \| 1.0d	2026-02-10 20:19:38 [Stale]	—
dizum (NL)	Yes	Yes	N	Yes	Valid, V2Dir, Exit, StaleDesc	0 bit/s \| 704.0 Kbit/s	0 bit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	6.0% \| 98%	1.0d \| 6d	0.1d \| 27.7d	1.1d \| 6.4d	6.0% \| 98.0%	1.0d \| 1.0d	2026-02-10 20:19:38 [Stale]	—
faravahar (US)	Yes	Yes	N	Yes	Valid, V2Dir, Exit, StaleDesc	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	5.5% \| 98%	1.0d \| 8d	0.1d \| 47.9d	1.1d \| 7.5d	5.5% \| 98.0%	1.0d \| 1.0d	2026-02-10 20:19:38 [Stale]	—
gabelmoo (DE)	Yes	Yes	Y	Yes	Valid, V2Dir, Exit, StaleDesc	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 312.0 Mbit/s OR 16.0 Mbit/s	6.5% \| 98%	1.0d \| 8d	0.1d \| 60.4d	1.1d \| 7.5d	6.5% \| 98.0%	1.0d \| 1.0d	2026-02-10 20:19:38 [Stale]	—
longclaw (US)	Yes	Yes	Y	Yes	Valid, V2Dir, Exit	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	9.4% \| 98%	0.7d \| 8d	0.1d \| 61.0d	1.1d \| 7.3d	9.4% \| 98.0%	0.7d \| 1.0d	2026-02-10 20:19:38	—
maatuska (SE)	Yes	Yes	Y	Yes	Valid, V2Dir, Exit, StaleDesc	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 304.0 Mbit/s OR 16.0 Mbit/s	8.6% \| 98%	0.7d \| 8d	0.1d \| 41.8d	1.1d \| 7.5d	8.6% \| 98.0%	0.7d \| 1.0d	2026-02-10 20:19:38 [Stale]	—
moria1 (US)	No	—	Y	No	—	—	—	—	—	—	—	—	—	—	—
tor26 (AT)	Yes	Yes	Y	Yes	Valid, V2Dir, Exit, StaleDesc	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	5.6% \| 98%	1.0d \| 8d	0.1d \| 57.3d	1.1d \| 7.5d	5.6% \| 98.0%	1.0d \| 1.0d	2026-02-10 20:19:38 [Stale]	—

— = 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). This is your relay's self-reported uptime from its 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.