View Relay "bkk"

Fingerprint: `D0968EE8B66665E15B8204AACF310E820AF8D799` | Family: 1 relay | nyc@bikerider.com | AS14061 | United States of America | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, V2Dir, Fast, Stable, Exit (6)
DNS Health: Healthy (17.5s, 58th percentile) (via exitdnshealth.1aeo.com)
BW Verified: 4/6 BW Auths Measured 3272 bit/s Median
Stability: Overloaded | UP 1d 3h 11m ago | UP 99% (1M)

Reachability: IPv4: 9/9 (Directory Auths)
First Seen: 1mo 2w 2d ago
BW Weight: 0.00% of Network | 3 Mbit/s Observed By Relay
Version: 0.4.9.11 Recommended

Issues Detected:

Guard: bandwidth below threshold : Observed bandwidth 4 Mbit/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.
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 (3 Mbit/s) was hit 31 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 (3 Mbit/s) was hit 70 times. Relay is throttling inbound traffic.
Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more download capacity.

Notes:

Rate Limit Configuration: Configured limits: Rate=3 Mbit/s, Burst=819 KB. Limits hit: Write=31, Read=70.

Connectivity and Location

Addresses

OR Address: 138.197.124.121:443
Exit Address: 138.197.124.121

Reachability (Directory Authorities)

IPv4: 9/9

Location

Country: United States of America
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS14061
AS Name: DigitalOcean, LLC (BGP.tools)
AS Rarity: Rare (score: 2/5, 0.45% consensus weight, 54 operators)

Flags and Eligibility

