View Relay "imprezahostru01"

Fingerprint: 227E603219E87C01E448B5DA18AF42A5D5C11DD4 | Operator: impreza.host v2 (10 relays) ⚠ Misconfigured | Family: 1 relay | abuse@imprezahost.com... | AS216334 | Russian Federation | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid (2)
BW Verified
1/7 BW Auths Measured 26 Kbit/s Median
Stability
Not Overloaded | DOWN 2d 5h 15m ago
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
2d 10h 15m ago
BW Weight
0.00% of Network | 26 Mbit/s Observed By Relay
Version
0.4.9.8 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 4.7 days is below 8 days requirement (3.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: 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
  • 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.
  • Low bandwidth authority measurements : Only 1/7 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.

Connectivity and Location

Addresses
OR Address
45.154.246.20:443
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Russian Federation Russian Federation
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS216334
AS Name
New Hosting Technologies LLC (BGP.tools)
AS Rarity
Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

Flags and Eligibility

Current Flags (2): Running, Valid
Eligible Flags (3): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 3/9 | Stable: 1/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
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 Meets (9/9 DA) 26.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 (1/9 DA) Median: 0.2d (1/9 DA above threshold)
Min/Max: 0.0d / 20596.1d (9/9 DA, Voting / Total Eligible)		 ≥20.2d - 51.1d (varies) (≥5/9 DA)
[Stricter] moria1: ≥336.1d
Uptime Below (0/9 DA) 4.9d (R) ≥12.4d - 12.8d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (3/9 DA) 3/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 (1/9 DA) 1/9 DA assigned Stable ≥20.2d - 51.1d (varies) (≥5/9 DA)
[Stricter] moria1: ≥336.1d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (3/9 DA) Median: 3.5% (3/9 DA above threshold)
Min/Max: 0.0% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (5/9 DA) Median: 2.3d (0/9 DA above threshold)
Min/Max: 0.0d / 4.7d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Below (3/9 DA) 3/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 (1/9 DA) 1/9 DA assigned Stable ≥20.2d - 51.1d (varies) (≥5/9 DA)
[Stricter] moria1: ≥336.1d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (3/9 DA) Median: 3.5% (3/9 DA above threshold)
Min/Max: 0.0% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 5.7 more days) Median: 2.3d (0/9 DA above threshold)
Min/Max: 0.0d / 4.7d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 26.9 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-328.0 Mbit/s (≥5/9 DA)
Exit Exit Policy Below (0/9 DA) Port 80: No | Port 443: No (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-05-25 09:15:07).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
26.94 Mbit/s
Advertised Bandwidth
26.94 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
504 MB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-05-25 09:15:07

Measured By
1/7 Bandwidth Authorities
Not measured by: bastet, dannenberg, gabelmoo, longclaw, maatuska, moria1
Median Measurement
26.9 Kbit/s
Min / Max
216 bit/s / 26.9 Kbit/s
Deviation
26.7 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (2th pctl) | Guard: N/A | Middle: N/A | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
DOWN 2d 5h 15m 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
2d 10h 15m ago (2026-05-23 00:00:00)
Last Seen
2d 5h 15m ago (2026-05-23 05:00:00)
Last Restarted
4d 20h 33m ago (2026-05-20 13:42:14)
Last Changed Address
2026-05-23 00:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-05-25 02:00 UTC

AROI Domain (?)
impreza.host
Operator Validation
Unvalidated
This Relay
Unvalidated
Error: URI-RSA: HTTP error 404 for impreza.host at URL: https://impreza.host/.well-known/tor-relay/rsa-fingerprint.txt; URI-RSA: HTTP error 526 for www.impreza.host at URL: https://www.impreza.host/.well-known/tor-relay/rsa-fingerprint.txt
Contact
abuse@imprezahost.com url:https://impreza.host proof:uri-rsa ciissversion:2 pgp:3C2965342A3DEE7AD712C227B67B73DDD6B62929 abuse:abuse@imprezahost.com hoster:imprezahost.com uplinkbw:1000 trafficacc:metered virtualization:kvm os:Linux/Debian autoupdate:yes offlinemasterkey:yes signingkeylifetime:90
Family Configuration
Family Support
Both — Happy Families (10 / 100%) and MyFamily (0 / 0%)

Software and Version

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

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 Mon, 25 May 2026 10:15:37 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-05-25 09:15:07).

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 Running, Valid 26.9 Mbit/s | 816.0 Kbit/s 26.9 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 4.7d | 8d 4.7d | 50.6d 4.9d | 12.4d 100.0% | 98.0% 4.7d | 1.0d 2026-05-25 03:32:42 26.9 Kbit/s
dannenberg (DE) Yes Yes No — Y Yes Valid, Fast 26.9 Mbit/s | 816.0 Kbit/s 26.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 38.6% | 98% 3.9d | 8d 0.2d | 44.5d 4.9d | 12.8d 38.6% | 98.0% 3.9d | 1.0d 2026-05-25 03:32:42 26.9 Kbit/s
dizum (NL) Yes Yes No — N Yes Valid, Fast 26.9 Mbit/s | 816.0 Kbit/s 26.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 0.0% | 98% 0.0d | 8d 0.0d | 20.2d 4.9d | 12.8d 0.0% | 98.0% 0.0d | 1.0d 2026-05-25 03:32:42 26.9 Kbit/s
faravahar (US) Yes Yes No — N Yes Valid, Fast 26.9 Mbit/s | 816.0 Kbit/s 26.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 3.0% | 98% 2.3d | 8d 0.0d | 51.1d 4.9d | 12.9d 3.0% | 98.0% 2.3d | 1.0d 2026-05-25 03:32:42 26.9 Kbit/s
gabelmoo (DE) Yes Yes No — Y Yes Valid 26.9 Mbit/s | 816.0 Kbit/s 26.9 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 0.0% | 98% 0.0d | 8d 0.0d | 51.9d 4.9d | 12.9d 0.0% | 98.0% 0.0d | 1.0d 2026-05-25 03:32:42 26.9 Kbit/s
longclaw (US) Yes Yes No — Y Yes Running, Valid 26.9 Mbit/s | 816.0 Kbit/s 26.9 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 4.7d | 8d 4.7d | 58.6d 4.9d | 12.8d 100.0% | 98.0% 4.7d | 1.0d 2026-05-25 03:32:42 26.9 Kbit/s
maatuska (SE) Yes Yes No — Y Yes Valid 26.9 Mbit/s | 816.0 Kbit/s 26.9 Mbit/s | 328.0 Mbit/s OR 16.0 Mbit/s 0.0% | 98% 0.0d | 8d 0.0d | 22.8d 4.9d | 12.7d 0.0% | 98.0% 0.0d | 1.0d 2026-05-25 03:32:42 26.9 Kbit/s
moria1 (US) Yes Yes No — Y Yes Valid, Stable 26.9 Mbit/s | 8.4 Mbit/s 26.9 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 3.5% | 98% 2.1d | 8d 20596.1d | 336.1d 4.9d | 13.1d 3.5% | 98.0% 2.1d | 9.9d 2026-05-25 03:32:42 26.9 Kbit/s
tor26 (AT) Yes Yes No — Y Yes Running, Valid 26.9 Mbit/s | 816.0 Kbit/s 26.9 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 4.7d | 8d 4.7d | 53.5d 4.9d | 13.0d 100.0% | 98.0% 4.7d | 1.0d 2026-05-25 03:32:42 216 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.