Tor Relays :: TV8503

View Relay "TV8503"

Fingerprint: `231C9952C348B8EEF0F6E05DBAF933F338449D52` | Family: 1 relay | printerexpert@mail2tor.com | AS6167 | United States of America | Linux

Health Status

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

Reachability: IPv4: 8/9 (Directory Auths)
First Seen: 4d 20h 15m ago
BW Weight: 0.00% of Network | 188 Kbit/s Observed By Relay
Version: 0.4.8.22 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: bandwidth below threshold : Observed bandwidth 0.0 MB/s is below 2 MB/s minimum (AuthDirGuardBWGuarantee)
Suggestion: Guard requires ≥2 MB/s bandwidth OR being in top 25% of network. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx or ARM.
Guard: WFU below threshold : Weighted Fractional Uptime 0.3% 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 4.2 days is below 8 days requirement (3.8 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: 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: WFU below threshold : WFU 0.3% 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 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.

Notes:

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

Connectivity and Location

Addresses

OR Address: 126.sub-75-247-195.myvzw.com
75.247.195.126:9001

Reachability (Directory Authorities)

IPv4: 8/9

Location

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

Autonomous System

AS Number: AS6167
AS Name: Verizon Business (BGP.tools)
AS Rarity: Legendary (score: 4/5, <0.05% consensus weight, 2 operators)

Flags and Eligibility

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

Eligibility Flag Vote Details

Flag	Metric	Status	Relay Value	Threshold Required
Running	IPv4 Reachability	Meets (8/9 DA)	8/9 authorities reached relay	≥5/9 DA ORPort reachable
Running	IPv6 Reachability	Below (0/1 DA)	0/1 tested authorities reached relay	≥1/1 tested (majority) (≥1/1 DA)
Valid	Descriptor	Meets (8/9 DA)	8/9 authorities assigned Valid	Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir	DirPort Available	Meets (8/9 DA)	Tunnelled: Yes (no DirPort) (R)	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast	Speed	Below (0/9 DA)	188.4 Kbit/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.0d (0/9 DA above threshold) Min/Max: 0.0d / 0.0d (8/9 DA, Voting / Total Eligible)	≥11.8d - 52.7d (varies) (≥5/9 DA) [Stricter] moria1: ≥430.3d
Stable	Uptime	Below (0/9 DA)	4.9d (R)	≥8.0d - 10.0d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Below (0/9 DA)	0/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 (0/9 DA)	0/9 DA assigned Stable	≥11.8d - 52.7d (varies) (≥5/9 DA) [Stricter] moria1: ≥430.3d
	Prereq: V2Dir	Meets (8/9 DA)	8/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Below (0/9 DA)	Median: 0.3% (0/9 DA above threshold) Min/Max: 0.0% / 0.4% (8/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Meets (7/9 DA)	Median: 4.2d (0/9 DA above threshold) Min/Max: 0.0d / 4.2d (8/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.9d
Guard	Prereq: Fast	Below (0/9 DA)	0/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 (0/9 DA)	0/9 DA assigned Stable	≥11.8d - 52.7d (varies) (≥5/9 DA) [Stricter] moria1: ≥430.3d
	Prereq: V2Dir	Meets (8/9 DA)	8/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Below (0/9 DA)	Median: 0.3% (0/9 DA above threshold) Min/Max: 0.0% / 0.4% (8/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Below (0/9 DA) (need 3.8 more days)	Median: 4.2d (0/9 DA above threshold) Min/Max: 0.0d / 4.2d (8/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Below (0/9 DA)	188.4 Kbit/s (R)	≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-304.0 Mbit/s (≥5/9 DA)
Exit	Exit Policy	Meets (8/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-03-04 22:15:08).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 188.42 Kbit/s
Advertised Bandwidth: 188.42 Kbit/s
Rate Limit: 100.00 Mbit/s
Burst Limit: 100.00 Mbit/s
Total Data: 739 MB (1 month)

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-04 22:15:08

Measured By: 0/6 Bandwidth Authorities
Not measured by: bastet, gabelmoo, longclaw, maatuska, moria1, tor26
Median Measurement: 208.0 bit/s
Min / Max: 208 bit/s / 208 bit/s

Network Participation: Consensus Weight: 0.0000% of network (3th pctl) | Guard: N/A | Middle: N/A | Exit: N/A

Uptime and Stability

Uptime Metrics

Current Status: DOWN 4d 20h 15m 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: 4d 20h 15m ago (2026-02-28 03:00:00)
Last Seen: 4d 20h 15m ago (2026-02-28 03:00:00)
Last Restarted: 4d 21h 9m ago (2026-02-28 02:05:58)
Last Changed Address: 2026-02-28 03:00:00

Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-03-04 14:00 UTC

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: printerexpert@mail2tor.com

Family Configuration

Family Support: None — No family membership configured

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Member: 1

231C9952C348B8EEF0F6E05DBAF933F338449D52 (this relay)

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

Platform: Linux — Tor 0.4.8.22 on Linux
Version: 0.4.8.22 — Recommended
Version Status: Recommended

Exit Policy

IPv4 Exit Policy Summary

accept: 
  1-65535

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

Last fetch was at Wed, 04 Mar 2026 23:15:39 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-03-04 22:15:08).

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	—	Y	Yes	Valid, V2Dir, Exit	188.4 Kbit/s \| 816.0 Kbit/s	188.4 Kbit/s \| 224.0 Mbit/s OR 16.0 Mbit/s	0.3% \| 98%	4.2d \| 8d	0.0d \| 56.3d	4.9d \| 9.6d	0.3% \| 98.0%	4.2d \| 1.0d	2026-03-04 04:55:37	208 bit/s
dannenberg (DE)	Yes	Yes	Yes	—	N	Yes	Valid, V2Dir, Exit	188.4 Kbit/s \| 816.0 Kbit/s	188.4 Kbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	0.0% \| 98%	0.0d \| 8d	0.0d \| 11.8d	4.9d \| 8.2d	0.0% \| 98.0%	0.0d \| 1.0d	2026-03-04 04:55:37	208 bit/s
dizum (NL)	Yes	Yes	Yes	—	N	Yes	Valid, V2Dir, Exit	188.4 Kbit/s \| 816.0 Kbit/s	188.4 Kbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	0.3% \| 98%	4.2d \| 8d	0.0d \| 42.7d	4.9d \| 8.0d	0.3% \| 98.0%	4.2d \| 1.0d	2026-03-04 04:55:37	208 bit/s
faravahar (US)	Yes	Yes	Yes	—	N	Yes	Valid, V2Dir, Exit	188.4 Kbit/s \| 816.0 Kbit/s	188.4 Kbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	0.3% \| 98%	4.2d \| 8d	0.0d \| 48.6d	4.9d \| 10.0d	0.3% \| 98.0%	4.2d \| 1.0d	2026-03-04 04:55:37	208 bit/s
gabelmoo (DE)	Yes	Yes	Yes	—	Y	Yes	Valid, V2Dir, Exit	188.4 Kbit/s \| 816.0 Kbit/s	188.4 Kbit/s \| 304.0 Mbit/s OR 16.0 Mbit/s	0.3% \| 98%	4.2d \| 8d	0.0d \| 58.8d	4.9d \| 10.1d	0.3% \| 98.0%	4.2d \| 1.0d	2026-03-04 04:55:37	208 bit/s
longclaw (US)	Yes	Yes	Yes	—	Y	Yes	Valid, V2Dir, Exit	188.4 Kbit/s \| 816.0 Kbit/s	188.4 Kbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	0.3% \| 98%	4.2d \| 8d	0.0d \| 59.0d	4.9d \| 9.6d	0.3% \| 98.0%	4.2d \| 1.0d	2026-03-04 04:55:37	208 bit/s
maatuska (SE)	Yes	Yes	Yes	—	Y	Yes	Valid, V2Dir, Exit	188.4 Kbit/s \| 816.0 Kbit/s	188.4 Kbit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	0.4% \| 98%	4.2d \| 8d	0.0d \| 39.2d	4.9d \| 10.1d	0.4% \| 98.0%	4.2d \| 1.0d	2026-03-04 04:55:37	208 bit/s
moria1 (US)	No	—	—	—	Y	No	—	—	—	—	—	—	—	—	—	—	—
tor26 (AT)	Yes	Yes	Yes	—	Y	Yes	Valid, V2Dir, Exit	188.4 Kbit/s \| 816.0 Kbit/s	188.4 Kbit/s \| 304.0 Mbit/s OR 16.0 Mbit/s	0.3% \| 98%	4.2d \| 8d	0.0d \| 52.7d	4.9d \| 10.1d	0.3% \| 98.0%	4.2d \| 1.0d	2026-03-04 04:55:37	208 bit/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.