Tor Relays :: forest35

View Relay "forest35"

Family: 1 relay | [email protected] | AS63949 | United States of America | Linux

Health Status

Consensus: In Consensus (5/9 Directory Auths)
Flags: Running, V2Dir, Valid (3)
BW Verified: 1/6 BW Auths Measured 28 Kbit/s Median
Stability: Not Overloaded | UP 1d 5h 13m ago

Reachability: IPv4: 5/9 | v6: 3/7 (Directory Auths)
First Seen: 1d 14h 47m ago
BW Weight: 0.00% of Network | 28 Mbit/s Observed By Relay
Version: 0.4.8.21 Recommended

Issues Detected:

Guard: Time Known below threshold : Time Known 1.6 days is below 8 days requirement (6.4 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.
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: 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.
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.
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 1/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: 5/9 authorities can reach this relay

Connectivity and Location

Addresses

OR Address: 66-228-32-180.ip.linodeusercontent.com
66.228.32.180:9001
[2600:3c03::2000:78ff:fea2:701a]:9001

Reachability (Directory Authorities)

IPv4: 5/9
IPv6: 3/7 (2 don't test)

Location

Country: United States of America
Interactive Map: View on Interactive Map

Autonomous System

AS Number: AS63949
AS Name: Akamai Technologies, Inc. (BGP.tools)

Flags and Eligibility

Current Flags (3): Running, Valid, V2Dir

Eligibility Flag Vote Details

Flag	Metric	Status	Relay Value	Threshold Required
Fast	Speed	Meets (≥100 KB/s)	28.5 Mbit/s (R)	≥800.0 Kbit/s (guarantee) OR top 7/8 [Stricter] moria1: ≥8.4 Mbit/s
Stable	MTBF	Below	Median: 1.6d (0/9 DA above threshold) Min/Max: 1.6d / 1.6d (5/9 DA, Voting / Total Eligible)	≥22.3d - 53.9d (varies) [Stricter] moria1: ≥403.9d
Stable	Uptime	Below	1.2d (R)	≥10.0d - 10.8d (varies)
HSDir	Prereq: Stable	Below	0/9 authorities assigned Stable flag	≥5/9 authorities
	Prereq: Fast	Below	4/9 authorities assigned Fast flag	≥5/9 authorities
	WFU	Meets	Majority: 100.0% (5/9 DA)	≥98.0%
	Time Known	Below	Median: 1.6d (0/9 DA above threshold) Min/Max: 1.6d / 1.6d (5/9 DA, Voting / Total Eligible)	≥1.0d (most) [Stricter] moria1: ≥9.8d
Guard	Prereq: Fast	Below	4/9 authorities assigned Fast flag	≥5/9 authorities
	Prereq: Stable	Below	0/9 authorities assigned Stable flag	≥5/9 authorities
	Prereq: V2Dir	Meets	5/9 authorities assigned V2Dir flag	≥5/9 authorities
	WFU	Meets	Majority: 100.0% (5/9 DA)	≥98% (all authorities)
	Time Known	Below (need 6.4 more days)	Median: 1.6d (0/9 DA above threshold) Min/Max: 1.6d / 1.6d (5/9 DA, Voting / Total Eligible)	≥8 days (all authorities)
	Bandwidth	Meets (≥2 MB/s)	28.5 Mbit/s (R)	≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-01-29 11:45:07).

Last fetch was at Thu, 29 Jan 2026 11:45:43 GMT.

Nickname

forest35

Fingerprint

22B71D9E049AFFCB85369A35FF06B82B4A1E9895

AROI (?)

none

Contact

[email protected]

IPv4 Exit Policy Summary

reject: 
  1-65535

IPv6 Exit Policy Summary

none

Exit Policy

reject *:*

Effective Family Member: 1

22B71D9E049AFFCB85369A35FF06B82B4A1E9895

Alleged Family Members: 0

none

Indirect Family Members: 0

none

Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit): 28.45 Mbit/s | 28.45 Mbit/s| 8.59 Gbit/s| 8.59 Gbit/s Not Measured
Network Participation (Consensus Weight | Guard | Middle | Exit): 0.00% | N/A | 0.00% | N/A
OR Address: 66-228-32-180.ip.linodeusercontent.com | 66.228.32.180:9001, [2600:3c03::2000:78ff:fea2:701a]:9001
Exit Address: none
Dir Address: none
Country: United States of America
Interactive Map: View on Interactive Map
Autonomous System (AS Number | AS Name): AS63949 | Akamai Technologies, Inc. (BGP.tools)
Flags: 3: Running V2Dir Valid
Flag Uptime (1M/6M/1Y/5Y): Match Overall Uptime (0.0%/0.0%/0.0%/0.0%)
Uptime (1M/6M/1Y/5Y): 0.0%/0.0%/0.0%/0.0%
Uptime / Downtime: UP 1d 5h 13m ago
Seen (First | Last): 1d 14h 47m ago (2026-01-27 21:00:00) | 1h 47m 12s ago (2026-01-29 10:00:00)
Last Restarted: 1d 5h 14m ago (2026-01-28 06:32:29)
Last Changed Address or Port: 2026-01-27 21:00:00
Hibernating: No
Platform (Short | Long): Linux | Tor 0.4.8.21 on Linux
Version (Running | Recommended | Status): 0.4.8.21 | Yes | recommended

