View Relay "TorHet4"
Fingerprint: D245932673168094C492D5155F64699E251703E9 |
Operator: nikolov.cz v2
(12 relays)
✓ Validated
|
Family: 12 relays
|
Viktor Nikolov... |
AS24940
|
Germany
|
Linux
- Consensus
- In Consensus (9/9 Directory Auths)
- BW Verified
- 5/7 BW Auths Measured 688 Mbit/s Median
- Stability
- Not Overloaded | UP 5d 23h 57m ago | UP 97% (1M)
- Reachability
- IPv4: 9/9 | v6: 8/8(Directory Auths)
- BW Weight
- 0.04% of Network | 285 Mbit/s Observed By Relay
- Version
- 0.4.9.15 Recommended
-
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). -
Not eligible for Stable flag
: 1/9 authorities meet Stable (uptime or MTBF at or above their own median; 5 needed). bastet, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska 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 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. -
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.
Addresses
- OR Address
-
static.30.14.9.5.clients.your-server.de
5.9.14.30:993
[2a01:4f8:160:8410::3]:993
Reachability (Directory Authorities)
- IPv4
- 9/9
- IPv6
- 8/8 (1 don't test)
Location
- Country
-
Germany
- 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 |
| IPv6 Reachability | Meets (8/8 DA) | 8/8 tested authorities reached relay | ≥5/8 tested (majority) (≥5/8 DA) | |
| 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) | 288.0 Mbit/s – 800.0 Mbit/s (5 DA measured) 80.0 Mbit/s (4 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 | Below (1/9 DA) | Median: 5.0d (1/9 DA above threshold) Min/Max: 1.6d / 10165.8d (9/9 DA, Voting / Total Eligible) |
≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d |
| Uptime | Meets (9/9 DA) | 6.0d (R) | ≥5.2d - 5.3d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Meets (9/9 DA) | 9/9 DA assigned Fast 288.0 Mbit/s – 800.0 Mbit/s (5 DA measured) 80.0 Mbit/s (4 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 | Below (3/9 DA) | 3/9 DA assigned Stable | ≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d |
|
| Prereq: V2Dir | Meets (9/9 DA) | 9/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| Uptime | Partial (8/9 DA) | 6.0d (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.8d Time Known |
|
| Guard | Prereq: Fast | Meets (9/9 DA) | 9/9 DA assigned Fast 288.0 Mbit/s – 800.0 Mbit/s (5 DA measured) 80.0 Mbit/s (4 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 | Below (3/9 DA) | 3/9 DA assigned Stable | ≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d |
|
| Prereq: V2Dir | Meets (9/9 DA) | 9/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Partial (7/9 DA) | Median: 98.9% (7/9 DA above threshold) Min/Max: 96.9% / 99.3% (9/9 DA, Voting / Total Eligible) |
≥98%; dizum: ≥97.84099999999999% (≥5/9 DA) | |
| Time Known | Meets (9/9 DA) | Median: 13.9d (9/9 DA above threshold) Min/Max: 9.5d / 15.5d (9/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Meets (9/9 DA) | 288.0 Mbit/s – 800.0 Mbit/s (5 DA measured) 80.0 Mbit/s (4 DA relay-reported) |
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-272.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-11-04 12:45:10).
Capacity (Relay Reported)
- Observed Bandwidth
- 285.01 Mbit/s
- Advertised Bandwidth
- 285.01 Mbit/s
- Rate Limit
- 8.59 Gbit/s
- Burst Limit
- 8.59 Gbit/s
- Total Data
-
4.4 PB
(5 years)
1mo: 72 TB | 6mo: 567 TB | 1y: 1.1 PB | 5y: 4.4 PB
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-04 12:45:10
- Measured By
-
5/7
Bandwidth Authorities
Not measured by: faravahar, longclaw - Consensus Weight
- 688.0 Mbit/s (median of 5 measurements)
- Measured Min / Max
- 288.0 Mbit/s / 800.0 Mbit/s
- Deviation
- 512.0 Mbit/s [Warning] High variation
History
Uptime Metrics
- Current Status
- UP 5d 23h 57m ago
- Overall Uptime (1M/6M/1Y/5Y)
- 97.6%/99.2%/99.6%/99.7%
- Flag Uptime (1M/6M/1Y/5Y)
- Matches Overall Uptime (97.6%/99.2%/99.6%/99.7%)
- Hibernating
- No
Timestamps
- First Seen
- 2y 10mo 1w ago (2024-01-01 00:00:00)
- Last Seen
- 2h 15m 37s ago (2026-11-04 11:00:00)
- Last Restarted
- 5d 23h 57m ago (2026-10-29 13:17:39)
- Last Changed Address
- 2026-04-06 23:00:00
Evaluated 2026-11-04 13:15 UTC. /details snapshot 2026-11-04 11:00:00 UTC (cached 19s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 5h 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
History
Operator Identity
Source: AROI Validation API — 2026-11-04 04:00 UTC
- AROI Domain (?)
- nikolov.cz
- Operator Validation
- Validated (12/12 relays)
- This Relay
- Validated (dns-rsa)
- Contact
- Viktor Nikolov email:vnikolov[]vnikolov.cz url:nikolov.cz proof:dns-rsa ciissversion:2
Family Configuration
- Family Support
- Happy Families (12) — Has family-cert in server descriptor (guide) | View Full Family (12)
- Effective Members: 12
0947B12441F69611D7DF7FA94D9188F7AA2B79FF 0ACF5BB9E37D33577F6C1AA9DEEB6E7EDDF8D2C0 1045C64A7591B985AEAA2650CEE3DBD38B19CF73 3A56376BB965825539D9BBF2E409F316CE57A22E 56909EDCDFFC04AA38593466F51F3FB2AC63414C 778DCB9DB6CDD5FF2F1A85571308B492D6DFF962 B7B35AFD69A1F8C0453A45FDC92B28824F34F402 B95A8A85310362945DD0F2D184CC2A50AC875492 CF6DBE7694EDD7216612EA9CA3F1169E7D2A837F D245932673168094C492D5155F64699E251703E9 (this relay) D7078D13C7799B2A1D788CCF1D43E06DEA67BF2D F4ADC09DDE6768ECBF701612469142EABE7AFCC6
DNS Health
Not an exit relay — DNS health testing does not apply.Last fetch was at Wed, 04 Nov 2026 13:15:37 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-04 12:45:10).
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 | v6 | 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) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast | 320.0 Mbit/s (M) | 816.0 Kbit/s | 320.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 98.5% | 98% | 14.1d | 8d | 4.4d | 8.4d | 6.0d | 5.2d | 2026-11-04 05:20:27 | 320.0 Mbit/s (M) |
| dannenberg (DE) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast | 800.0 Mbit/s (M) | 816.0 Kbit/s | 800.0 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s | 98.8% | 98% | 13.9d | 8d | 4.2d | 9.3d | 6.0d | 5.3d | 2026-11-04 05:20:27 | 800.0 Mbit/s (M) |
| dizum (NL) | Yes | Yes | No | — | N | Yes | Yes | Running, Valid, V2Dir, Fast | 80.0 Mbit/s (R) | 816.0 Kbit/s | 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 96.9% | 98% | 12.8d | 8d | 3.8d | 6.7d | 6.0d | 5.3d | 2026-11-04 05:20:27 | 80.0 Mbit/s (R) |
| faravahar (US) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Guard | 80.0 Mbit/s (R) | 816.0 Kbit/s | 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 99.1% | 98% | 13.6d | 8d | 5.1d | 6.5d | 6.0d | 5.3d | 2026-11-04 05:20:27 | 80.0 Mbit/s (R) |
| gabelmoo (DE) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast | 720.0 Mbit/s (M) | 816.0 Kbit/s | 720.0 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s | 99.0% | 98% | 13.9d | 8d | 5.0d | 10.8d | 6.0d | 5.3d | 2026-11-04 05:20:27 | 720.0 Mbit/s (M) |
| longclaw (US) | Yes | Yes | No | — | Y | Yes | N/T | Running, Valid, V2Dir, Fast, Stable, HSDir, Guard | 80.0 Mbit/s (R) | 816.0 Kbit/s | 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 99.3% | 98% | 15.5d | 8d | 7.7d | 10.9d | 6.0d | 5.3d | 2026-11-04 05:20:27 | 80.0 Mbit/s (R) |
| maatuska (SE) | Yes | Yes | No | — | N | Yes | Yes | Running, Valid, V2Dir, Fast | 80.0 Mbit/s (R) | 816.0 Kbit/s | 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 97.2% | 98% | 12.5d | 8d | 1.6d | 2.4d | 6.0d | 5.3d | 2026-11-04 05:20:27 | 80.0 Mbit/s (R) |
| moria1 (US) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, Guard | 288.0 Mbit/s (M) | 8.4 Mbit/s | 288.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 98.9% | 98% | 9.5d | 8d | 10165.8d | 7607.5d | 6.0d | 5.3d | 2026-11-04 05:20:27 | 288.0 Mbit/s (M) |
| tor26 (AT) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast | 688.0 Mbit/s (M) | 816.0 Kbit/s | 688.0 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s | 98.9% | 98% | 14.4d | 8d | 5.0d | 10.6d | 6.0d | 5.3d | 2026-11-04 05:20:27 | 688.0 Mbit/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.







