View Relay "bkk"
Fingerprint: D0968EE8B66665E15B8204AACF310E820AF8D799 |
Family: 1 relay
|
nyc@bikerider.com |
AS14061
|
United States of America
|
Linux
- Consensus
- In Consensus (9/9 Directory Auths)
- DNS Health
- Healthy (16.0s, 58th percentile) (via exitdnshealth.1aeo.com)
- BW Verified
- 6/7 BW Auths Measured 576 Kbit/s Median
- Stability
- Overloaded | UP 4d 1h 7m ago | UP 100% (1M)
- Reachability
- IPv4: 9/9 | v6: None configured(Directory Auths)
- BW Weight
- 0.00% of Network | 3 Mbit/s Observed By Relay
- Version
- 0.4.9.15 Recommended
-
Not getting the Fast flag
: Only 4/9 authorities vote Fast (5 needed). dannenberg, gabelmoo, longclaw, moria1 and tor26 measured this relay at 448.0 Kbit/s – 1.2 Mbit/s, below the Fast threshold (816.0 Kbit/s; moria1: 8.4 Mbit/s). Its consensus weight, the median of the 6 bandwidth-scanner measurements, is 576.0 Kbit/s.
Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports. A low measurement means the scanners see your relay underperforming compared with other relays that report a similar speed. Clients only build circuits through Fast relays, so a relay near the threshold can gain and lose most of its traffic from one hourly consensus to the next. -
Guard: requires Fast flag
: Guard flag requires having the Fast flag first
Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports. -
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 – 248.0 Mbit/s). E30CF7B3, dannenberg, gabelmoo, longclaw, moria1 and tor26 measured this relay at 448.0 Kbit/s – 1.8 Mbit/s. dizum, faravahar and maatuska used the relay-reported 3.3 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. -
HSDir: requires Fast flag
: HSDir flag requires having the Fast flag first
Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports. -
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 counter is 110 (configured rate 3.28 Mbit/s). Read and write counters increment at most once per minute per direction. They are not a count of blocked connections, the duration of throttling, or necessarily the number of events in the last 24 hours.
Suggestion: Inspect BandwidthRate and BandwidthBurst (the values reported with this hit), any relay-specific caps such as RelayBandwidthRate and RelayBandwidthBurst, the intended bandwidth budget, and actual uplink headroom. A rate-limit report is not evidence of ISP throttling. After checking that evidence and the capacity you meant to offer, review whether those limits should change. MetricsPort: tor_relay_load_global_rate_limit_reached_total{side="read"} and {side="write"}. Increases indicate additional global token-bucket limit events. -
Read Bandwidth Limit Hit
: Read rate-limit counter is 123 (configured rate 3.28 Mbit/s). Read and write counters increment at most once per minute per direction. They are not a count of blocked connections, the duration of throttling, or necessarily the number of events in the last 24 hours.
Suggestion: Inspect BandwidthRate and BandwidthBurst (the values reported with this hit), any relay-specific caps such as RelayBandwidthRate and RelayBandwidthBurst, the intended bandwidth budget, and actual uplink headroom. A rate-limit report is not evidence of ISP throttling. After checking that evidence and the capacity you meant to offer, review whether those limits should change. MetricsPort: tor_relay_load_global_rate_limit_reached_total{side="read"} and {side="write"}. Increases indicate additional global token-bucket limit events.
- Rate Limit Configuration: Configured limits: Rate=3.28 Mbit/s, Burst=819 KB. Counters: Write=110, Read=123. These values are BandwidthRate and BandwidthBurst from the extra-info descriptor. RelayBandwidthRate and RelayBandwidthBurst are additional torrc caps, not the names of these values. Burst is a quantity of bytes.
Suggestion: Inspect BandwidthRate and BandwidthBurst (the values reported with this hit), any relay-specific caps such as RelayBandwidthRate and RelayBandwidthBurst, the intended bandwidth budget, and actual uplink headroom. A rate-limit report is not evidence of ISP throttling. After checking that evidence and the capacity you meant to offer, review whether those limits should change. MetricsPort: tor_relay_load_global_rate_limit_reached_total{side="read"} and {side="write"}. Increases indicate additional global token-bucket limit events.
Addresses
- OR Address
- 138.197.124.121:443
- Exit Address
- 138.197.124.121
Reachability (Directory Authorities)
- IPv4
- 9/9
- IPv6
- None configured
Location
- Country
-
United States of America
- Interactive Map
- View in RouteFluxMap
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 (4/9 DA) | 448.0 Kbit/s – 1.8 Mbit/s (6 DA measured) 3.3 Mbit/s (3 DA relay-reported) |
≥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: 46.3d (8/9 DA above threshold) Min/Max: 6.8d / 122.5d (9/9 DA, Voting / Total Eligible) |
≥2.3d - 8.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥12669.7d |
| Uptime | Below (0/9 DA) | 4.0d (R) | ≥5.0d - 5.1d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Below (4/9 DA) | 4/9 DA assigned Fast 448.0 Kbit/s – 1.8 Mbit/s (6 DA measured) 3.3 Mbit/s (3 DA relay-reported) |
≥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 | ≥2.3d - 8.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥12669.7d |
|
| Prereq: V2Dir | Meets (9/9 DA) | 9/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| Uptime | Meets (9/9 DA) | 4.0d (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.7d Time Known |
|
| Guard | Prereq: Fast | Below (4/9 DA) | 4/9 DA assigned Fast 448.0 Kbit/s – 1.8 Mbit/s (6 DA measured) 3.3 Mbit/s (3 DA relay-reported) |
≥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 | ≥2.3d - 8.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥12669.7d |
|
| 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/Med/Max: 99.4% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible) |
≥98% (≥5/9 DA) | |
| Time Known | Meets (9/9 DA) | Median: 35.2d (9/9 DA above threshold) Min/Max: 6.8d / 122.5d (9/9 DA, Voting / Total Eligible) |
≥8 days; E30CF7B3: ≥5 days 10 hours 41 minutes 56 seconds (≥5/9 DA) | |
| Bandwidth | Below (0/9 DA) | 448.0 Kbit/s – 1.8 Mbit/s (6 DA measured) 3.3 Mbit/s (3 DA relay-reported) |
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-248.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-11-20 08:45:05).
Capacity (Relay Reported)
- Observed Bandwidth
- 3.44 Mbit/s
- Advertised Bandwidth
- 3.28 Mbit/s
- Rate Limit
- 3.28 Mbit/s
- Burst Limit
- 6.55 Mbit/s
- Total Data
-
1.7 TB
(6 months)
1mo: 341 GB | 6mo: 1.7 TB
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-20 08:45:05
- Measured By
-
6/7
Bandwidth Authorities
Not measured by: faravahar - Consensus Weight
- 576.0 Kbit/s (median of 6 measurements)
- Measured Min / Max
- 448.0 Kbit/s / 1.8 Mbit/s
- Deviation
- 1.3 Mbit/s [Warning] High variation
History
Uptime Metrics
- Current Status
- UP 4d 1h 7m ago
- Overall Uptime (1M/6M/1Y/5Y)
- 100.0%/100.0%/0.0%/0.0%
- Flag Uptime (1M/6M/1Y/5Y)
- Matches Overall Uptime (100.0%/100.0%/0.0%/0.0%)
- Hibernating
- No
Timestamps
- First Seen
- 4mo 3w 2d ago (2026-06-30 03:00:00)
- Last Seen
- 1h 45m 32s ago (2026-11-20 08:00:00)
- Last Restarted
- 4d 1h 7m ago (2026-11-16 08:38:12)
- Last Changed Address
- 2026-06-30 03:00:00
Evaluated 2026-11-20 09:45 UTC. /details snapshot 2026-11-20 08:00:00 UTC (cached 37s ago). /bandwidth snapshot 2026-11-20 02:00:00 UTC (cached 6h 30m ago).
Reported timestamps use hour precision, so the displayed minute is not an exact incident time.
General Overload (from /details)
- Status
- No general overload report in available data
File Descriptor Exhaustion (from /bandwidth)
- Status
- No file-descriptor exhaustion report in available data
Rate Limits (from /bandwidth)
- Status
- Reported
- Rate Limit
- 3.28 Mbit/s
- Burst Limit
- 819 KB
- Write counter
- 110
- Read counter
- 123
- Reported
- 2026-11-19 11:00 UTC (22 hours ago)
Read and write counters increment at most once per minute per direction. They are not a count of blocked connections, the duration of throttling, or necessarily the number of events in the last 24 hours. Rate is BandwidthRate and follows this site’s bits/bytes setting. Burst is BandwidthBurst, already a byte quantity. RelayBandwidthRate and RelayBandwidthBurst are extra torrc caps, not the names of these values. A hit stays eligible for 24 hours.
What to check
-
Configured bandwidth limits
Inspect BandwidthRate and BandwidthBurst (the values reported with this hit), any relay-specific caps such as RelayBandwidthRate and RelayBandwidthBurst, the intended bandwidth budget, and actual uplink headroom. A rate-limit report is not evidence of ISP throttling. After checking that evidence and the capacity you meant to offer, review whether those limits should change.MetricsPort:
tor_relay_load_global_rate_limit_reached_total{side="read"} and {side="write"}— Increases indicate additional global token-bucket limit events.
About these reports and MetricsPort
Allium’s eligibility windows are applied to the reported timestamps: 72 hours for general overload and file-descriptor exhaustion, 24 hours for a rate-limit hit. A report at the cutoff is historical. An older report can remain visible after Onionoo or Allium’s cache still has it. The cutoff does not prove the relay recovered at that moment. Allium caches the bandwidth document for 12 hours by default. The snapshot time is when Onionoo published that document. It is not the relay’s event time, and it is not necessarily the extra-info publication time. Cache age is how old Allium’s copy is.
MetricsPort counters are cumulative. Compare samples, and account for process restarts. A nonzero total alone does not show ongoing activity. Gauges describe current values. An unavailable metric is unknown, not zero. Allium does not have this relay’s MetricsPort readings and does not invent them.
The port below is an example for an endpoint you have already configured. MetricsPort must be enabled with restricted access and must not be exposed publicly. Setup stays in the Tor overload troubleshooting guide.
curl http://127.0.0.1:9035/metrics
History
Operator Identity
Source: AROI Validation API — 2026-11-19 23: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
- Effective Members: 0
- none
- Effective Member: 1
D0968EE8B66665E15B8204AACF310E820AF8D799 (this relay)
- Alleged Members: 0
- none
- Indirect Members: 0
- none
DNS Health
- Status
- Healthy (avg. 16.0s, 58th percentile)
- Query Domain
ef926613b06a43518c5e3958ee2f3e4d.d0968ee8.tor.exit.validator.1aeo.com- DNS Result
-
Resolved to
64.65.4.1 - Upstream Resolver
-
Local AS
(exit's own network)
Local AS 100% (~200 estimated queries) - Cross-Validation
- 4/4 instances succeeded
- First Hop
- HwSystems (CA) 7B1EC8B17C5E48D12C39159A595626D610F29377
- Exit Address Used
138.197.124.121- Per-Instance Results
-
Cross Validation Attempt 1: Success, 13.0s (cv1_w3) Cross Validation Attempt 2: Success, 19.9s (cv2_w3) Cross Validation Attempt 3: Success, 15.4s (cv3_w3) Cross Validation Attempt 4: Success, 15.9s (cv4_w3)
IPv4 Exit Policy Summary
reject: 25 445 465 587 6881-6999
IPv6 Exit Policy Summary
NoneFull 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 Fri, 20 Nov 2026 09:45:32 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-20 08:45:05).
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) | Desc Published | Cons Wt (Authority) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| E30CF7B3 | Yes | Yes | Yes | — | Y | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Exit | 1.8 Mbit/s (M) | 816.0 Kbit/s | 1.8 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 6.8d | 5d | 6.8d | 3.9d | 4.0d | 5.1d | 2026-11-20 05:38:25 | 1.8 Mbit/s (M) |
| dannenberg (DE) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, V2Dir, Stable, Exit | 592.0 Kbit/s (M) | 816.0 Kbit/s | 592.0 Kbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 113.8d | 8d | 113.8d | 8.2d | 4.0d | 5.1d | 2026-11-20 05:38:25 | 592.0 Kbit/s (M) |
| dizum (NL) | Yes | Yes | Yes | — | N | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Exit | 3.3 Mbit/s (R) | 816.0 Kbit/s | 3.3 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 99.9% | 98% | 34.2d | 8d | 31.2d | 6.8d | 4.0d | 5.1d | 2026-11-20 05:38:25 | 3.3 Mbit/s (R) |
| faravahar (US) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Exit | 3.3 Mbit/s (R) | 816.0 Kbit/s | 3.3 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 35.2d | 8d | 31.3d | 7.0d | 4.0d | 5.1d | 2026-11-20 05:38:25 | 3.3 Mbit/s (R) |
| gabelmoo (DE) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, V2Dir, Stable, Exit | 456.0 Kbit/s (M) | 816.0 Kbit/s | 456.0 Kbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 122.5d | 8d | 122.5d | 8.3d | 4.0d | 5.1d | 2026-11-20 05:38:25 | 456.0 Kbit/s (M) |
| longclaw (US) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, V2Dir, Stable, Exit | 448.0 Kbit/s (M) | 816.0 Kbit/s | 448.0 Kbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 77.0d | 8d | 46.3d | 9.1d | 4.0d | 5.1d | 2026-11-20 05:38:25 | 448.0 Kbit/s (M) |
| maatuska (SE) | Yes | Yes | Yes | — | N | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Exit | 3.3 Mbit/s (R) | 816.0 Kbit/s | 3.3 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 99.4% | 98% | 22.6d | 8d | 9.3d | 2.3d | 4.0d | 5.1d | 2026-11-20 05:38:25 | 3.3 Mbit/s (R) |
| moria1 (US) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, V2Dir, Stable, Exit | 1.2 Mbit/s (M) | 8.4 Mbit/s | 1.2 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 10.0d | 8d | 114.1d | 12669.7d | 4.0d | 5.0d | 2026-11-20 05:38:25 | 1.2 Mbit/s (M) |
| tor26 (AT) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, V2Dir, Stable, Exit | 576.0 Kbit/s (M) | 816.0 Kbit/s | 576.0 Kbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 114.0d | 8d | 114.0d | 8.2d | 4.0d | 5.1d | 2026-11-20 05:38:25 | 576.0 Kbit/s (M) |
N/T = this authority does not test IPv6 • — = not in this vote • 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
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.
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.