Consensus Evaluation

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

Consensus Status (need ≥5/9): In Consensus — 5/9 authorities voted.
Flag Eligibility (need ≥5/9 for flag): Running: 5/9 | Valid: 5/9 | V2Dir: 5/9 | Fast: 4/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9
Reachability: IPv4: 5/9 | IPv6: 3/7 (2 don't test)
Consensus Weight (Dir. Auth.): Median: 28.4 Kbit/s | Min: 8 bit/s | Max: 28.4 Kbit/s [Warning] High deviation
Identified Issues:
- Guard: Time Known below threshold: Time Known 1.6 days is below 8 days requirement (6.4 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.
- 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: 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.
- 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.
- 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 1/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: 5/9 authorities can reach this relay

Summary: Your Relay vs Consensus

Green = meets threshold, Red = below threshold, Yellow = partial.

Metric	Dir Auth Measured	Dir Auth Threshold	Status
In Consensus (Dir. Auth.)	5/9 authorities	≥5/9 (majority)	IN CONSENSUS
Running (IPv4 Reachable)	5/9 authorities reached this relay	≥5/9 (majority)	RUNNING
Valid	5/9 (Running + Valid Descriptor)	≥5/9 (majority)	VALID
Consensus Weight (Dir. Auth.)	28.4 Kbit/s (median)	N/A (no threshold, used for path selection)	—
Guard WFU (Dir. Auth., guard-wfu)	100.0%	≥98% (all authorities)	MEETS
Guard TK (Dir. Auth., tk)	1.6 days	≥8 days (all authorities)	BELOW - need 6.4 more days
Guard BW (Relay Reported)	28.5 Mbit/s	≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s	MEETS - ≥2 MB/s guarantee
Stable Uptime (Relay Reported)	1.2d	≥10.0d - 10.8d (typical)	BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf)	2 days	≥22.3d - 53.9d (typical) [Stricter] moria1: ≥403.9d	BELOW - 0/9
Fast Speed (Relay Reported)	28.5 Mbit/s	≥800.0 Kbit/s (guarantee) OR ≥816.0 Kbit/s (typical) [Stricter] moria1: ≥8.4 Mbit/s	MEETS - ≥100 KB/s guarantee
HSDir WFU (Dir. Auth., wfu)	100.0%	≥98.0% (from all auths)	BELOW - 0/9
HSDir TK (Dir. Auth., tk)	1.6 days	≥1.0d (8/9 auths) [Stricter] moria1: ≥9.8d	BELOW - 0/9
IPv6 Reachable (Dir. Auth.)	3/7 tested	≥4/7 (majority)	PARTIAL

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	BW Scan (Authority)	v4	v6	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)	No	—	Y	No	—	—	—	—	—	—	—	—	—	—	—	—
dannenberg (DE)	Yes	Yes	N	Yes	Yes	Running, Valid, V2Dir, Fast	28.5 Mbit/s \| 816.0 Kbit/s	28.5 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	1.6d \| 8d	1.6d \| 22.3d	1.2d \| 10.8d	100.0% \| 98.0%	1.6d \| 1.0d	2026-01-28 20:02:49	28.4 Kbit/s
dizum (NL)	Yes	Yes	N	Yes	—	Running, Valid, V2Dir, Fast	28.5 Mbit/s \| 816.0 Kbit/s	28.5 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	1.6d \| 8d	1.6d \| 34.8d	1.2d \| 10.9d	100.0% \| 98.0%	1.6d \| 1.0d	2026-01-28 20:02:49	28.4 Kbit/s
faravahar (US)	Yes	Yes	N	Yes	Yes	Running, Valid, V2Dir, Fast	28.5 Mbit/s \| 816.0 Kbit/s	28.5 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	1.6d \| 8d	1.6d \| 47.4d	1.2d \| 10.0d	100.0% \| 98.0%	1.6d \| 1.0d	2026-01-28 20:02:49	28.4 Kbit/s
gabelmoo (DE)	No	—	Y	No	—	—	—	—	—	—	—	—	—	—	—	—
longclaw (US)	Yes	Yes	Y	Yes	—	Running, Valid, V2Dir, Fast	28.5 Mbit/s \| 816.0 Kbit/s	28.5 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	1.6d \| 8d	1.6d \| 55.1d	1.2d \| 10.2d	100.0% \| 98.0%	1.6d \| 1.0d	2026-01-28 20:02:49	28.4 Kbit/s
maatuska (SE)	No	—	Y	No	—	—	—	—	—	—	—	—	—	—	—	—
moria1 (US)	No	—	Y	No	—	—	—	—	—	—	—	—	—	—	—	—
tor26 (AT)	Yes	Yes	Y	Yes	Yes	Running, Valid, V2Dir	28.5 Mbit/s \| 816.0 Kbit/s	28.5 Mbit/s \| 288.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	1.6d \| 8d	1.6d \| 55.8d	1.2d \| 11.9d	100.0% \| 98.0%	1.6d \| 1.0d	2026-01-28 20:02:49	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). This is your relay's self-reported uptime from its 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.