View Relay "bkk"

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

Health Status

Consensus
In Consensus (7/7 Directory Auths)
Flags
Running, Valid, V2Dir, Stable, Exit (5)
DNS Health
Healthy (14.0s, 16th percentile) (via exitdnshealth.1aeo.com)
BW Verified
5/6 BW Auths Measured 776 bit/s Median
Stability
Overloaded | UP 1w 1d 18h ago | UP 100% (1M)
Reachability
IPv4: 7/7 (Directory Auths)
First Seen
2w 5d 20h ago
BW Weight
0.00% of Network | 3 Mbit/s Observed By Relay
Version
0.4.9.11 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: bandwidth below threshold : Observed bandwidth 3 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.
  • 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.
  • 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 76 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 145 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=76, Read=145.

Connectivity and Location

Addresses
OR Address
138.197.124.121:443
Exit Address
138.197.124.121
Reachability (Directory Authorities)
IPv4
7/7
Location
Country
United States of America United States of America
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS14061
AS Name
DigitalOcean, LLC (BGP.tools)
AS Rarity
Emerging (score: 1/5, 0.66% consensus weight, 66 operators)

Flags and Eligibility

Current Flags (5): Running, Valid, V2Dir, Stable, Exit
Eligible Flags (5): Running: 7/7 | Valid: 7/7 | V2Dir: 7/7 | Fast: 2/7 | Stable: 7/7 | HSDir: 2/7 | Guard: 0/7 | Exit: 7/7
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (7/7 DA) 7/7 authorities reached relay ≥4/7 DA ORPort reachable
Valid Descriptor Meets (7/7 DA) 7/7 authorities assigned Valid Not blacklisted + valid descriptor (≥4/7 DA)
V2Dir DirPort Available Meets (7/7 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥4/7 DA)
Fast Speed Meets (7/7 DA) 3.5 Mbit/s (R) ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Partial (4/7 DA) Median: 19.8d (6/7 DA above threshold)
Min/Max: 15.0d / 19.8d (7/7 DA, Voting / Total Eligible)		 ≥8.4d - 15.1d (varies) (≥4/7 DA)
[Stricter] moria1: ≥9211.0d
Uptime Meets (7/7 DA) 8.8d (R) ≥8.4d - 8.5d (varies) (≥4/7 DA)
HSDir Prereq: Fast Below (2/7 DA) 2/7 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Meets (7/7 DA) 7/7 DA assigned Stable ≥8.4d - 15.1d (varies) (≥4/7 DA)
[Stricter] moria1: ≥9211.0d
Prereq: V2Dir Meets (7/7 DA) 7/7 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥4/7 DA)
WFU Meets (7/7 DA) Majority: 100.0% (5/7 DA)
Min/Med/Max: 99.0% / 100.0% / 100.0% (7/7 DA, Voting / Total Eligible)		 ≥98.0% (≥4/7 DA)
Time Known Meets (6/7 DA) Median: 19.7d (7/7 DA above threshold)
Min/Max: 8.5d / 19.8d (7/7 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥4/7 DA)
[Stricter] moria1: ≥10.0d
Guard Prereq: Fast Below (2/7 DA) 2/7 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Meets (7/7 DA) 7/7 DA assigned Stable ≥8.4d - 15.1d (varies) (≥4/7 DA)
[Stricter] moria1: ≥9211.0d
Prereq: V2Dir Meets (7/7 DA) 7/7 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥4/7 DA)
WFU Meets (7/7 DA) Majority: 100.0% (5/7 DA)
Min/Med/Max: 99.0% / 100.0% / 100.0% (7/7 DA, Voting / Total Eligible)		 ≥98% (≥4/7 DA)
Time Known Meets (7/7 DA) Median: 19.7d (7/7 DA above threshold)
Min/Max: 8.5d / 19.8d (7/7 DA, Voting / Total Eligible)		 ≥8 days (≥4/7 DA)
Bandwidth Below (0/7 DA) 3.5 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-280.0 Mbit/s (≥4/7 DA)
Exit Exit Policy Meets (7/7 DA) Port 80: Yes | Port 443: Yes (R) Allows ≥1 /8 on ports 80 AND 443 (≥4/7 DA)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-07-19 22:00:24).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
3.47 Mbit/s
Advertised Bandwidth
3.28 Mbit/s
Rate Limit
3.28 Mbit/s
Burst Limit
6.55 Mbit/s
Total Data
55 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-07-19 22:00:24

