View Relay "segv"

Fingerprint: 7008E27D30A67C57D7C730A3006BAC6FAAEB978F | Family: 1 relay | contactmobile@duck.me | AS14061 | Germany | Linux

Health Status

Consensus
In Consensus (7/7 Directory Auths)
Flags
Running, Valid, V2Dir (3)
BW Verified
0/6 BW Auths Measured
Stability
Not Overloaded | DOWN 17h 45m 41s ago
Reachability
IPv4: 7/7 (Directory Auths)
First Seen
17h 45m 41s ago
BW Weight
0 Kbit/s Observed By Relay
Version
0.4.8.10 Not 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 1.9% 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.7 days is below 8 days requirement (7.3 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 1.9% 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 17.4 hours below 25 hours (dir-spec default)
    Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.
  • 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.
  • Tor version not recommended : Running Tor version 0.4.8.10 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.

Connectivity and Location

Addresses
OR Address
164.90.180.143:443
[2a03:b0c0:3:f0:0:2:aa61:5000]:443
Reachability (Directory Authorities)
IPv4
7/7
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS14061
AS Name
DigitalOcean, LLC (BGP.tools)
AS Rarity
Emerging (score: 1/5, 0.77% consensus weight, 69 operators)

Flags and Eligibility

Current Flags (3): Running, Valid, V2Dir
Eligible Flags (3): Running: 7/7 | Valid: 7/7 | V2Dir: 7/7 | Fast: 0/7 | Stable: 1/7 | HSDir: 0/7 | Guard: 0/7 | Exit: 0/7
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (7/7 DA) 7/7 authorities reached relay ≥4/7 DA ORPort reachable
Valid Descriptor Meets (7/7 DA) 7/7 authorities assigned Valid Not blacklisted + valid descriptor (≥4/7 DA)
V2Dir DirPort Available Meets (7/7 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥4/7 DA)
Fast Speed Below (0/7 DA) 0 bit/s (R) ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (1/7 DA) Median: 0.0d (1/7 DA above threshold)
Min/Max: 0.0d / 20647.6d (7/7 DA, Voting / Total Eligible)		 ≥9.3d - 19.8d (varies) (≥4/7 DA)
[Stricter] moria1: ≥7800.1d
Uptime Below (0/7 DA) 0.8d (R) ≥4.1d - 4.1d (varies) (≥4/7 DA)
HSDir Prereq: Fast Below (0/7 DA) 0/7 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (1/7 DA) 1/7 DA assigned Stable ≥9.3d - 19.8d (varies) (≥4/7 DA)
[Stricter] moria1: ≥7800.1d
Prereq: V2Dir Meets (7/7 DA) 7/7 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥4/7 DA)
WFU Below (0/7 DA) Median: 1.9% (0/7 DA above threshold)
Min/Max: 0.0% / 2.0% (7/7 DA, Voting / Total Eligible)		 ≥98.0% (≥4/7 DA)
Time Known Below (0/7 DA) Median: 0.7d (0/7 DA above threshold)
Min/Max: 0.0d / 0.7d (7/7 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥4/7 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Below (0/7 DA) 0/7 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (1/7 DA) 1/7 DA assigned Stable ≥9.3d - 19.8d (varies) (≥4/7 DA)
[Stricter] moria1: ≥7800.1d
Prereq: V2Dir Meets (7/7 DA) 7/7 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥4/7 DA)
WFU Below (0/7 DA) Median: 1.9% (0/7 DA above threshold)
Min/Max: 0.0% / 2.0% (7/7 DA, Voting / Total Eligible)		 ≥98% (≥4/7 DA)
Time Known Below (0/7 DA) (need 7.3 more days) Median: 0.7d (0/7 DA above threshold)
Min/Max: 0.0d / 0.7d (7/7 DA, Voting / Total Eligible)		 ≥8 days (≥4/7 DA)
Bandwidth Below (0/7 DA) 0 bit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-288.0 Mbit/s (≥4/7 DA)
Exit Exit Policy Below (0/7 DA) Port 80: No | Port 443: No (R) Allows ≥1 /8 on ports 80 AND 443 (≥4/7 DA)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-07-14 08:45:05).

Bandwidth Metrics

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-07-14 08:45:05

Measured By
0/6 Bandwidth Authorities
Not measured by: bastet, dannenberg, faravahar, maatuska, moria1, tor26
Median Measurement
0 bit/s
Min / Max
0 bit/s / 0 bit/s
Network Participation: Consensus Weight: N/A | Guard: N/A | Middle: N/A | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
DOWN 17h 45m 41s 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
17h 45m 41s ago (2026-07-13 15:00:00)
Last Seen
17h 45m 41s ago (2026-07-13 15:00:00)
Last Restarted
18h 20m 49s ago (2026-07-13 14:24:52)
Last Changed Address
2026-07-13 15:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-07-14 01:00 UTC

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

Software and Version

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

Exit Health & Policy

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 Tue, 14 Jul 2026 08:45:40 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-07-14 08:45:05).

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 No — Y Yes Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 1.9% | 98% 0.7d | 8d 0.0d | 29.3d 0.8d | 4.2d 1.9% | 98.0% 0.7d | 1.0d 2026-07-13 14:24:59 —
dannenberg (DE) Yes Yes No — Y Yes Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 248.0 Mbit/s OR 16.0 Mbit/s 1.9% | 98% 0.7d | 8d 0.0d | 9.3d 0.8d | 4.1d 1.9% | 98.0% 0.7d | 1.0d 2026-07-13 14:24:59 —
dizum (NL) Yes Yes No — N Yes Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 2.0% | 98% 0.7d | 8d 0.0d | 18.2d 0.8d | 4.1d 2.0% | 98.0% 0.7d | 1.0d 2026-07-13 14:24:59 —
faravahar (US) Yes Yes No — Y Yes Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 288.0 Mbit/s OR 16.0 Mbit/s 0.0% | 98% 0.0d | 8d 0.0d | 16.0d 0.8d | 4.1d 0.0% | 98.0% 0.0d | 1.0d 2026-07-13 14:24:59 —
maatuska (SE) Yes Yes No — Y Yes Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 280.0 Mbit/s OR 16.0 Mbit/s 1.9% | 98% 0.7d | 8d 0.0d | 19.8d 0.8d | 4.1d 1.9% | 98.0% 0.7d | 1.0d 2026-07-13 14:24:59 —
moria1 (US) Yes Yes No — Y Yes Valid, V2Dir, Stable 0 bit/s | 8.4 Mbit/s 0 bit/s | 232.0 Mbit/s OR 16.0 Mbit/s 2.0% | 98% 0.7d | 8d 20647.6d | 7800.1d 0.8d | 4.1d 2.0% | 98.0% 0.7d | 9.9d 2026-07-13 14:24:59 —
tor26 (AT) Yes Yes No — Y Yes Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 272.0 Mbit/s OR 16.0 Mbit/s 0.0% | 98% 0.0d | 8d 0.0d | 28.6d 0.8d | 4.1d 0.0% | 98.0% 0.0d | 1.0d 2026-07-13 14:24:59 —

— = 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.