View Relay "PrivacyMatters"

Fingerprint: 9700CF4518FCE35C6D2D9C352E490574F8C6BEB2 | Family: 1 relay | tor (at) privacymatte.rs | AS207656 | Ukraine | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, MiddleOnly, BadExit (4)
BW Verified
4/6 BW Auths Measured
Stability
Not Overloaded | UP 14h 51m 2s ago | UP 1% (1M)
Reachability
IPv4: 9/9 | v6: 8/8 (Directory Auths)
First Seen
1y 4mo 4w ago
BW Weight
0.00% of Network | 0 Kbit/s Observed By Relay
Version
0.4.8.16 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: 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: requires V2Dir (tunnelled-dir-server) : HSDir requires the relay to support tunnelled directory requests (V2Dir flag). This relay is missing V2Dir — the descriptor likely does not include tunnelled-dir-server, usually because DirCache 0 is set in torrc.
    Suggestion: Remove DirCache 0 from torrc (DirCache is enabled by default in Tor ≥0.3.3). Restart Tor and verify the descriptor includes tunnelled-dir-server. You can check with: grep tunnelled-dir-server /var/lib/tor/cached-descriptors
  • HSDir: Time Known below threshold : Time Known 13.9 hours below 25 hours (dir-spec default)
    Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.
  • BadExit flag assigned : This relay has been flagged as a bad exit by directory authorities. BadExit means authorities detected malicious behavior (traffic modification, SSL stripping, etc.).
    Suggestion: Contact bad-relays@lists.torproject.org to understand and resolve this issue.
  • MiddleOnly restriction active : This relay has been restricted to middle position only by directory authorities. MiddleOnly removes Guard, Exit, HSDir, and V2Dir flags, and adds BadExit. This significantly limits the relay's role in the network.
    Suggestion: This may indicate suspicious behavior patterns, Sybil risk indicators, or policy violations. Contact bad-relays@lists.torproject.org for more information.
  • Tor version not recommended : Running Tor version 0.4.8.16 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
