View Relay "TV895"

Fingerprint: 7F167255C26587B96FE01C1FE2E080FDF8BD6FD2 | Family: 1 relay | printerexpert@mail2tor.com | AS7922 | United States of America | Linux

Health Status

Consensus
In Consensus (8/9 Directory Auths)
Flags
Running, Valid, V2Dir, Exit (4)
DNS Health
Not Tested (via exitdnshealth.1aeo.com)
BW Verified
4/6 BW Auths Measured 6120 bit/s Median
Stability
Not Overloaded | DOWN 21h 46m 38s ago
Reachability
IPv4: 8/9 (Directory Auths)
First Seen
1d 7h 46m ago
BW Weight
0.00% of Network | 532 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.1 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 39.5% 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.2 days is below 8 days requirement (6.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 39.5% 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.
  • High consensus weight deviation : Large variation in Consensus Weight values across authorities (see 'Cons Wt' column in Per-Authority Details below)
    Suggestion: Consensus weight measurements vary significantly between authorities. This can affect traffic distribution. Ensure stable network connection and consistent bandwidth availability.
Notes:
  • Partial IPv4 reachability: 8/9 authorities can reach this relay

Connectivity and Location

Addresses
OR Address
c-73-207-115-65.hsd1.ga.comcast.net
73.207.115.65:9001
Reachability (Directory Authorities)
IPv4
8/9
Location
Country
United States of America United States of America
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS7922
AS Name
Comcast Cable Communications, LLC (BGP.tools)
AS Rarity
Epic (score: 3/5, <0.05% consensus weight, 35 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Exit
Eligible Flags (4): Running: 8/9 | Valid: 8/9 | V2Dir: 8/9 | Fast: 4/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 8/9
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
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) 532.5 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.2d (0/9 DA above threshold)
Min/Max: 0.2d / 0.3d (8/9 DA, Voting / Total Eligible)		 ≥11.5d - 55.6d (varies) (≥5/9 DA)
[Stricter] moria1: ≥356.4d
Uptime Below (0/9 DA) 0.9d (R) ≥13.7d - 14.7d (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 (0/9 DA) 0/9 DA assigned Stable ≥11.5d - 55.6d (varies) (≥5/9 DA)
[Stricter] moria1: ≥356.4d
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: 38.7% (0/9 DA above threshold)
Min/Max: 36.8% / 39.5% (8/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 1.2d (0/9 DA above threshold)
Min/Max: 1.2d / 1.3d (8/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 (0/9 DA) 0/9 DA assigned Stable ≥11.5d - 55.6d (varies) (≥5/9 DA)
[Stricter] moria1: ≥356.4d
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: 38.7% (0/9 DA above threshold)
Min/Max: 36.8% / 39.5% (8/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 6.8 more days) Median: 1.2d (0/9 DA above threshold)
Min/Max: 1.2d / 1.3d (8/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 532.5 Kbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-296.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-13 23:45:02).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
532.48 Kbit/s
Advertised Bandwidth
532.48 Kbit/s
Rate Limit
100.00 Mbit/s
Burst Limit
100.00 Mbit/s
Total Data
525 MB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-13 23:45:02

Measured By
4/6 Bandwidth Authorities
Not measured by: longclaw, moria1
Median Measurement
6120.0 bit/s
Min / Max
8 bit/s / 12.0 Kbit/s
Deviation
12.0 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (2th pctl) | Guard: N/A | Middle: N/A | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
DOWN 21h 46m 38s ago
Overall Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (0.0%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
1d 7h 46m ago (2026-03-12 16:00:00)
Last Seen
21h 46m 38s ago (2026-03-13 02:00:00)
Last Restarted
22h 40m 37s ago (2026-03-13 01:06:01)
Last Changed Address
2026-03-12 16:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-03-13 16: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 
7F167255C26587B96FE01C1FE2E080FDF8BD6FD2 (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 Health & Policy

DNS Health
Status
Not Tested
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 
  1-65535
IPv6 Exit Policy Summary
None
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 73.207.115.65:*
accept *:*

Last fetch was at Fri, 13 Mar 2026 23:46:37 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-03-13 23:45:02).

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 532.5 Kbit/s | 816.0 Kbit/s 532.5 Kbit/s | 208.0 Mbit/s OR 16.0 Mbit/s 39.5% | 98% 1.2d | 8d 0.3d | 58.0d 0.9d | 14.6d 39.5% | 98.0% 1.2d | 1.0d 2026-03-13 18:58:11 240 bit/s
dannenberg (DE) Yes Yes Yes — N Yes Valid, V2Dir, Fast, Exit 532.5 Kbit/s | 816.0 Kbit/s 532.5 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 37.5% | 98% 1.3d | 8d 0.2d | 11.5d 0.9d | 14.7d 37.5% | 98.0% 1.3d | 1.0d 2026-03-13 18:58:11 12.0 Kbit/s
dizum (NL) Yes Yes Yes — N Yes Valid, V2Dir, Fast, Exit 532.5 Kbit/s | 816.0 Kbit/s 532.5 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 39.5% | 98% 1.2d | 8d 0.3d | 46.2d 0.9d | 13.7d 39.5% | 98.0% 1.2d | 1.0d 2026-03-13 18:58:11 12.0 Kbit/s
faravahar (US) Yes Yes Yes — N Yes Valid, V2Dir, Fast, Exit 532.5 Kbit/s | 816.0 Kbit/s 532.5 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 39.3% | 98% 1.2d | 8d 0.3d | 53.2d 0.9d | 14.7d 39.3% | 98.0% 1.2d | 1.0d 2026-03-13 18:58:11 12.0 Kbit/s
gabelmoo (DE) Yes Yes Yes — Y Yes Valid, V2Dir, Exit 532.5 Kbit/s | 816.0 Kbit/s 532.5 Kbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 37.6% | 98% 1.2d | 8d 0.2d | 59.7d 0.9d | 14.7d 37.6% | 98.0% 1.2d | 1.0d 2026-03-13 18:58:11 40 bit/s
longclaw (US) Yes Yes Yes — Y Yes Valid, V2Dir, Fast, Exit 532.5 Kbit/s | 816.0 Kbit/s 532.5 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 38.4% | 98% 1.2d | 8d 0.2d | 59.2d 0.9d | 14.7d 38.4% | 98.0% 1.2d | 1.0d 2026-03-13 18:58:11 12.0 Kbit/s
maatuska (SE) Yes Yes Yes — Y Yes Valid, V2Dir, Exit 532.5 Kbit/s | 816.0 Kbit/s 532.5 Kbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 38.9% | 98% 1.2d | 8d 0.2d | 39.2d 0.9d | 14.7d 38.9% | 98.0% 1.2d | 1.0d 2026-03-13 18:58:11 160 bit/s
moria1 (US) No — — — Y No — — — — — — — — — — —
tor26 (AT) Yes Yes Yes — Y Yes Valid, V2Dir, Exit 532.5 Kbit/s | 816.0 Kbit/s 532.5 Kbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 36.8% | 98% 1.2d | 8d 0.2d | 55.6d 0.9d | 15.3d 36.8% | 98.0% 1.2d | 1.0d 2026-03-13 18:58:11 8 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.