View Relay "NTH302R1"
Fingerprint: E5C7A023A49948D9733A722BB6F7D1E9EA6E3F3E |
Operator: nothingtohide.nl v2
(665 relays)
⚠ Misconfigured
|
Family: 31 relays
|
email:mail[]nothingtohide.nl... |
AS8283
|
Netherlands
|
FreeBSD
- Consensus
- In Consensus (8/8 Directory Auths)
- BW Verified
- 0/6 BW Auths Measured
- Stability
- Incomplete | DOWN 3h 15m 38s ago
- Reachability
- IPv4: 8/8 | v6: None configured(Directory Auths)
- BW Weight
- 0 Kbit/s Observed By Relay
- Version
- 0.4.9.15 Recommended
Issues Detected:
-
Not getting the Fast flag
: Only 0/8 authorities vote Fast (5 needed). dizum, faravahar, longclaw and maatuska used the relay-reported unknown, below the Fast threshold (816.0 Kbit/s). dannenberg, gabelmoo, moria1 and tor26 counted this relay as 0 (no measurement, relay-reported bandwidth ignored).
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/8 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 – 272.0 Mbit/s). dizum, faravahar, longclaw and maatuska used the relay-reported unknown. 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/8 authorities meet guard-wfu (≥98%; maatuska: ≥96.571%; 5 needed). dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 measured 0.6%–1.7%.
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
: 1/8 authorities meet Stable (uptime or MTBF at or above their own median; 5 needed). 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 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. -
Low bandwidth authority measurements
: Only 0/6 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.
Addresses
- OR Address
- 94.142.241.41:22
Reachability (Directory Authorities)
- IPv4
- 8/8
- IPv6
- None configured
Location
- Country
-
Netherlands
- Interactive Map
- View in RouteFluxMap
Eligible Flags (3):
Running: 8/8 | Valid: 8/8 | V2Dir: 8/8 | Fast: 0/8 | Stable: 1/8 | HSDir: 0/8 | Guard: 0/8 | Exit: 0/8
Eligibility Flag Vote Details
| Flag | Metric | Status | Relay Value | Threshold Required |
|---|---|---|---|---|
| Running | IPv4 Reachability | Meets (8/8 DA) | 8/8 authorities reached relay | ≥5/8 DA ORPort reachable |
| Valid | Descriptor | Meets (8/8 DA) | 8/8 authorities assigned Valid | Not blacklisted + valid descriptor (≥5/8 DA) |
| V2Dir | DirPort Available | Meets (8/8 DA) | Tunnelled: Yes (no DirPort) (R) | Tunnelled directory via ORPort or DirPort (≥5/8 DA) |
| Fast | Speed | Below (0/8 DA) | 0 bit/s (4 DA relay-reported) 0 bit/s (4 DA unmeasured, counted as 0) |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/8 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Stable | MTBF | Below (1/8 DA) | Median: 0.2d (1/8 DA above threshold) Min/Max: 0.2d / 20766.6d (8/8 DA, Voting / Total Eligible) |
≥1.4d - 12.9d (varies) (≥5/8 DA) [Stricter] moria1: ≥6724.7d |
| Uptime | Below (0/8 DA) | 0.2d (R) | ≥5.0d - 5.0d (varies) (≥5/8 DA) | |
| HSDir | Prereq: Fast | Below (0/8 DA) | 0/8 DA assigned Fast 0 bit/s (4 DA relay-reported) 0 bit/s (4 DA unmeasured, counted as 0) |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/8 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Below (1/8 DA) | 1/8 DA assigned Stable | ≥1.4d - 12.9d (varies) (≥5/8 DA) [Stricter] moria1: ≥6724.7d |
|
| Prereq: V2Dir | Meets (8/8 DA) | 8/8 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/8 DA) | |
| Uptime | Below (0/8 DA) | 0.2d (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/8 DA) [Stricter] moria1: ≥98% WFU and ≥9.8d Time Known |
|
| Guard | Prereq: Fast | Below (0/8 DA) | 0/8 DA assigned Fast 0 bit/s (4 DA relay-reported) 0 bit/s (4 DA unmeasured, counted as 0) |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/8 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Below (1/8 DA) | 1/8 DA assigned Stable | ≥1.4d - 12.9d (varies) (≥5/8 DA) [Stricter] moria1: ≥6724.7d |
|
| Prereq: V2Dir | Meets (8/8 DA) | 8/8 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/8 DA) | |
| WFU | Below (0/8 DA) | Median: 0.6% (0/8 DA above threshold) Min/Max: 0.6% / 1.7% (8/8 DA, Voting / Total Eligible) |
≥98%; maatuska: ≥96.571% (≥5/8 DA) | |
| Time Known | Meets (8/8 DA) | Median: 40.8d (8/8 DA above threshold) Min/Max: 9.6d / 40.9d (8/8 DA, Voting / Total Eligible) |
≥8 days (≥5/8 DA) | |
| Bandwidth | Below (0/8 DA) | 0 bit/s (4 DA relay-reported) 0 bit/s (4 DA unmeasured, counted as 0) |
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-272.0 Mbit/s) (≥5/8 DA) | |
| Exit | Exit Policy | Below (0/8 DA) | Port 80: No | Port 443: No (R) | Allows ≥1 /8 on ports 80 AND 443 (≥5/8 DA) |
(DA) = Dir. Auth. Measured |
(R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-11-11 13:45:07).
Capacity (Relay Reported)
- Observed Bandwidth
- 0.00 Kbit/s
- Advertised Bandwidth
- Unknown
- Rate Limit
- 8.59 Gbit/s
- Burst Limit
- 8.59 Gbit/s
- Total Data
- N/A
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-11 13:45:07
- Measured By
-
0/6
Bandwidth Authorities
Not measured by: dannenberg, faravahar, gabelmoo, longclaw, moria1, tor26 - Consensus Weight
- 0 bit/s (Unmeasured)
- Measured Min / Max
- N/A / N/A
Network Participation:
Consensus Weight:
N/A
|
Guard:
N/A |
Middle:
N/A |
Exit:
N/A
Uptime Metrics
- Current Status
- DOWN 3h 15m 38s 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
- 3h 15m 38s ago (2026-11-11 11:00:00)
- Last Seen
- 3h 15m 38s ago (2026-11-11 11:00:00)
- Last Restarted
- 3h 39m 50s ago (2026-11-11 10:35:48)
- Last Changed Address
- 2026-11-11 11:00:00
Overload status:
Incomplete — not every signal could be evaluated.
(No bandwidth record available for this relay)
Evaluated 2026-11-11 14:15 UTC. /details snapshot 2026-11-11 13:00:00 UTC (cached 29s ago). /bandwidth snapshot 2026-11-11 02:00:00 UTC (cached 11h ago).
General Overload (from /details)
- Status
- No general overload report in available data
File Descriptor Exhaustion (from /bandwidth)
- Status
- No bandwidth record available for this relay
Rate Limits (from /bandwidth)
- Status
- No bandwidth record available for this relay
- 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-11-11 05:00 UTC
- AROI Domain (?)
- nothingtohide.nl
- Operator Validation
- Unvalidated
- This Relay
-
Unvalidated
Error: URI-RSA: HTTP error connection timed out after 5s for URL: https://nothingtohide.nl/.well-known/tor-relay/rsa-fingerprint.txt. Used domain cache after 22 attempts. - Contact
- email:mail[]nothingtohide.nl url:nothingtohide.nl proof:uri-rsa abuse:abuse[]nothingtohide.nl ciissversion:2
Family Configuration
- Family Support
- MyFamily Only (31) — Legacy only. Consider migrating to Happy Families. | View Full Family (31)
Happy Families (family-cert)
- Effective Members: 0
- none
MyFamily (legacy declarations)
- Effective Members: 31
050E32583A80FA5E71CB1089777FE284A2169D74 1BA9275480BEACF3AF2069BDB91E4345D399E3C6 1CDA765239A945979917154730B66179092B305F 22202074254FB6ED9C9CA0A4A1ECA21C9F0AAB33 3510FC0B2782BF7A37F1110FF6F31E1CAADB0375 40C220ECFC104C96FEAD00A154EF3CE844F65E35 41934D094EADFDFAA798BF637A199FFCC7D29051 46E0487EEEFD694CE625CC6E12D032395C01DB82 485519E539E65603C48E033ED62D91B5EB16D152 4E07BA5001102603CFE6130780E7CA568E02F116 4F6892AB848ED224A5BA5E70A865D981E44B268D 6026A261920D4B886CD60BCFEA4841FA1555A79B 66A06F6BED7CD6E9683A4EF04B034FB93301BE01 6C68BEB275D375B510681243C90371BA0B518E77 6F05AB498C6B276D87B395A7F334EC64B0B0363D 818F4F4CBA692A9EE7CE4D19D0E6C4F51C903EA2 8E84C81FA99A70AFD2751B761435D2A301CFFBAB 9307966D513D58D9E9A6957BDC6DAD2E6833D95F 940591A3B06434E86DC019434EB2AF425ADBD9CD 9A2E66E7B305D0CB98889CD1D290CE8307F49F95 9A3C11A601BCDE7DB3BF4A495C74DA58308A673A AA5821AAE1676BD503BBE31435727E414AC371CD AE18CC3A99115F56EE3D116AE52FA92E7F7A5F72 AFE993EA8F7C7D053DF83F78B42625B959B8CBB8 B5558CFA70A5308582B25767C9698E6DBE6A90B2 BBAB820AF8216277F36EAA1787B44BA0A5D7C204 C1FD3CA10A19635A83DC9E6E2E4F1B3E42FCE042 CA1AC54C401CCFE69943542F2CF9843BC6917820 E5C7A023A49948D9733A722BB6F7D1E9EA6E3F3E (this relay) F04AC7D177EC79308D6959DBE042A247D9761635 F0A2D13158DDE019181F8B5B14AAEEA74ADC8249
- Alleged Member: 1
-
(they don't list you back)
864B095917EA3486738A138303FFC322E395D3AA (not in the network) - Indirect Members: 0
- none
DNS Health
Not an exit relay — DNS health testing does not apply.Last fetch was at Wed, 11 Nov 2026 14:15:38 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-11 13:45:07).
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) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| dannenberg (DE) | Yes | Yes | No | — | Y | Yes | Valid, V2Dir | 0 bit/s (U) | 816.0 Kbit/s | 0 bit/s (U) | 272.0 Mbit/s OR 16.8 Mbit/s | 0.7% | 98% | 40.9d | 8d | 0.3d | 11.7d | 0.2d | 5.0d | 2026-11-11 10:36:17 | — |
| dizum (NL) | Yes | Yes | No | — | N | Yes | Valid, V2Dir | 0 bit/s (R) | 816.0 Kbit/s | 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 0.6% | 98% | 40.9d | 8d | 0.2d | 10.0d | 0.2d | 5.0d | 2026-11-11 10:36:17 | — |
| faravahar (US) | Yes | Yes | No | — | Y | Yes | Valid, V2Dir | 0 bit/s (R) | 816.0 Kbit/s | 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 0.6% | 98% | 40.9d | 8d | 0.2d | 9.4d | 0.2d | 5.0d | 2026-11-11 10:36:17 | — |
| gabelmoo (DE) | Yes | Yes | No | — | Y | Yes | Valid, V2Dir | 0 bit/s (U) | 816.0 Kbit/s | 0 bit/s (U) | 248.0 Mbit/s OR 16.8 Mbit/s | 0.6% | 98% | 40.8d | 8d | 0.2d | 12.9d | 0.2d | 5.0d | 2026-11-11 10:36:17 | — |
| longclaw (US) | Yes | Yes | No | — | Y | Yes | Valid, V2Dir | 0 bit/s (R) | 816.0 Kbit/s | 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 0.6% | 98% | 40.9d | 8d | 0.2d | 13.1d | 0.2d | 5.0d | 2026-11-11 10:36:17 | — |
| maatuska (SE) | Yes | Yes | No | — | N | Yes | Valid, V2Dir | 0 bit/s (R) | 816.0 Kbit/s | 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 0.6% | 97% | 40.7d | 8d | 0.2d | 1.4d | 0.2d | 5.0d | 2026-11-11 10:36:17 | — |
| moria1 (US) | Yes | Yes | No | — | Y | Yes | Valid, V2Dir, Stable | 0 bit/s (U) | 8.4 Mbit/s | 0 bit/s (U) | 184.0 Mbit/s OR 16.8 Mbit/s | 1.7% | 98% | 9.6d | 8d | 20766.6d | 6724.7d | 0.2d | 5.1d | 2026-11-11 10:36:17 | — |
| tor26 (AT) | Yes | Yes | No | — | Y | Yes | Valid, V2Dir | 0 bit/s (U) | 816.0 Kbit/s | 0 bit/s (U) | 256.0 Mbit/s OR 16.8 Mbit/s | 0.6% | 98% | 40.8d | 8d | 0.2d | 12.9d | 0.2d | 5.0d | 2026-11-11 10:36:17 | — |
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.