View Relay "hkrelaytorproject"
Fingerprint: 2DA9088E2CA03D1CE042F07D38D5BBE89873F672 |
Family: 1 relay
|
h4kr.anonymous@gmail.com |
AS31898
|
India
|
Linux
- Consensus
- In Consensus (8/9 Directory Auths)
- BW Verified
- 0/7 BW Auths Measured 160 Kbit/s Median
- Stability
- Not Overloaded | UP 3h 19m 37s ago
- Reachability
- IPv4: 8/9 | v6: None configured(Directory Auths)
- BW Weight
- 0.00% of Network | 516 Kbit/s Observed By Relay
- Version
- 0.4.9.14 Recommended
Issues Detected:
-
Not getting the Fast flag
: Only 0/9 authorities vote Fast (5 needed). dizum, longclaw and maatuska used the relay-reported 512.0 Kbit/s, below the Fast threshold (816.0 Kbit/s). dannenberg, gabelmoo, moria1 and tor26 counted this relay as 0 (no measurement, relay-reported bandwidth ignored). faravahar judged it by bandwidth not shown in the votes.
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: 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
: 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 – 296.0 Mbit/s). dizum, longclaw and maatuska used the relay-reported 512.0 Kbit/s. dannenberg, gabelmoo, moria1 and tor26 counted this relay as 0 (no measurement, relay-reported bandwidth ignored).
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. -
Guard: WFU below threshold
: 0/9 authorities meet guard-wfu (≥98%; 5 needed). dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 measured 0.2%–1.3%.
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. -
Not eligible for Stable flag
: 0/9 authorities meet Stable (uptime or MTBF at or above their own median; 5 needed). dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 do not.
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: 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. -
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: requires V2Dir (tunnelled-dir-server)
: HSDir requires the relay to support tunnelled directory requests (V2Dir flag). This relay is missing V2Dir — the descriptor likely does not include
tunnelled-dir-server, usually becauseDirCache 0is set in torrc.
Suggestion: RemoveDirCache 0from torrc (DirCache is enabled by default in Tor ≥0.3.3). Restart Tor and verify the descriptor includestunnelled-dir-server. You can check with:grep tunnelled-dir-server /var/lib/tor/cached-descriptors -
Low bandwidth authority measurements
: Only 0/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.
Notes:
- Partial IPv4 reachability: 8/9 authorities can reach this relay
Suggestion: Some authorities cannot reach you: bastet. This may be temporary or due to geographic routing issues.
Addresses
- OR Address
- 140.245.28.121:9001
Reachability (Directory Authorities)
- IPv4
- 8/9
- IPv6
- None configured
Location
- Country
-
India
- Interactive Map
- View in RouteFluxMap
Eligible Flags (3):
Running: 8/9 | Valid: 8/9 | V2Dir: 8/9 | Fast: 0/9 | Stable: 1/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 0/9
Eligibility Flag Vote Details
| Flag | Metric | Status | Relay Value | Threshold Required |
|---|---|---|---|---|
| Running | IPv4 Reachability | Meets (8/9 DA) | 8/9 authorities reached relay | ≥5/9 DA ORPort reachable |
| Valid | Descriptor | Meets (8/9 DA) | 8/9 authorities assigned Valid | Not blacklisted + valid descriptor (≥5/9 DA) |
| V2Dir | DirPort Available | Below (0/9 DA) | No DirPort, no tunnelled-dir-server (R) | Tunnelled directory via ORPort or DirPort (≥5/9 DA) |
| Fast | Speed | Below (0/9 DA) | 512.0 Kbit/s (3 DA relay-reported) 0 bit/s (4 DA unmeasured, counted as 0) faravahar: not published |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Stable | MTBF | Below (0/9 DA) | Median: 0.2d (1/9 DA above threshold) Min/Max: 0.1d / 190.4d (8/9 DA, Voting / Total Eligible) |
≥4.9d - 7.9d (varies) (≥5/9 DA) [Stricter] moria1: ≥10586.3d |
| Uptime | Below (0/9 DA) | 0.1d (R) | ≥6.8d - 7.0d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Below (0/9 DA) | 0/9 DA assigned Fast 512.0 Kbit/s (3 DA relay-reported) 0 bit/s (4 DA unmeasured, counted as 0) faravahar: not published |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Below (1/9 DA) | 1/9 DA assigned Stable | ≥4.9d - 7.9d (varies) (≥5/9 DA) [Stricter] moria1: ≥10586.3d |
|
| Prereq: V2Dir | Below (0/9 DA) | 0/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| Uptime | Below (0/9 DA) | 0.1d (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.8d Time Known |
|
| Guard | Prereq: Fast | Below (0/9 DA) | 0/9 DA assigned Fast 512.0 Kbit/s (3 DA relay-reported) 0 bit/s (4 DA unmeasured, counted as 0) faravahar: not published |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Below (1/9 DA) | 1/9 DA assigned Stable | ≥4.9d - 7.9d (varies) (≥5/9 DA) [Stricter] moria1: ≥10586.3d |
|
| Prereq: V2Dir | Below (0/9 DA) | 0/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Below (0/9 DA) | Median: 0.3% (0/9 DA above threshold) Min/Max: 0.2% / 1.3% (8/9 DA, Voting / Total Eligible) |
≥98% (≥5/9 DA) | |
| Time Known | Partial (8/9 DA) | Median: 50.3d (8/9 DA above threshold) Min/Max: 9.7d / 53.0d (8/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Below (0/9 DA) | 512.0 Kbit/s (3 DA relay-reported) 0 bit/s (4 DA unmeasured, counted as 0) faravahar: not published |
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-296.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-10-24 15:45:06).
Capacity (Relay Reported)
- Observed Bandwidth
- 516.10 Kbit/s
- Advertised Bandwidth
- 516.10 Kbit/s
- Rate Limit
- 8.59 Gbit/s
- Burst Limit
- 8.59 Gbit/s
- Total Data
-
4.2 GB
(6 months)
1mo: 206 MB | 6mo: 4.2 GB
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-10-24 15:45:06
- Measured By
-
0/7
Bandwidth Authorities
Not measured by: bastet, dannenberg, faravahar, gabelmoo, longclaw, moria1, tor26 - Consensus Weight
- 160.0 Kbit/s (Unmeasured)
- Measured Min / Max
- N/A / N/A
Network Participation:
Consensus Weight:
0.0000% of network
(3th pctl)
|
Guard:
N/A |
Middle:
0.0000% (3th pctl) |
Exit:
N/A
History
Uptime Metrics
- Current Status
- UP 3h 19m 37s ago
- Overall Uptime (1M/6M/1Y/5Y)
- 0.0%/0.0%/0.0%/0.0%
- Flag Uptime (1M/6M/1Y/5Y)
- N/A
- Hibernating
- No
Timestamps
- First Seen
- 2h 45m 10s ago (2026-10-24 14:00:00)
- Last Seen
- 1h 45m 10s ago (2026-10-24 15:00:00)
- Last Restarted
- 3h 19m 37s ago (2026-10-24 13:25:33)
- Last Changed Address
- 2026-10-24 14:00:00
Overload Status:
Not Overloaded — No overload conditions reported.
Evaluated 2026-10-24 16:45 UTC. /details snapshot 2026-10-24 15:00:00 UTC (cached 10s ago). /bandwidth snapshot 2026-10-24 14:00:00 UTC (cached 1h 30m ago).
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
- No rate-limit report in available data
- Rate Limit
- —
- Burst Limit
- —
- Write counter
- —
- Read counter
- —
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
Operator Identity
Source: AROI Validation API — 2026-10-24 08:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- h4kr.anonymous@gmail.com
Family Configuration
- Family Support
- None — No family membership configured
Happy Families (family-cert)
- Effective Members: 0
- none
MyFamily (legacy declarations)
- Effective Member: 1
2DA9088E2CA03D1CE042F07D38D5BBE89873F672 (this relay)
- Alleged Members: 0
- none
- Indirect Members: 0
- none
DNS Health
Not an exit relay — DNS health testing does not apply.Last fetch was at Sat, 24 Oct 2026 16:45:10 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-10-24 15:45:06).
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) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| bastet (US) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — |
| dannenberg (DE) | Yes | Yes | No | — | Y | Yes | Running, Valid | 0 bit/s (U) | 816.0 Kbit/s | 0 bit/s (U) | 296.0 Mbit/s OR 16.8 Mbit/s | 1.3% | 98% | 40.2d | 8d | 0.5d | 6.0d | 0.1d | 7.0d | 2026-10-24 13:26:37 | 512.0 Kbit/s (R) |
| dizum (NL) | Yes | Yes | No | — | N | Yes | Running, Valid | 512.0 Kbit/s (R) | 816.0 Kbit/s | 512.0 Kbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 0.7% | 98% | 42.9d | 8d | 0.3d | 7.7d | 0.1d | 6.9d | 2026-10-24 13:26:37 | 512.0 Kbit/s (R) |
| faravahar (US) | Yes | Yes | No | — | Y | Yes | Running, Valid | not published | 816.0 Kbit/s | not published | 280.0 Mbit/s OR 16.8 Mbit/s | 0.3% | 98% | 50.2d | 8d | 0.1d | 8.0d | 0.1d | 7.9d | 2026-10-24 13:26:37 | 512.0 Kbit/s (R) |
| gabelmoo (DE) | Yes | Yes | No | — | Y | Yes | Running, Valid | 0 bit/s (U) | 816.0 Kbit/s | 0 bit/s (U) | 264.0 Mbit/s OR 16.8 Mbit/s | 0.3% | 98% | 52.9d | 8d | 0.1d | 7.9d | 0.1d | 7.0d | 2026-10-24 13:26:37 | 512.0 Kbit/s (R) |
| longclaw (US) | Yes | Yes | No | — | Y | Yes | Running, Valid | 512.0 Kbit/s (R) | 816.0 Kbit/s | 512.0 Kbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 0.2% | 98% | 53.0d | 8d | 0.1d | 8.1d | 0.1d | 6.8d | 2026-10-24 13:26:37 | 512.0 Kbit/s (R) |
| maatuska (SE) | Yes | Yes | No | — | N | Yes | Running, Valid | 512.0 Kbit/s (R) | 816.0 Kbit/s | 512.0 Kbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 0.3% | 98% | 52.2d | 8d | 0.1d | 7.8d | 0.1d | 6.8d | 2026-10-24 13:26:37 | 512.0 Kbit/s (R) |
| moria1 (US) | Yes | Yes | No | — | Y | Yes | Running, Valid, Stable | 0 bit/s (U) | 8.4 Mbit/s | 0 bit/s (U) | 200.0 Mbit/s OR 16.8 Mbit/s | 1.0% | 98% | 9.7d | 8d | 190.4d | 10586.3d | 0.1d | 7.0d | 2026-10-24 13:26:37 | 512.0 Kbit/s (R) |
| tor26 (AT) | Yes | Yes | No | — | Y | Yes | Running, Valid | 0 bit/s (U) | 816.0 Kbit/s | 0 bit/s (U) | 272.0 Mbit/s OR 16.8 Mbit/s | 0.4% | 98% | 50.4d | 8d | 0.2d | 7.9d | 0.1d | 7.0d | 2026-10-24 13:26:37 | 512.0 Kbit/s (R) |
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
Bandwidth Values Explained:
Measured (M) = An authority's bandwidth-scanner measurement of your relay (
Relay-reported (R) = The bandwidth your relay advertises: the lower of its observed bandwidth and its rate limit, capped at 10 MB/s (
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.
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.
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.
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.