Measured By
5/6 Bandwidth Authorities
Not measured by: bastet
Median Measurement
776 bit/s
Min / Max
576 bit/s / 3272 bit/s
Deviation
2696 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (4th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0001% (2th pctl)

Uptime and Stability

Uptime Metrics
Current Status
UP 1w 1d 18h ago
Overall Uptime (1M/6M/1Y/5Y)
100.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (100.0%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
2w 5d 20h ago (2026-06-30 03:00:00)
Last Seen
3h 3m 17s ago (2026-07-19 20:00:00)
Last Restarted
1w 1d 18h ago (2026-07-11 04:21:15)
Last Changed Address
2026-06-30 03:00:00
[Warning] OVERLOADED — Rate limits hit W:76 R:145 (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
76 times
Read Limit Hit
145 times
Last Reported
15 hours ago
Recommendations
  • Consider increasing RelayBandwidthRate
  • Check if ISP is throttling traffic

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-07-19 14: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. 14.0s, 16th percentile)
Query Domain
76042615746542e88b387cefd3578ece.d0968ee8.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
3/3 instances succeeded
First Hop
Rem (DE) 47186E3631689057A7EF223ECC5D86918A9E679E
Exit Address Used
138.197.124.121
Per-Instance Results
Cross Validation Attempt 1: Success, 15.7s (cv2_w4)
Cross Validation Attempt 2: Success, 11.1s (cv3_w4)
Cross Validation Attempt 3: Success, 15.2s (cv4_w4)
Tested: 2026-07-19 07:22:54 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
reject: 
  25
  445
  465
  587
  6881-6999
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 138.197.124.121:*
reject *:25
reject *:465
reject *:587
reject *:6881-6999
reject *:445
accept *:*

Last fetch was at Sun, 19 Jul 2026 23:03:07 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-07-19 22:00:24).

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, Fast, Stable, HSDir, Exit 3.5 Mbit/s | 816.0 Kbit/s 3.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 19.8d | 8d 19.8d | 21.3d 8.8d | 8.4d 100.0% | 98.0% 19.8d | 1.0d 2026-07-19 10:21:58 3272 bit/s
dannenberg (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Stable, Exit 3.5 Mbit/s | 816.0 Kbit/s 3.5 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 99.9% | 98% 19.0d | 8d 16.7d | 8.4d 8.8d | 8.5d 99.9% | 98.0% 19.0d | 1.0d 2026-07-19 10:21:58 752 bit/s
dizum (NL) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 3.5 Mbit/s | 816.0 Kbit/s 3.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 19.8d | 8d 19.8d | 13.5d 8.8d | 8.5d 100.0% | 98.0% 19.8d | 1.0d 2026-07-19 10:21:58 3272 bit/s
faravahar (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Stable, Exit 3.5 Mbit/s | 816.0 Kbit/s 3.5 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 99.0% | 98% 17.5d | 8d 15.0d | 14.4d 8.8d | 8.5d 99.0% | 98.0% 17.5d | 1.0d 2026-07-19 10:21:58 696 bit/s
maatuska (SE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Stable, Exit 3.5 Mbit/s | 816.0 Kbit/s 3.5 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 19.7d | 8d 19.7d | 15.1d 8.8d | 8.5d 100.0% | 98.0% 19.7d | 1.0d 2026-07-19 10:21:58 776 bit/s
moria1 (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Stable, Exit 3.5 Mbit/s | 8.4 Mbit/s 3.5 Mbit/s | 208.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 8.5d | 8d 19.8d | 9211.0d 8.8d | 8.5d 100.0% | 98.0% 8.5d | 10.0d 2026-07-19 10:21:58 1440 bit/s
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Stable, Exit 3.5 Mbit/s | 816.0 Kbit/s 3.5 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 19.8d | 8d 19.8d | 21.1d 8.8d | 8.5d 100.0% | 98.0% 19.8d | 1.0d 2026-07-19 10:21:58 576 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.