Tor Relays :: TheBestRelayNick3

View Relay "TheBestRelayNick3"

Fingerprint: `8A655EC10A103C36174B7E5B0908490CDD68F192` | Family: 1 relay | AS577 | Canada | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, V2Dir (3)
BW Verified: 2/7 BW Auths Measured 96 bit/s Median
Stability: Not Overloaded | DOWN 5d 22h 45m ago

Reachability: IPv4: 9/9 (Directory Auths)
First Seen: 3y 7mo 2w ago
BW Weight: 0.00% of Network | 98 Kbit/s Observed By Relay
Version: 0.4.9.10 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 1.9% 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 6.0 days is below 8 days requirement (2.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.
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 1.9% 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.
Low bandwidth authority measurements : Only 2/7 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.

Connectivity and Location

Addresses

OR Address: bras-base-toroon2643w-grc-01-142-198-35-21.dsl.bell.ca
142.198.35.21:9001

Reachability (Directory Authorities)

IPv4: 9/9

Location

Country: Canada
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS577
AS Name: Bell Canada (BGP.tools)
AS Rarity: Legendary (score: 4/5, <0.05% consensus weight, 5 operators)

Flags and Eligibility

Current Flags (3): Running, Valid, V2Dir

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	Below (0/9 DA)	98.1 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 (1/9 DA)	Median: 0.2d (1/9 DA above threshold) Min/Max: 0.2d / 20630.1d (9/9 DA, Voting / Total Eligible)	≥20.7d - 57.6d (varies) (≥5/9 DA) [Stricter] moria1: ≥936.0d
Stable	Uptime	Meets (9/9 DA)	6.2d (R)	≥4.3d - 4.7d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Below (1/9 DA)	1/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 (1/9 DA)	1/9 DA assigned Stable	≥20.7d - 57.6d (varies) (≥5/9 DA) [Stricter] moria1: ≥936.0d
	Prereq: V2Dir	Meets (9/9 DA)	9/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Below (0/9 DA)	Median: 1.9% (0/9 DA above threshold) Min/Max: 1.8% / 3.5% (9/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Meets (8/9 DA)	Median: 6.0d (0/9 DA above threshold) Min/Max: 3.9d / 6.0d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.8d
Guard	Prereq: Fast	Below (1/9 DA)	1/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 (1/9 DA)	1/9 DA assigned Stable	≥20.7d - 57.6d (varies) (≥5/9 DA) [Stricter] moria1: ≥936.0d
	Prereq: V2Dir	Meets (9/9 DA)	9/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Below (0/9 DA)	Median: 1.9% (0/9 DA above threshold) Min/Max: 1.8% / 3.5% (9/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Below (0/9 DA) (need 2.0 more days)	Median: 6.0d (0/9 DA above threshold) Min/Max: 3.9d / 6.0d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Below (0/9 DA)	98.1 Kbit/s (R)	≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-312.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-07-01 23:45:03).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 98.06 Kbit/s
Advertised Bandwidth: 98.06 Kbit/s
Rate Limit: 83.89 Mbit/s
Burst Limit: 83.89 Mbit/s
Total Data: 12 TB (5 years)
1mo: 633 MB | 6mo: 633 MB | 1y: 2.7 TB | 5y: 12 TB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-07-01 23:45:03

Measured By: 2/7 Bandwidth Authorities
Not measured by: bastet, dannenberg, gabelmoo, longclaw, maatuska
Median Measurement: 96 bit/s
Min / Max: 8 bit/s / 26.0 Kbit/s
Deviation: 26.0 Kbit/s [Warning] High variation

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

Uptime and Stability

Uptime Metrics

Current Status: DOWN 5d 22h 45m ago
Overall Uptime (1M/6M/1Y/5Y): 0.0%/0.0%/13.4%/11.8%
Flag Uptime (1M/6M/1Y/5Y): Matches Overall Uptime (0.0%/0.0%/13.4%/11.8%)
Hibernating: No

Timestamps

First Seen: 3y 7mo 2w ago (2022-11-19 00:00:00)
Last Seen: 5d 22h 45m ago (2026-06-26 02:00:00)
Last Restarted: 6d 4h 57m ago (2026-06-25 19:47:59)
Last Changed Address: 2026-06-25 22:00:00

Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-07-01 16:00 UTC

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: none

Family Configuration

Family Support: None — No family membership configured

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Member: 1

8A655EC10A103C36174B7E5B0908490CDD68F192 (this relay)

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

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

Exit Health & Policy

DNS Health

Not an exit relay — DNS health testing does not apply.

IPv4 Exit Policy Summary

reject: 
  1-65535

Full Exit Policy

reject *:*

Last fetch was at Thu, 02 Jul 2026 00:45:33 GMT.

Consensus Evaluation

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

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	No	—	Y	Yes	Valid, V2Dir	98.1 Kbit/s \| 816.0 Kbit/s	98.1 Kbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	1.9% \| 98%	6.0d \| 8d	0.2d \| 53.6d	6.2d \| 4.7d	1.9% \| 98.0%	6.0d \| 1.0d	2026-07-01 21:01:39	96 bit/s
dannenberg (DE)	Yes	Yes	No	—	Y	Yes	Valid, V2Dir	98.1 Kbit/s \| 816.0 Kbit/s	98.1 Kbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	1.9% \| 98%	6.0d \| 8d	0.2d \| 20.7d	6.2d \| 4.7d	1.9% \| 98.0%	6.0d \| 1.0d	2026-07-01 21:01:39	96 bit/s
dizum (NL)	Yes	Yes	No	—	N	Yes	Valid, V2Dir	98.1 Kbit/s \| 816.0 Kbit/s	98.1 Kbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	1.9% \| 98%	6.0d \| 8d	0.2d \| 33.1d	6.2d \| 4.7d	1.9% \| 98.0%	6.0d \| 1.0d	2026-07-01 21:01:39	96 bit/s
faravahar (US)	Yes	Yes	No	—	N	Yes	Valid, V2Dir, Fast	98.1 Kbit/s \| 816.0 Kbit/s	98.1 Kbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	2.0% \| 98%	5.7d \| 8d	0.2d \| 57.6d	6.2d \| 4.5d	2.0% \| 98.0%	5.7d \| 1.0d	2026-07-01 14:58:38	26.0 Kbit/s
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Valid, V2Dir	98.1 Kbit/s \| 816.0 Kbit/s	98.1 Kbit/s \| 312.0 Mbit/s OR 16.0 Mbit/s	3.5% \| 98%	3.9d \| 8d	0.2d \| 60.1d	6.2d \| 4.3d	3.5% \| 98.0%	3.9d \| 1.0d	2026-06-29 20:40:28	26.0 Kbit/s
longclaw (US)	Yes	Yes	No	—	Y	Yes	Valid, V2Dir	98.1 Kbit/s \| 816.0 Kbit/s	98.1 Kbit/s \| 248.0 Mbit/s OR 16.0 Mbit/s	1.9% \| 98%	6.0d \| 8d	0.2d \| 59.5d	6.2d \| 4.7d	1.9% \| 98.0%	6.0d \| 1.0d	2026-07-01 21:01:39	96 bit/s
maatuska (SE)	Yes	Yes	No	—	Y	Yes	Valid, V2Dir	98.1 Kbit/s \| 816.0 Kbit/s	98.1 Kbit/s \| 312.0 Mbit/s OR 16.0 Mbit/s	1.8% \| 98%	6.0d \| 8d	0.2d \| 33.3d	6.2d \| 4.7d	1.8% \| 98.0%	6.0d \| 1.0d	2026-07-01 21:01:39	96 bit/s
moria1 (US)	Yes	Yes	No	—	Y	Yes	Valid, V2Dir, Stable	98.1 Kbit/s \| 8.4 Mbit/s	98.1 Kbit/s \| 256.0 Mbit/s OR 16.0 Mbit/s	2.4% \| 98%	4.6d \| 8d	20630.1d \| 936.0d	6.2d \| 4.7d	2.4% \| 98.0%	4.6d \| 9.8d	2026-07-01 21:01:39	8 bit/s
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Valid, V2Dir	98.1 Kbit/s \| 816.0 Kbit/s	98.1 Kbit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	1.8% \| 98%	6.0d \| 8d	0.2d \| 58.9d	6.2d \| 4.7d	1.8% \| 98.0%	6.0d \| 1.0d	2026-07-01 21:01:39	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.