193.218.118.56:8443
[2a0f:e586:f:f:9405:a52b:796f:aff2]:8443
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
Location
Country
Ukraine Ukraine
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS207656
AS Name
Epinatura LLC (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 3 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, MiddleOnly, BadExit
Eligible Flags (3): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 0/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/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
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 Below (0/9 DA) No DirPort, no tunnelled-dir-server (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Below (0/9 DA) 0 bit/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: 0.6d (0/9 DA above threshold)
Min/Max: 0.6d / 0.6d (9/9 DA, Voting / Total Eligible)		 ≥7.8d - 11.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8667.2d
Uptime Below (0/9 DA) 0.6d (R) ≥7.0d - 7.4d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (0/9 DA) 0/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 ≥7.8d - 11.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8667.2d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (9/9 DA) Majority: 100.0% (9/9 DA) ≥98.0% (≥5/9 DA)
Time Known Below (0/9 DA) Median: 0.6d (0/9 DA above threshold)
Min/Max: 0.6d / 0.6d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Below (0/9 DA) 0/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 ≥7.8d - 11.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8667.2d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (9/9 DA) Majority: 100.0% (9/9 DA) ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 7.4 more days) Median: 0.6d (0/9 DA above threshold)
Min/Max: 0.6d / 0.6d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 0 bit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-336.0 Mbit/s (≥5/9 DA)
Exit Exit Policy Partial (0/9 DA) (only port 80) Port 80: Yes | Port 443: Yes (R) Allows ≥1 /8 on ports 80 AND 443 (≥5/9 DA)
MiddleOnly Restriction (by DA) Flagged (9/9 DA) 9/9 authorities assigned MiddleOnly Suspicious behavior, Sybil risk, or policy violation
BadExit Restriction (by DA) Flagged (5/9 DA) 5/9 authorities assigned BadExit Exit traffic manipulation, SSL stripping, or policy violation

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

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-08-14 06:45:11

Measured By
4/6 Bandwidth Authorities
Not measured by: faravahar, longclaw
Median Measurement
0 bit/s
Min / Max
0 bit/s / 8 bit/s
Network Participation: Consensus Weight: 0.0000% of network (0th pctl) | Guard: N/A | Middle: 0.0000% (0th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 14h 51m 2s ago
Overall Uptime (1M/6M/1Y/5Y)
1.5%/0.0%/0.0%/22.1%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (1.5%/0.0%/0.0%/22.1%)
Hibernating
No
Timestamps
First Seen
1y 4mo 4w ago (2025-03-18 00:00:00)
Last Seen
1h 45m 43s ago (2026-08-14 05:00:00)
Last Restarted
14h 51m 2s ago (2026-08-13 15:54:41)
Last Changed Address
2026-08-13 17:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-08-13 23:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
tor (at) privacymatte.rs
Family Configuration
Family Support
MyFamily Only (1) — Legacy only. Consider migrating to Happy Families.
Happy Families (family-cert)
Effective Members: 0
none

Software and Version

Platform
Linux — Tor 0.4.8.16 on Linux
Version
0.4.8.16 — 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: 
  25
  119
  135-139
  445
  563
  1214
  4661-4666
  6346-6429
  6699
  6881-6999
IPv6 Exit Policy Summary
None
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 193.218.118.56:*
reject *:25
reject *:119
reject *:135-139
reject *:445
reject *:563
reject *:1214
reject *:4661-4666
reject *:6346-6429
reject *:6699
reject *:6881-6999
accept *:*

Last fetch was at Fri, 14 Aug 2026 06:45:41 GMT.

Consensus Evaluation

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

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 v6 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 Yes N Yes Yes Running, Valid, MiddleOnly 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.6d | 8d 0.6d | 7.8d 0.6d | 7.0d 100.0% | 98.0% 0.6d | 1.0d 2026-08-13 15:54:50 —
dannenberg (DE) Yes Yes No Yes Y Yes Yes Running, Valid, MiddleOnly 0 bit/s | 816.0 Kbit/s 0 bit/s | 336.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.6d | 8d 0.6d | 11.3d 0.6d | 7.2d 100.0% | 98.0% 0.6d | 1.0d 2026-08-13 15:54:50 8 bit/s
dizum (NL) Yes Yes No Yes N Yes Yes Running, Valid, MiddleOnly 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.6d | 8d 0.6d | 10.8d 0.6d | 7.4d 100.0% | 98.0% 0.6d | 1.0d 2026-08-13 15:54:50 —
faravahar (US) Yes Yes No Yes Y Yes Yes Running, Valid, MiddleOnly, BadExit 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.6d | 8d 0.6d | 10.9d 0.6d | 7.4d 100.0% | 98.0% 0.6d | 1.0d 2026-08-13 15:54:50 —
gabelmoo (DE) Yes Yes No Yes Y Yes Yes Running, Valid, MiddleOnly, BadExit 0 bit/s | 816.0 Kbit/s 0 bit/s | 312.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.6d | 8d 0.6d | 13.0d 0.6d | 7.4d 100.0% | 98.0% 0.6d | 1.0d 2026-08-13 15:54:50 8 bit/s
longclaw (US) Yes Yes No Yes Y Yes — Running, Valid, MiddleOnly, BadExit 0 bit/s | 816.0 Kbit/s 0 bit/s | 232.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.6d | 8d 0.6d | 18.0d 0.6d | 8.0d 100.0% | 98.0% 0.6d | 1.0d 2026-08-13 15:54:50 —
maatuska (SE) Yes Yes No Yes N Yes Yes Running, Valid, MiddleOnly 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.6d | 8d 0.6d | 11.1d 0.6d | 7.4d 100.0% | 98.0% 0.6d | 1.0d 2026-08-13 15:54:50 —
moria1 (US) Yes Yes No Yes Y Yes Yes Running, Valid, MiddleOnly, BadExit 0 bit/s | 8.4 Mbit/s 0 bit/s | 232.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.6d | 8d 0.6d | 8667.2d 0.6d | 7.3d 100.0% | 98.0% 0.6d | 9.9d 2026-08-13 15:54:50 8 bit/s
tor26 (AT) Yes Yes No Yes Y Yes Yes Running, Valid, MiddleOnly, BadExit 0 bit/s | 816.0 Kbit/s 0 bit/s | 312.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.6d | 8d 0.6d | 12.2d 0.6d | 7.4d 100.0% | 98.0% 0.6d | 1.0d 2026-08-13 15:54:50 8 bit/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.