View Relay "NLTorNiceVPSnet"

Fingerprint: 69022EDC564591DDC51FAC44CC6937434754D231 | Family: 1 relay | https://NiceVPS.net | AS49447 | Netherlands | Linux

Consensus
In Consensus (9/9 Directory Auths)
DNS Health
Healthy (19.3s, 97th percentile) (via exitdnshealth.1aeo.com)
BW Verified
5/7 BW Auths Measured 200 Mbit/s Median
Stability
Not Overloaded | UP 5d 7h 11m ago | UP 98% (1M)
Reachability
IPv4: 9/9 | v6: None configured(Directory Auths)
BW Weight
0.01% of Network | 111 Mbit/s Observed By Relay
Version
0.4.9.15 Recommended
Notes:
  • Guard: WFU near threshold: Weighted Fractional Uptime is just under the Guard bar at dizum (97.7%, need ≥97.84099999999999%). 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
nl-tor.nicevps.net
45.9.148.50:443
Exit Address
45.9.148.50
Reachability (Directory Authorities)
IPv4
9/9
IPv6
None configured
Location
Country
Netherlands Netherlands
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS49447
AS Name
Nice IT Services Group Inc. (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 2 operators)

Current Flags (8): Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit
Eligible Flags (8): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 9/9 | HSDir: 9/9 | Guard: 8/9 | Exit: 9/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) 144.0 Mbit/s – 240.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 (3/9 DA) Median: 10.3d (5/9 DA above threshold)
Min/Max: 3.6d / 6648.8d (9/9 DA, Voting / Total Eligible)
≥2.4d - 9.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7607.5d
Uptime Below (2/9 DA) 5.3d (R) ≥5.2d - 5.3d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
144.0 Mbit/s – 240.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 (9/9 DA) 9/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 Meets (9/9 DA) 5.3d (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
144.0 Mbit/s – 240.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 (9/9 DA) 9/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 (8/9 DA) Median: 99.5% (8/9 DA above threshold)
Min/Max: 97.7% / 99.6% (9/9 DA, Voting / Total Eligible)
≥98%; dizum: ≥97.84099999999999% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 17.1d (9/9 DA above threshold)
Min/Max: 9.8d / 18.0d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 144.0 Mbit/s – 240.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 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-04 12:45:10).

Capacity (Relay Reported)
Observed Bandwidth
111.05 Mbit/s
Advertised Bandwidth
111.05 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
728 TB (5 years)
1mo: 31 TB | 6mo: 153 TB | 1y: 424 TB | 5y: 728 TB
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
200.0 Mbit/s (median of 5 measurements)
Measured Min / Max
144.0 Mbit/s / 240.0 Mbit/s
Network Participation: Consensus Weight: 0.0126% of network (71th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0411% (64th pctl)
History

Uptime Metrics
Current Status
UP 5d 7h 11m ago
Overall Uptime (1M/6M/1Y/5Y)
98.5%/92.3%/90.9%/85.1%
Flag Uptime (1M/6M/1Y/5Y)
—/—/—/84.8%
Hibernating
No
Timestamps
First Seen
1y 9mo 1w ago (2025-01-29 19:00:00)
Last Seen
2h 45m 39s ago (2026-11-04 11:00:00)
Last Restarted
5d 7h 11m ago (2026-10-30 06:33:40)
Last Changed Address
2026-06-02 19:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Evaluated 2026-11-04 13:45 UTC. /details snapshot 2026-11-04 11:00:00 UTC (cached 42s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 6h 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 (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
https://NiceVPS.net
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1
69022EDC564591DDC51FAC44CC6937434754D231 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Platform
Linux — Tor 0.4.9.15 on Linux
Version
0.4.9.15 — Recommended
Version Status
Recommended

DNS Health
Status
Healthy (avg. 19.3s, 97th percentile)
Query Domain
32c5ed35d0284d1fad564ac50a39926a.69022edc.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Upstream Resolver
Cloudflare (public resolver)
Cloudflare 76%, Google 24% (~59 estimated queries)
Cross-Validation
3/3 instances succeeded
First Hop
yfnkay (US) E8B7F2E20BED40FEDA3E85A4F2DF3BABE99110C6
Exit Address Used
45.9.148.50
Per-Instance Results
Cross Validation Attempt 1: Success, 20.9s (cv1_w2)
Cross Validation Attempt 2: Success, 19.9s (cv2_w2)
Cross Validation Attempt 3: Success, 17.3s (cv4_w2)
Tested: 2026-11-03 20:09:56 UTC
IPv4 Exit Policy Summary
reject: 
  25
  194
  465
  587
  994
  6657
  6660-6670
  6697
  7000-7005
  7070
  8000-8004
  9000-9001
  9998-9999
IPv6 Exit Policy Summary
reject: 
  25
  194
  465
  587
  994
  6657
  6660-6670
  6697
  7000-7005
  7070
  8000-8004
  9000-9001
  9998-9999
Full 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 45.9.148.50:*
reject *:25
reject *:194
reject *:465
reject *:587
reject *:994
reject *:6657
reject *:6660-6670
reject *:6697
reject *:7000-7005
reject *:7070
reject *:8000-8004
reject *:9000
reject *:9001
reject *:9998
reject *:9999
accept *:*

Last fetch was at Wed, 04 Nov 2026 13:45:39 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 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 Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 152.0 Mbit/s (M) | 816.0 Kbit/s 152.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 99.4% | 98% 17.1d | 8d 8.5d | 8.4d 5.3d | 5.2d 2026-11-03 18:54:15 152.0 Mbit/s (M)
dannenberg (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 200.0 Mbit/s (M) | 816.0 Kbit/s 200.0 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s 99.6% | 98% 17.8d | 8d 10.3d | 9.3d 5.3d | 5.3d 2026-11-03 18:54:15 200.0 Mbit/s (M)
dizum (NL) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 97.7% | 98% 13.9d | 8d 6.3d | 6.7d 5.3d | 5.3d 2026-11-03 18:54:15 80.0 Mbit/s (R)
faravahar (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 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% 14.2d | 8d 6.0d | 6.5d 5.3d | 5.3d 2026-11-03 18:54:15 80.0 Mbit/s (R)
gabelmoo (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 240.0 Mbit/s (M) | 816.0 Kbit/s 240.0 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 99.6% | 98% 17.7d | 8d 10.4d | 10.8d 5.3d | 5.3d 2026-11-03 18:54:15 240.0 Mbit/s (M)
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 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% 18.0d | 8d 10.4d | 10.9d 5.3d | 5.3d 2026-11-03 18:54:15 80.0 Mbit/s (R)
maatuska (SE) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.0% | 98% 13.3d | 8d 3.6d | 2.4d 5.3d | 5.3d 2026-11-03 18:54:15 80.0 Mbit/s (R)
moria1 (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 144.0 Mbit/s (M) | 8.4 Mbit/s 144.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 99.5% | 98% 9.8d | 8d 6648.8d | 7607.5d 5.3d | 5.3d 2026-11-03 18:54:15 144.0 Mbit/s (M)
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 216.0 Mbit/s (M) | 816.0 Kbit/s 216.0 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s 99.6% | 98% 17.8d | 8d 10.3d | 10.6d 5.3d | 5.3d 2026-11-03 18:54:15 216.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.