View Relay "NTH302R4"

Fingerprint: 8E84C81FA99A70AFD2751B761435D2A301CFFBAB | Operator: nothingtohide.nl v2 (664 relays) ✓ Validated | Family: 30 relays | email:mail[]nothingtohide.nl... | AS8283 | Netherlands | FreeBSD

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
5/7 BW Auths Measured 272 Mbit/s Median
Stability
Not Overloaded | UP 1mo 3d 14h ago | UP 98% (1M)
Reachability
IPv4: 9/9 | v6: None configured(Directory Auths)
BW Weight
0.02% of Network | 123 Mbit/s Observed By Relay
Version
0.4.9.13 Not Recommended
Issues Detected:
  • 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.
  • Tor version not recommended : Running Tor version 0.4.9.13 which is not on the recommended list.
    Suggestion: Update to the latest stable Tor version. Outdated versions may have security vulnerabilities and could eventually be rejected by the network. See torproject.org/download for latest releases.
Notes:
  • Guard: WFU near threshold: Weighted Fractional Uptime is just above the Guard bar at maatuska (98.1%, need ≥98%) and just under the Guard bar at dizum (97.5%, need ≥97.774%). Recent downtime weighs more than older downtime. Avoid restarts while it is this close; a short outage can drop the Guard flag.
    Suggestion: Recent downtime weighs more than older downtime. Minimize restarts, use systemd Restart=always, and watch for OOM kills until each authority has more room above its own guard-wfu.

Addresses
OR Address
1.tor-relay.nozel.org
94.142.241.41:443
Reachability (Directory Authorities)
IPv4
9/9
IPv6
None configured
Location
Country
Netherlands Netherlands
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS8283
AS Name
Netwerkvereniging Coloclue (BGP.tools)
AS Rarity
Epic (score: 3/5, 0.51% consensus weight, 4 operators)

Current Flags (7): Running, Valid, V2Dir, Fast, Stable, HSDir, Guard
Eligible Flags (7): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 8/9 | HSDir: 7/9 | Guard: 7/9 | Exit: 0/9
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 Meets (9/9 DA) 80.0 Mbit/s – 336.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: 8.2d (4/9 DA above threshold)
Min/Max: 1.9d / 8384.8d (9/9 DA, Voting / Total Eligible)
≥2.3d - 9.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7607.9d
Uptime Meets (9/9 DA) 33.6d (R) ≥5.2d - 5.3d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
80.0 Mbit/s – 336.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 Meets (8/9 DA) 8/9 DA assigned Stable ≥2.3d - 9.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7607.9d
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) 33.6d (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
80.0 Mbit/s – 336.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 Meets (8/9 DA) 8/9 DA assigned Stable ≥2.3d - 9.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7607.9d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Partial (8/9 DA) Median: 99.4% (8/9 DA above threshold)
Min/Max: 97.5% / 99.6% (9/9 DA, Voting / Total Eligible)
≥98%; dizum: ≥97.774% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 15.9d (9/9 DA above threshold)
Min/Max: 9.6d / 16.1d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 80.0 Mbit/s – 336.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 11:15:19).

Capacity (Relay Reported)
Observed Bandwidth
123.82 Mbit/s
Advertised Bandwidth
123.82 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
868 TB (5 years)
1mo: 27 TB | 6mo: 48 TB | 1y: 182 TB | 5y: 868 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-04 11:15:19

Measured By
5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Consensus Weight
272.0 Mbit/s (median of 5 measurements)
Measured Min / Max
80.0 Mbit/s / 336.0 Mbit/s
Deviation
256.0 Mbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0172% of network (79th pctl) | Guard: 0.0361% (71th pctl) | Middle: 0.0136% (72th pctl) | Exit: N/A
History