Current Flags (6): Running, Valid, V2Dir, Fast, Stable, Exit

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	Meets (9/9 DA)	3.7 Mbit/s (R)	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s
Stable	MTBF	Partial (8/9 DA)	Median: 19.3d (8/9 DA above threshold) Min/Max: 10.9d / 2831.2d (9/9 DA, Voting / Total Eligible)	≥8.2d - 11.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥8443.5d
Stable	Uptime	Below (0/9 DA)	1.1d (R)	≥6.8d - 7.7d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (5/9 DA)	5/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	Meets (9/9 DA)	9/9 DA assigned Stable	≥8.2d - 11.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥8443.5d
	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: 100.0% (9/9 DA above threshold) Min/Max: 99.6% / 100.0% (9/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Meets (8/9 DA)	Median: 22.4d (9/9 DA above threshold) Min/Max: 9.5d / 46.8d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.8d
Guard	Prereq: Fast	Meets (5/9 DA)	5/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	Meets (9/9 DA)	9/9 DA assigned Stable	≥8.2d - 11.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥8443.5d
	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: 100.0% (9/9 DA above threshold) Min/Max: 99.6% / 100.0% (9/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 22.4d (9/9 DA above threshold) Min/Max: 9.5d / 46.8d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Below (0/9 DA)	3.7 Mbit/s (R)	≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-328.0 Mbit/s (≥5/9 DA)
Exit	Exit Policy	Meets (9/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-08-16 00:15:11).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 3.65 Mbit/s
Advertised Bandwidth: 3.28 Mbit/s
Rate Limit: 3.28 Mbit/s
Burst Limit: 6.55 Mbit/s
Total Data: 343 GB (6 months)
1mo: 290 GB | 6mo: 343 GB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-08-16 00:15:11

Measured By: 4/6 Bandwidth Authorities
Not measured by: faravahar, longclaw
Median Measurement: 3272 bit/s
Min / Max: 400 bit/s / 3272 bit/s
Deviation: 2872 bit/s [Warning] High variation

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

Uptime and Stability

Uptime Metrics

Current Status: UP 1d 3h 11m ago
Overall Uptime (1M/6M/1Y/5Y): 99.9%/99.9%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y): Matches Overall Uptime (99.9%/99.9%/0.0%/0.0%)
Hibernating: No

Timestamps

First Seen: 1mo 2w 2d ago (2026-06-30 03:00:00)
Last Seen: 1h 17m 33s ago (2026-08-16 00:00:00)
Last Restarted: 1d 3h 11m ago (2026-08-14 22:06:29)
Last Changed Address: 2026-06-30 03:00:00

[Warning] OVERLOADED — Rate limits hit W:31 R:70 (limit: 3 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: 3.28 Mbit/s
Burst Limit: 819 KB
Write Limit Hit: 31 times
Read Limit Hit: 70 times
Last Reported: 10 hours ago

Recommendations

Consider increasing RelayBandwidthRate
Check if ISP is throttling traffic

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-08-15 17:00 UTC

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: nyc@bikerider.com

Family Configuration

Family Support: None — No family membership configured

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Member: 1

D0968EE8B66665E15B8204AACF310E820AF8D799 (this relay)

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

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

Exit Health & Policy

DNS Health

Status

Healthy (avg. 17.5s, 58th percentile)

Query Domain

a65fe7c1028c4c8bb3d096d6f743e62b.d0968ee8.tor.exit.validator.1aeo.com

DNS Result

Resolved to 64.65.4.1

Cross-Validation

4/4 instances succeeded

First Hop

TORKeFFORG34 (SE) 11DEFFF912BA94402D37F4BDF0440A361F837F65

Exit Address Used

138.197.124.121

Per-Instance Results

Cross Validation Attempt 1:	Success, 13.0s	(cv1_w4)
Cross Validation Attempt 2:	Success, 19.0s	(cv2_w4)
Cross Validation Attempt 3:	Success, 13.8s	(cv3_w4)
Cross Validation Attempt 4:	Success, 24.3s	(cv4_w4)

Tested: 2026-08-15 07:21:39 UTC

Source: exitdnshealth.1aeo.com

IPv4 Exit Policy Summary

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 138.197.124.121:*
reject *:25
reject *:465
reject *:587
reject *:6881-6999
reject *:445
accept *:*

Last fetch was at Sun, 16 Aug 2026 01:17:30 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-08-16 00:15:11).

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	—	N	Yes	Running, Valid, V2Dir, Fast, Stable, Exit	3.7 Mbit/s \| 816.0 Kbit/s	3.7 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	99.6% \| 98%	17.3d \| 8d	10.9d \| 8.2d	1.1d \| 6.8d	99.6% \| 98.0%	17.3d \| 1.0d	2026-08-15 16:06:34	3272 bit/s
dannenberg (DE)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, V2Dir, Stable, Exit	3.7 Mbit/s \| 816.0 Kbit/s	3.7 Mbit/s \| 328.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	22.4d \| 8d	19.1d \| 11.4d	1.1d \| 7.7d	100.0% \| 98.0%	22.4d \| 1.0d	2026-08-15 16:06:34	512 bit/s
dizum (NL)	Yes	Yes	Yes	—	N	Yes	Running, Valid, V2Dir, Fast, Stable, Exit	3.7 Mbit/s \| 816.0 Kbit/s	3.7 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	46.8d \| 8d	46.8d \| 11.2d	1.1d \| 7.6d	100.0% \| 98.0%	46.8d \| 1.0d	2026-08-15 16:06:34	3272 bit/s
faravahar (US)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, V2Dir, Fast, Stable, Exit	3.7 Mbit/s \| 816.0 Kbit/s	3.7 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	44.2d \| 8d	43.8d \| 11.0d	1.1d \| 7.7d	100.0% \| 98.0%	44.2d \| 1.0d	2026-08-15 16:06:34	3272 bit/s
gabelmoo (DE)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, V2Dir, Stable, Exit	3.7 Mbit/s \| 816.0 Kbit/s	3.7 Mbit/s \| 304.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	26.1d \| 8d	26.1d \| 12.8d	1.1d \| 7.7d	100.0% \| 98.0%	26.1d \| 1.0d	2026-08-15 16:06:34	400 bit/s
longclaw (US)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, V2Dir, Fast, Stable, Exit	3.7 Mbit/s \| 816.0 Kbit/s	3.7 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	20.6d \| 8d	17.6d \| 16.5d	1.1d \| 7.7d	100.0% \| 98.0%	20.6d \| 1.0d	2026-08-15 16:06:34	3272 bit/s
maatuska (SE)	Yes	Yes	Yes	—	N	Yes	Running, Valid, V2Dir, Fast, Stable, Exit	3.7 Mbit/s \| 816.0 Kbit/s	3.7 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	22.3d \| 8d	19.2d \| 11.4d	1.1d \| 7.6d	100.0% \| 98.0%	22.3d \| 1.0d	2026-08-15 16:06:34	3272 bit/s
moria1 (US)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, V2Dir, Stable, Exit	3.7 Mbit/s \| 8.4 Mbit/s	3.7 Mbit/s \| 232.0 Mbit/s OR 16.0 Mbit/s	99.9% \| 98%	9.5d \| 8d	2831.2d \| 8443.5d	1.1d \| 7.0d	99.9% \| 98.0%	9.5d \| 9.8d	2026-08-15 16:06:34	1040 bit/s
tor26 (AT)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, V2Dir, Stable, Exit	3.7 Mbit/s \| 816.0 Kbit/s	3.7 Mbit/s \| 304.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	22.5d \| 8d	19.3d \| 12.2d	1.1d \| 7.7d	100.0% \| 98.0%	22.5d \| 1.0d	2026-08-15 16:06:34	456 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.