View Relay "TV388"

Fingerprint: 5313F5948F308EB4CCBE25C2EFFE6D2988B2AD73 | Family: 1 relay | printerexpert@mail2tor.com | AS5650 | 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
2/6 BW Auths Measured 240 bit/s Median
Stability
Not Overloaded | UP 4h 41m 15s ago
Reachability
IPv4: 8/9 (Directory Auths)
First Seen
3h 46m 39s ago
BW Weight
0.00% of Network | 245 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: 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: 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: Time Known below threshold : Time Known 2.7 hours below 25 hours (dir-spec default)
    Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.
  • 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.
  • Low bandwidth authority measurements : Only 2/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
47-151-129-189.fdr02.snmn.ca.ip.frontiernet.net
47.151.129.189: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
AS5650
AS Name
Frontier Communications of America, Inc. (BGP.tools)
AS Rarity
Epic (score: 3/5, <0.05% consensus weight, 12 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Exit
Eligible Flags (4): Running: 8/9 | Valid: 8/9 | V2Dir: 8/9 | Fast: 0/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) 245.8 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.1d (0/9 DA above threshold)
Min/Max: 0.1d / 0.1d (8/9 DA, Voting / Total Eligible)		 ≥11.7d - 55.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥360.8d
Uptime Below (0/9 DA) 0.2d (R) ≥9.7d - 12.7d (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.7d - 55.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥360.8d
Prereq: V2Dir Meets (8/9 DA) 8/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (8/9 DA) Majority: 100.0% (8/9 DA) ≥98.0% (≥5/9 DA)
Time Known Below (0/9 DA) Median: 0.1d (0/9 DA above threshold)
Min/Max: 0.1d / 0.1d (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.7d - 55.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥360.8d
Prereq: V2Dir Meets (8/9 DA) 8/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (8/9 DA) Majority: 100.0% (8/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 (8/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 245.8 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-16 17:45:08).

Bandwidth Metrics

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

Source: CollecTor — fetched 2026-03-16 17:45:08

Measured By
2/6 Bandwidth Authorities
Not measured by: bastet, longclaw, maatuska, moria1
Median Measurement
240.0 bit/s
Min / Max
80 bit/s / 240 bit/s
Deviation
160 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (3th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0000% (1th pctl)

Uptime and Stability

Uptime Metrics
Current Status
UP 4h 41m 15s 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 46m 39s ago (2026-03-16 14:00:00)
Last Seen
2h 46m 39s ago (2026-03-16 15:00:00)
Last Restarted
4h 41m 15s ago (2026-03-16 13:05:24)
Last Changed Address
2026-03-16 14:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-03-16 10: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 
5313F5948F308EB4CCBE25C2EFFE6D2988B2AD73 (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 47.151.129.189:*
accept *:*

Last fetch was at Mon, 16 Mar 2026 17:46:38 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-03-16 17:45: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 Running, Valid, V2Dir, Exit 245.8 Kbit/s | 816.0 Kbit/s 245.8 Kbit/s | 208.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 58.0d 0.2d | 11.8d 100.0% | 98.0% 0.1d | 1.0d 2026-03-16 13:07:42 240 bit/s
dannenberg (DE) Yes Yes Yes — N Yes Running, Valid, V2Dir, Exit 245.8 Kbit/s | 816.0 Kbit/s 245.8 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 11.7d 0.2d | 12.7d 100.0% | 98.0% 0.1d | 1.0d 2026-03-16 13:07:42 240 bit/s
dizum (NL) Yes Yes Yes — N Yes Running, Valid, V2Dir, Exit 245.8 Kbit/s | 816.0 Kbit/s 245.8 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 43.4d 0.2d | 9.7d 100.0% | 98.0% 0.1d | 1.0d 2026-03-16 13:07:42 240 bit/s
faravahar (US) Yes Yes Yes — N Yes Running, Valid, V2Dir, Exit 245.8 Kbit/s | 816.0 Kbit/s 245.8 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 54.0d 0.2d | 12.7d 100.0% | 98.0% 0.1d | 1.0d 2026-03-16 13:07:42 240 bit/s
gabelmoo (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 245.8 Kbit/s | 816.0 Kbit/s 245.8 Kbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 58.6d 0.2d | 12.7d 100.0% | 98.0% 0.1d | 1.0d 2026-03-16 13:07:42 80 bit/s
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 245.8 Kbit/s | 816.0 Kbit/s 245.8 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 62.0d 0.2d | 12.7d 100.0% | 98.0% 0.1d | 1.0d 2026-03-16 13:07:42 240 bit/s
maatuska (SE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 245.8 Kbit/s | 816.0 Kbit/s 245.8 Kbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 41.5d 0.2d | 12.6d 100.0% | 98.0% 0.1d | 1.0d 2026-03-16 13:07:42 240 bit/s
moria1 (US) No — — — Y No — — — — — — — — — — —
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 245.8 Kbit/s | 816.0 Kbit/s 245.8 Kbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 55.9d 0.2d | 13.3d 100.0% | 98.0% 0.1d | 1.0d 2026-03-16 13:07:42 88 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.