View Relay "overvpn"

Fingerprint: BFC49E31852AFDC14B7493236EB2F0D2B8F9CD88 | Family: 1 relay | somebody@earth | AS49453 | Netherlands | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Exit (4)
DNS Health
Healthy (14.2s, 23rd percentile) (via exitdnshealth.1aeo.com)
BW Verified
3/6 BW Auths Measured 28 Kbit/s Median
Stability
Not Overloaded | DOWN 2h 46m 39s ago
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
3d 14h 46m ago
BW Weight
0.00% of Network | 28 Mbit/s Observed By Relay
Version
0.4.9.6 Recommended
Issues Detected:
  • Guard: requires Fast flag : Guard flag requires having the Fast flag first
    Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
  • 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: WFU below threshold : Weighted Fractional Uptime 14.7% is below 98% requirement
    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.
  • Guard: Time Known below threshold : Time Known 0.6 days is below 8 days requirement (7.4 more days needed)
    Suggestion: Time Known tracks how long authorities have observed your relay. This resets if: 1) Identity key changes, 2) Long downtime makes authorities forget you. Just keep running stably.
  • Not eligible for Stable flag : Uptime or MTBF below network median for most authorities
    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: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
  • 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.
  • HSDir: WFU below threshold : WFU 14.7% below 98% required for HSDir
    Suggestion: HSDir requires ≥98% WFU, Stable flag, and Time Known ≥25 hours (or ~10 days for moria1). Improve uptime consistency.
  • HSDir: Time Known below threshold : Time Known 15.2 hours below 25 hours (dir-spec default)
    Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.
  • 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.
Notes:
  • Bandwidth authority measurements below majority: 3/6 bandwidth authorities measured this relay (majority is 4).

Connectivity and Location

Addresses
OR Address
connected-by.global-layer.com
134.19.178.162:35799
[2a00:1678:2470:99:6c72:4a9c:a493:f2d2]:35799
Exit Address
185.65.133.196
89.37.63.80
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Netherlands Netherlands
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS49453
AS Name
Global Layer B.V. (BGP.tools)
AS Rarity
Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Exit
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 4/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/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 (5/5 DA) 5/5 tested authorities reached relay ≥3/5 tested (majority) (≥3/5 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) 28.9 Mbit/s (R) ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (0/9 DA) Median: 2.6d (0/9 DA above threshold)
Min/Max: 0.0d / 3.6d (9/9 DA, Voting / Total Eligible)		 ≥38.3d - 62.2d (varies) (≥5/9 DA)
Uptime Below (0/9 DA) 2.6d (R) ≥8.3d - 11.1d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (4/9 DA) 4/9 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (0/9 DA) 0/9 DA assigned Stable ≥38.3d - 62.2d (varies) (≥5/9 DA)
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (5/9 DA) Majority: 100.0% (5/9 DA)
Min/Med/Max: 14.4% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (7/9 DA) Median: 3.1d (0/9 DA above threshold)
Min/Max: 0.6d / 3.6d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Below (4/9 DA) 4/9 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (0/9 DA) 0/9 DA assigned Stable ≥38.3d - 62.2d (varies) (≥5/9 DA)
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (5/9 DA) Majority: 100.0% (5/9 DA)
Min/Med/Max: 14.4% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 4.9 more days) Median: 3.1d (0/9 DA above threshold)
Min/Max: 0.6d / 3.6d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 28.9 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-312.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-04-20 10:15:08).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
28.85 Mbit/s
Advertised Bandwidth
28.85 Mbit/s
Rate Limit
83.89 Mbit/s
Burst Limit
167.77 Mbit/s
Total Data
5.1 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-04-20 10:15:08

Measured By
3/6 Bandwidth Authorities
Not measured by: bastet, maatuska, tor26
Median Measurement
28.8 Kbit/s
Min / Max
0 bit/s / 28.8 Kbit/s
Deviation
28.8 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (0th pctl) | Guard: N/A | Middle: N/A | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
DOWN 2h 46m 39s ago
Overall Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (0.0%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
3d 14h 46m ago (2026-04-16 20:00:00)
Last Seen
2h 46m 39s ago (2026-04-20 08:00:00)
Last Restarted
2d 15h 3m ago (2026-04-17 19:42:56)
Last Changed Address
2026-04-16 20:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-04-20 03:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
somebody@earth
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
BFC49E31852AFDC14B7493236EB2F0D2B8F9CD88 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

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

Exit Health & Policy

DNS Health
Status
Healthy (avg. 14.2s, 23rd percentile)
Query Domain
36939b2243554a70adb86bebc17ffc63.bfc49e31.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
1/1 instances succeeded
First Hop
prsv (NL) 88D4E2A8211DBBDF9FEA7194C72BF36860D49799
Exit Address Used
134.19.178.162
Per-Instance Results
Cross Validation Attempt 1: Success, 14.2s (cv3_w3)
Tested: 2026-04-20 07:13:57 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
reject: 
  25
  137-139
  445
IPv6 Exit Policy Summary
reject: 
  25
  137-139
  445
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 134.19.178.162:*
reject *:25
reject *:137
reject *:138
reject *:139
reject *:445
accept *:*

Last fetch was at Mon, 20 Apr 2026 10:46:38 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-04-20 10:15:08).

