View Relay "w000000h000004"

Fingerprint: 4F19B88218263778258D3316511AB88DAFC25F2C | Family: 1 relay | http://exitnodev8.v6.rocks | AS21409 | France | Linux

Consensus
In Consensus (9/9 Directory Auths)
DNS Health
Healthy (10.8s, 15th percentile) (via exitdnshealth.1aeo.com)
BW Verified
5/7 BW Auths Measured 8 Mbit/s Median
Stability
Not Overloaded | UP 6d 20h 55m ago | UP 100% (1M)
Reachability
IPv4: 9/9 | v6: 8/8(Directory Auths)
BW Weight
0.00% of Network | 28 Mbit/s Observed By Relay
Version
0.4.9.14 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.14 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 dizum (98.33%, 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.
  • Guard: bandwidth near threshold: Bandwidth counted for Guard is just above the Guard bar at dizum, faravahar, longclaw and maatuska (17.2 Mbit/s, need ≥16.8 Mbit/s) and moria1 (16.8 Mbit/s, need ≥16.8 Mbit/s). The bar is the lower of AuthDirGuardBWGuarantee and that authority's top 25%. A dip in the bandwidth it counts can drop the Guard flag.
    Suggestion: The bandwidth that counts is that authority's measurement when it has one, otherwise the relay-reported rate. Keep it above the lower of AuthDirGuardBWGuarantee (2 MB by default) and that authority's top 25%.

Addresses
OR Address
185.246.84.179:4433
[2a00:c70:1:185:246:84:179:1]:4433
Exit Address
185.246.84.179
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
Location
Country
France France
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS21409
AS Name
Ikoula Net SAS (BGP.tools)
AS Rarity
Epic (score: 3/5, 0.08% consensus weight, 5 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: 8/9 | Guard: 6/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
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) 6.4 Mbit/s – 19.2 Mbit/s (5 DA measured)
17.2 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 Partial (6/9 DA) Median: 11.0d (7/9 DA above threshold)
Min/Max: 2.8d / 2144.4d (9/9 DA, Voting / Total Eligible)
≥2.4d - 9.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7607.5d
Uptime Meets (9/9 DA) 6.9d (R) ≥5.2d - 5.3d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
6.4 Mbit/s – 19.2 Mbit/s (5 DA measured)
17.2 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 Partial (8/9 DA) 6.9d (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
6.4 Mbit/s – 19.2 Mbit/s (5 DA measured)
17.2 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 Meets (9/9 DA) Median: 99.9% (9/9 DA above threshold)
Min/Max: 98.3% / 100.0% (9/9 DA, Voting / Total Eligible)
≥98%; dizum: ≥97.84099999999999% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 18.8d (9/9 DA above threshold)
Min/Max: 9.7d / 22.1d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Partial (6/9 DA) 6.4 Mbit/s – 19.2 Mbit/s (5 DA measured)
17.2 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
28.00 Mbit/s
Advertised Bandwidth
17.20 Mbit/s
Rate Limit
17.20 Mbit/s
Burst Limit
17.20 Mbit/s
Total Data
122 TB (5 years)
1mo: 6.0 TB | 6mo: 32 TB | 1y: 49 TB | 5y: 122 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
8.8 Mbit/s (median of 5 measurements)
Measured Min / Max
6.4 Mbit/s / 19.2 Mbit/s
Deviation
12.8 Mbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0006% of network (16th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0018% (3th pctl)
History

Uptime Metrics
Current Status
UP 6d 20h 55m ago
Overall Uptime (1M/6M/1Y/5Y)
100.0%/100.0%/100.0%/99.7%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (100.0%/100.0%/100.0%/99.7%)
Hibernating
No
Timestamps
First Seen
2y 7mo 1w ago (2024-03-29 13:00:00)
Last Seen
2h 45m 39s ago (2026-11-04 11:00:00)
Last Restarted
6d 20h 55m ago (2026-10-28 16:50:35)
Last Changed Address
2026-10-28 15: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
http://exitnodev8.v6.rocks
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1
4F19B88218263778258D3316511AB88DAFC25F2C (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Platform
Linux — Tor 0.4.9.14 on Linux
Version
0.4.9.14 — Not Recommended
Version Status
Obsolete — Update urgently. See torproject.org/download

DNS Health
Status
Healthy (avg. 10.8s, 15th percentile)
Query Domain
da8f443ca4ce4461bfc48b9b1e844e0f.4f19b882.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Upstream Resolver
Local AS (exit's own network)
Local AS 56%, Local /22 44% (~153 estimated queries)
Cross-Validation
4/4 instances succeeded
First Hop
blackkent (US) 6C82656574A07A1F4E2626DF8663C3CF55CFD4C7
Exit Address Used
185.246.84.179
Per-Instance Results
Cross Validation Attempt 1: Success, 3.3s (cv1_w2)
Cross Validation Attempt 2: Success, 13.9s (cv2_w2)
Cross Validation Attempt 3: Success, 15.1s (cv3_w2)
Cross Validation Attempt 4: Success, 10.8s (cv4_w2)
Tested: 2026-11-03 20:09:41 UTC
IPv4 Exit Policy Summary
reject: 
  22
  25
  119
  135-139
  445
  465
  563
  587
  1214
  2525
  4661-4666
  6025
  6346-6429
  6465
  6660-6669
  6699
  6881-7000
  49002-60632
IPv6 Exit Policy Summary
reject: 
  22
  25
  119
  135-139
  445
  465
  563
  587
  1214
  2525
  4661-4666
  6025
  6346-6429
  6465
  6660-6669
  6699
  6881-7000
  49002-60632
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 185.246.84.179:*
reject *:22
reject *:135-139
reject *:445
reject *:6660-6669
reject *:7000
reject *:49002-60632
reject *:25
reject *:465
reject *:587
reject *:2525
reject *:6025
reject *:6465
reject *:119
reject *:563
reject *:1214
reject *:4661-4666
reject *:6346-6429
reject *:6699
reject *:6881-6999
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 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 Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 19.2 Mbit/s (M) | 816.0 Kbit/s 19.2 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 99.7% | 98% 18.8d | 8d 11.6d | 8.4d 6.9d | 5.2d 2026-11-03 16:51:03 19.2 Mbit/s (M)
dannenberg (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 6.4 Mbit/s (M) | 816.0 Kbit/s 6.4 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 19.2d | 8d 10.8d | 9.3d 6.9d | 5.3d 2026-11-04 10:51:06 6.4 Mbit/s (M)
dizum (NL) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 17.2 Mbit/s (R) | 816.0 Kbit/s 17.2 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 98.3% | 98% 17.1d | 8d 6.3d | 6.7d 6.9d | 5.3d 2026-11-04 10:51:06 17.2 Mbit/s (R)
faravahar (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 17.2 Mbit/s (R) | 816.0 Kbit/s 17.2 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.9% | 98% 19.7d | 8d 11.3d | 6.5d 6.9d | 5.3d 2026-11-04 10:51:06 17.2 Mbit/s (R)
gabelmoo (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 8.8 Mbit/s (M) | 816.0 Kbit/s 8.8 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 99.8% | 98% 17.8d | 8d 9.6d | 10.8d 6.9d | 5.3d 2026-11-04 10:51:06 8.8 Mbit/s (M)
longclaw (US) Yes Yes Yes — Y Yes N/T Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 17.2 Mbit/s (R) | 816.0 Kbit/s 17.2 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.9% | 98% 18.9d | 8d 11.0d | 10.9d 6.9d | 5.3d 2026-11-03 16:51:03 17.2 Mbit/s (R)
maatuska (SE) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 17.2 Mbit/s (R) | 816.0 Kbit/s 17.2 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.1% | 98% 14.9d | 8d 2.8d | 2.4d 6.9d | 5.3d 2026-11-04 10:51:06 17.2 Mbit/s (R)
moria1 (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, Guard, Exit 16.8 Mbit/s (M) | 8.4 Mbit/s 16.8 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 99.9% | 98% 9.7d | 8d 2144.4d | 7607.5d 6.9d | 5.3d 2026-11-04 10:51:06 16.8 Mbit/s (M)
tor26 (AT) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 8.8 Mbit/s (M) | 816.0 Kbit/s 8.8 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 22.1d | 8d 18.6d | 10.6d 6.9d | 5.3d 2026-11-04 10:51:06 8.8 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.