View Relay "TruthSeeker"

Fingerprint: 88754AF9B6A820614E14FE8F1FEA423179E8097E | Family: 1 relay | niktosn at gmail dot com | AS393552 | United States of America | Windows

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
5/7 BW Auths Measured 880 Kbit/s Median
Stability
Overloaded | UP 4d 10h 33s ago | UP 99% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
BW Weight
0.00% of Network | 4 Mbit/s Observed By Relay
Version
0.4.9.13 Recommended
Issues Detected:
  • Guard: bandwidth below threshold : 0/9 authorities credit this relay with enough bandwidth for Guard (5 needed): at least 16.8 Mbit/s (AuthDirGuardBWGuarantee) or a place in their top 25% (80.0 Mbit/s – 288.0 Mbit/s). bastet, dannenberg, gabelmoo, moria1 and tor26 measured this relay at 784.0 Kbit/s – 2.2 Mbit/s. dizum, longclaw and maatuska used the relay-reported 4.9 Mbit/s.
    Suggestion: Guard requires a bandwidth of at least AuthDirGuardBWGuarantee (16.8 Mbit/s by default) or one in the top 25% of relays, judged by each authority the same way as for Fast. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx.
  • 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.
  • Write Bandwidth Limit Hit : Write rate limit (5 Mbit/s) was hit 16 times. Relay is throttling outbound traffic.
    Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more upload capacity.
  • Read Bandwidth Limit Hit : Read rate limit (5 Mbit/s) was hit 4,112 times. Relay is throttling inbound traffic.
    Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more download capacity.
Notes:

Addresses
OR Address
008-042-076-068.v4.mynextlight.net
8.42.76.68:29443
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
United States of America United States of America
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS393552
AS Name
Longmont Power & Communications (BGP.tools)
AS Rarity
Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