Per-Authority Details

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 (Relay|T) Guard BW (Relay|Threshold) Guard WFU (M|T) Guard TK (M|T) Stable MTBF (M|T) Stable Uptime (Relay|T) HSDir WFU (M|T) HSDir TK (M|T) Desc Published Cons Wt (Authority)
bastet (US) Yes Yes Yes — Y Yes Valid, V2Dir, Exit 28.9 Mbit/s | 816.0 Kbit/s 28.9 Mbit/s | 200.0 Mbit/s OR 16.0 Mbit/s 14.7% | 98% 0.6d | 8d 0.0d | 62.2d 2.6d | 8.3d 14.7% | 98.0% 0.6d | 1.0d 2026-04-16 20:18:48 —
dannenberg (DE) Yes Yes Yes — N Yes Valid, V2Dir, Fast, Exit 28.9 Mbit/s | 816.0 Kbit/s 28.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 38.7% | 98% 3.1d | 8d 0.0d | 38.3d 2.6d | 11.1d 38.7% | 98.0% 3.1d | 1.0d 2026-04-20 09:16:06 28.8 Kbit/s
dizum (NL) Yes Yes Yes — N Yes Valid, V2Dir, Fast, Exit 28.9 Mbit/s | 816.0 Kbit/s 28.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 37.5% | 98% 3.1d | 8d 0.0d | 40.3d 2.6d | 11.1d 37.5% | 98.0% 3.1d | 1.0d 2026-04-20 09:16:06 28.8 Kbit/s
faravahar (US) Yes Yes Yes — N Yes Valid, V2Dir, Fast, Exit 28.9 Mbit/s | 816.0 Kbit/s 28.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 14.4% | 98% 3.0d | 8d 0.0d | 61.2d 2.6d | 11.1d 14.4% | 98.0% 3.0d | 1.0d 2026-04-20 09:16:06 28.8 Kbit/s
gabelmoo (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 28.9 Mbit/s | 816.0 Kbit/s 28.9 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.6d | 8d 3.6d | 63.0d 2.6d | 11.1d 100.0% | 98.0% 3.6d | 1.0d 2026-04-20 09:16:06 8 bit/s
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 28.9 Mbit/s | 816.0 Kbit/s 28.9 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.6d | 8d 3.6d | 62.3d 2.6d | 11.1d 100.0% | 98.0% 3.6d | 1.0d 2026-04-20 09:16:06 10.4 Kbit/s
maatuska (SE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 28.9 Mbit/s | 816.0 Kbit/s 28.9 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.6d | 8d 2.6d | 61.4d 2.6d | 10.2d 100.0% | 98.0% 2.6d | 1.0d 2026-04-18 19:34:02 28.8 Kbit/s
moria1 (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 28.9 Mbit/s | 8.4 Mbit/s 28.9 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.0d | 8d 3.5d | 303.7d 2.6d | 11.0d 100.0% | 98.0% 3.0d | 9.9d 2026-04-20 03:28:05 8 bit/s
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 28.9 Mbit/s | 816.0 Kbit/s 28.9 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.6d | 8d 3.6d | 63.2d 2.6d | 11.1d 100.0% | 98.0% 3.6d | 1.0d 2026-04-20 09:16:06 28.8 Kbit/s

— = not tested/available • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known

Bandwidth Values Explained:
Relay Reported = Your relay's self-reported bandwidth from its descriptor (observed_bandwidth). Used for flag eligibility (Guard, Fast).
Authority Measured = Bandwidth measured by authority's sbws scanner. Used for consensus weight (path selection probability).
Why different? Authorities verify your reported bandwidth independently. 6 of 9 authorities run bandwidth scanners; 3 use relay-reported values directly.
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.