Uptime Metrics
Current Status
UP 1mo 3d 14h ago
Overall Uptime (1M/6M/1Y/5Y)
98.7%/37.2%/59.5%/78.4%
Flag Uptime (1M/6M/1Y/5Y)
65.3%/21.3%/51.6%/67.5%
Hibernating
No
Timestamps
First Seen
2y 6mo 6d ago (2024-05-02 00:00:00)
Last Seen
1h 15m 40s ago (2026-11-04 11:00:00)
Last Restarted
1mo 3d 14h ago (2026-10-01 21:37:51)
Last Changed Address
2026-08-27 08:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Evaluated 2026-11-04 12:15 UTC. /details snapshot 2026-11-04 11:00:00 UTC (cached 25s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 4h 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 03:00 UTC

AROI Domain (?)
nothingtohide.nl
Operator Validation
Validated (534/664 relays)
This Relay
Validated (uri-rsa)
Contact
email:mail[]nothingtohide.nl url:nothingtohide.nl proof:uri-rsa abuse:abuse[]nothingtohide.nl ciissversion:2
Family Configuration
Family Support
MyFamily Only (30) — Legacy only. Consider migrating to Happy Families. | View Full Family (30)
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Members: 30
050E32583A80FA5E71CB1089777FE284A2169D74
1BA9275480BEACF3AF2069BDB91E4345D399E3C6
1CDA765239A945979917154730B66179092B305F
22202074254FB6ED9C9CA0A4A1ECA21C9F0AAB33
3510FC0B2782BF7A37F1110FF6F31E1CAADB0375
40C220ECFC104C96FEAD00A154EF3CE844F65E35
41934D094EADFDFAA798BF637A199FFCC7D29051
46E0487EEEFD694CE625CC6E12D032395C01DB82
485519E539E65603C48E033ED62D91B5EB16D152
4E07BA5001102603CFE6130780E7CA568E02F116
4F6892AB848ED224A5BA5E70A865D981E44B268D
6026A261920D4B886CD60BCFEA4841FA1555A79B
66A06F6BED7CD6E9683A4EF04B034FB93301BE01
6C68BEB275D375B510681243C90371BA0B518E77
6F05AB498C6B276D87B395A7F334EC64B0B0363D
818F4F4CBA692A9EE7CE4D19D0E6C4F51C903EA2
8E84C81FA99A70AFD2751B761435D2A301CFFBAB (this relay)
9307966D513D58D9E9A6957BDC6DAD2E6833D95F
940591A3B06434E86DC019434EB2AF425ADBD9CD
9A2E66E7B305D0CB98889CD1D290CE8307F49F95
9A3C11A601BCDE7DB3BF4A495C74DA58308A673A
AA5821AAE1676BD503BBE31435727E414AC371CD
AE18CC3A99115F56EE3D116AE52FA92E7F7A5F72
AFE993EA8F7C7D053DF83F78B42625B959B8CBB8
B5558CFA70A5308582B25767C9698E6DBE6A90B2
BBAB820AF8216277F36EAA1787B44BA0A5D7C204
C1FD3CA10A19635A83DC9E6E2E4F1B3E42FCE042
CA1AC54C401CCFE69943542F2CF9843BC6917820
F04AC7D177EC79308D6959DBE042A247D9761635
F0A2D13158DDE019181F8B5B14AAEEA74ADC8249
Alleged Members: 2
(they don't list you back)
864B095917EA3486738A138303FFC322E395D3AA (not in the network)
E5C7A023A49948D9733A722BB6F7D1E9EA6E3F3E (not in the network)
Indirect Members: 0
none

Platform
FreeBSD — Tor 0.4.9.13 on FreeBSD
Version
0.4.9.13 — Not Recommended
Version Status
Obsolete — Update urgently. See torproject.org/download — nothingtohide.nl: 664 relays on 0.4.9.14 and 0.4.9.13, 10.20% of consensus weight. Operator versions

DNS Health
Not an exit relay — DNS health testing does not apply.
IPv4 Exit Policy Summary
reject: 
  1-65535
IPv6 Exit Policy Summary
None
Full Exit Policy
reject *:*

Last fetch was at Wed, 04 Nov 2026 12:15:39 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-11-04 11:15:19).

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) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 96.0 Mbit/s (M) | 816.0 Kbit/s 96.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 99.3% | 98% 15.9d | 8d 7.0d | 8.4d 33.6d | 5.2d 2026-11-03 21:07:55 96.0 Mbit/s (M)
dannenberg (DE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 336.0 Mbit/s (M) | 816.0 Kbit/s 336.0 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s 99.5% | 98% 15.9d | 8d 8.2d | 9.3d 33.6d | 5.3d 2026-11-03 21:07:55 336.0 Mbit/s (M)
dizum (NL) Yes Yes No — N Yes Running, Valid, V2Dir, Fast, Stable, HSDir 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 97.5% | 98% 13.6d | 8d 6.0d | 6.7d 33.6d | 5.3d 2026-11-03 21:07:55 80.0 Mbit/s (R)
faravahar (US) Yes Yes No — Y 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.4% | 98% 13.3d | 8d 5.7d | 6.5d 33.6d | 5.3d 2026-11-03 21:07:55 80.0 Mbit/s (R)
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 280.0 Mbit/s (M) | 816.0 Kbit/s 280.0 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 99.6% | 98% 16.1d | 8d 9.3d | 10.7d 33.6d | 5.3d 2026-11-03 21:07:55 280.0 Mbit/s (M)
longclaw (US) Yes Yes No — Y 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.6% | 98% 15.9d | 8d 9.4d | 10.9d 33.6d | 5.3d 2026-11-03 21:07:55 80.0 Mbit/s (R)
maatuska (SE) Yes Yes No — N 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 98.1% | 98% 12.3d | 8d 1.9d | 2.3d 33.6d | 5.3d 2026-11-03 21:07:55 80.0 Mbit/s (R)
moria1 (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, Stable, Guard 80.0 Mbit/s (M) | 8.4 Mbit/s 80.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 99.2% | 98% 9.6d | 8d 8384.8d | 7607.9d 33.6d | 5.3d 2026-11-03 21:07:55 80.0 Mbit/s (M)
tor26 (AT) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 272.0 Mbit/s (M) | 816.0 Kbit/s 272.0 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s 99.5% | 98% 15.9d | 8d 9.4d | 10.6d 33.6d | 5.3d 2026-11-03 21:07:55 272.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

Bandwidth Values Explained:
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.