Current Flags (6): Running, Valid, V2Dir, Fast, Stable, HSDir
Eligible Flags (6): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 5/9 | Stable: 9/9 | HSDir: 5/9 | Guard: 0/9 | Exit: 0/9
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 Meets (9/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Partial (5/9 DA) 784.0 Kbit/s – 2.2 Mbit/s (5 DA measured)
4.9 Mbit/s (3 DA relay-reported)
faravahar: not published
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Partial (8/9 DA) Median: 11.6d (9/9 DA above threshold)
Min/Max: 11.5d / 8657.1d (9/9 DA, Voting / Total Eligible)
≥5.4d - 10.6d (varies) (≥5/9 DA)
[Stricter] moria1: ≥9590.6d
Uptime Meets (9/9 DA) 4.4d (R) ≥3.9d - 4.0d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (5/9 DA) 5/9 DA assigned Fast
784.0 Kbit/s – 2.2 Mbit/s (5 DA measured)
4.9 Mbit/s (3 DA relay-reported)
faravahar: not published
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Meets (9/9 DA) 9/9 DA assigned Stable ≥5.4d - 10.6d (varies) (≥5/9 DA)
[Stricter] moria1: ≥9590.6d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (9/9 DA) Median: 99.0% (9/9 DA above threshold)
Min/Max: 98.0% / 99.3% (9/9 DA, Voting / Total Eligible)
≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 20.0d (9/9 DA above threshold)
Min/Max: 9.8d / 20.1d (9/9 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥10.0d
Guard Prereq: Fast Meets (5/9 DA) 5/9 DA assigned Fast
784.0 Kbit/s – 2.2 Mbit/s (5 DA measured)
4.9 Mbit/s (3 DA relay-reported)
faravahar: not published
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Meets (9/9 DA) 9/9 DA assigned Stable ≥5.4d - 10.6d (varies) (≥5/9 DA)
[Stricter] moria1: ≥9590.6d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (9/9 DA) Median: 99.0% (9/9 DA above threshold)
Min/Max: 98.0% / 99.3% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 20.0d (9/9 DA above threshold)
Min/Max: 9.8d / 20.1d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 784.0 Kbit/s – 2.2 Mbit/s (5 DA measured)
4.9 Mbit/s (3 DA relay-reported)
faravahar: not published
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-288.0 Mbit/s) (≥5/9 DA)
Exit Exit Policy Below (0/9 DA) Port 80: No | Port 443: No (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-10-13 08:45:07).

Capacity (Relay Reported)
Observed Bandwidth
4.91 Mbit/s
Advertised Bandwidth
4.91 Mbit/s
Rate Limit
5.24 Mbit/s
Burst Limit
10.49 Mbit/s
Total Data
33 TB (5 years)
1mo: 546 GB | 6mo: 3.0 TB | 1y: 4.6 TB | 5y: 33 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-10-13 08:45:07

Measured By
5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Consensus Weight
880.0 Kbit/s (median of 5 measurements)
Measured Min / Max
784.0 Kbit/s / 2.2 Mbit/s
Deviation
1.4 Mbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0001% of network (5th pctl) | Guard: N/A | Middle: 0.0002% (5th pctl) | Exit: N/A
History

Uptime Metrics
Current Status
UP 4d 10h 33s ago
Overall Uptime (1M/6M/1Y/5Y)
99.0%/97.9%/98.7%/96.8%
Flag Uptime (1M/6M/1Y/5Y)
24.3%/81.2%/90.0%/94.6%
Hibernating
No
Timestamps
First Seen
7y 3mo 2d ago (2019-07-15 04:00:00)
Last Seen
1h 45m 28s ago (2026-10-13 07:00:00)
Last Restarted
4d 10h 33s ago (2026-10-08 22:44:55)
Last Changed Address
2026-04-06 23:00:00
[Warning] OVERLOADED — Rate limits hit W:16 R:4112 (limit: 5 Mbit/s)
General Overload (from /details)
Status
Not Reported

OOM killer, onionskin queue saturation, or TCP port exhaustion. Flag remains 72h after last event (Tor spec 328).

File Descriptor Exhaustion (from /bandwidth)
Status
Not Reported
Rate Limits (from /bandwidth)
Rate Limit
5.24 Mbit/s
Burst Limit
1.3 MB
Write Limit Hit
16 times
Read Limit Hit
4,112 times
Last Reported
15 hours ago
Recommendations
  • Consider increasing RelayBandwidthRate
  • Check if ISP is throttling traffic
History

Operator Identity

Source: AROI Validation API — 2026-10-13 00:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
niktosn at gmail dot com
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1
88754AF9B6A820614E14FE8F1FEA423179E8097E (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Platform
Windows — Tor 0.4.9.13 on Windows 8 [or later]
Version
0.4.9.13 — Recommended
Version Status
Recommended

DNS Health
Not an exit relay — DNS health testing does not apply.
IPv4 Exit Policy Summary
reject: 
  1-65535
IPv6 Exit Policy Summary
None
Full Exit Policy
reject *:*

Last fetch was at Tue, 13 Oct 2026 08:45:27 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-10-13 08:45:07).

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 (BW|T) Guard BW (BW|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 No — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir 1.9 Mbit/s (M) | 816.0 Kbit/s 1.9 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 99.3% | 98% 20.1d | 8d 11.6d | 10.4d 4.4d | 4.1d 99.3% | 98.0% 20.1d | 1.0d 2026-10-12 17:27:18 1.9 Mbit/s (M)
dannenberg (DE) Yes Yes No — Y Yes Running, Valid, V2Dir, Stable 800.0 Kbit/s (M) | 816.0 Kbit/s 800.0 Kbit/s (M) | 288.0 Mbit/s OR 16.8 Mbit/s 99.1% | 98% 20.0d | 8d 11.5d | 5.4d 4.4d | 4.0d 99.1% | 98.0% 20.0d | 1.0d 2026-10-12 17:27:18 800.0 Kbit/s (M)
dizum (NL) Yes Yes No — N Yes Running, Valid, V2Dir, Fast, Stable, HSDir 4.9 Mbit/s (R) | 816.0 Kbit/s 4.9 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.0% | 98% 20.1d | 8d 11.6d | 10.6d 4.4d | 4.0d 99.0% | 98.0% 20.1d | 1.0d 2026-10-12 17:27:18 4.9 Mbit/s (R)
faravahar (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Stable not published | 816.0 Kbit/s not published | 280.0 Mbit/s OR 16.8 Mbit/s 99.1% | 98% 20.1d | 8d 11.6d | 11.4d 4.4d | 4.0d 99.1% | 98.0% 20.1d | 1.0d 2026-10-12 17:27:18 4.9 Mbit/s (R)
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid, V2Dir, Stable 784.0 Kbit/s (M) | 816.0 Kbit/s 784.0 Kbit/s (M) | 264.0 Mbit/s OR 16.8 Mbit/s 99.0% | 98% 20.1d | 8d 11.6d | 10.4d 4.4d | 4.0d 99.0% | 98.0% 20.1d | 1.0d 2026-10-12 17:27:18 784.0 Kbit/s (M)
longclaw (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir 4.9 Mbit/s (R) | 816.0 Kbit/s 4.9 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.0% | 98% 20.0d | 8d 11.6d | 10.9d 4.4d | 4.0d 99.0% | 98.0% 20.0d | 1.0d 2026-10-12 17:27:18 4.9 Mbit/s (R)
maatuska (SE) Yes Yes No — N Yes Running, Valid, V2Dir, Fast, Stable, HSDir 4.9 Mbit/s (R) | 816.0 Kbit/s 4.9 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.0% | 98% 20.0d | 8d 11.5d | 10.3d 4.4d | 4.0d 99.0% | 98.0% 20.0d | 1.0d 2026-10-12 17:27:18 4.9 Mbit/s (R)
moria1 (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Stable 2.2 Mbit/s (M) | 8.4 Mbit/s 2.2 Mbit/s (M) | 208.0 Mbit/s OR 16.8 Mbit/s 98.0% | 98% 9.8d | 8d 8657.1d | 9590.6d 4.4d | 3.9d 98.0% | 98.0% 9.8d | 10.0d 2026-10-12 17:27:18 2.2 Mbit/s (M)
tor26 (AT) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir 880.0 Kbit/s (M) | 816.0 Kbit/s 880.0 Kbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s 99.1% | 98% 20.0d | 8d 11.6d | 10.6d 4.4d | 4.0d 99.1% | 98.0% 20.0d | 1.0d 2026-10-12 17:27:18 880.0 Kbit/s (M)

— = not tested/available • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known • Bandwidth source: (M) bandwidth-scanner measurement, (R) relay-reported, (U) unmeasured, counted as 0

Bandwidth Values Explained:
Measured (M) = An authority's bandwidth-scanner measurement of your relay (Measured= in its vote). An authority that has one uses it for the Fast and Guard flags, and the consensus weight is the median of these measurements when 3 or more authorities have one.
Relay-reported (R) = The bandwidth your relay advertises: the lower of its observed bandwidth and its rate limit, capped at 10 MB/s (Bandwidth= in every vote). An authority without a measurement uses it for flags, unless it has measurements for enough other relays (ignoring-advertised-bws=1); then your relay counts as 0 (U). It sets the consensus weight only when fewer than 3 authorities measured the relay, capped at 20 KB/s (maxunmeasuredbw) while 3 or more authorities publish measurements.
Not published = The authority has no measurement of your relay in its vote and ignores relay-reported bandwidth, yet it voted Fast or its vote has no measurements at all: it judges your relay by a measurement kept from an earlier bandwidth file (0 if none), which its vote doesn't show.
Why different? A low measurement means the bandwidth scanners see your relay underperforming compared with other relays that report a similar speed. Votes list both values in kilobytes per second. Rules: Assigning flags in a vote, Computing a consensus.
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.