View Relay "cafeine"

Fingerprint: 58EBF3AEBCBFDA4DA2C53BA44AEB5DFA0F63DE18 | Operator: deuza.bzh v2 (3 relays) ⚠ Misconfigured | Family: 2 relays | DeuZa <deuza42@pm.me> 760E 1B07 5183... | AS211619 | Hungary | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Exit (4)
DNS Health
Not Tested (via exitdnshealth.1aeo.com)
BW Verified
0/6 BW Auths Measured
Stability
Not Overloaded | DOWN 3h 15m 40s ago
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
4h 15m 40s ago
BW Weight
0 Kbit/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: WFU below threshold : Weighted Fractional Uptime 38.8% 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.1 days is below 8 days requirement (7.9 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 38.8% 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 3.1 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.

Connectivity and Location

Addresses
OR Address
server26014.maxko-hosting.net
45.9.168.96:9001
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Hungary Hungary
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS211619
AS Name
MAXKO d.o.o. (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.24% consensus weight, 15 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Exit
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 0/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
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 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.0d (0/9 DA above threshold)
Min/Max: 0.0d / 0.1d (9/9 DA, Voting / Total Eligible)		 ≥19.7d - 51.8d (varies) (≥5/9 DA)
[Stricter] moria1: ≥328.3d
Uptime Below (0/9 DA) 0.2d (R) ≥6.6d - 6.6d (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 ≥19.7d - 51.8d (varies) (≥5/9 DA)
[Stricter] moria1: ≥328.3d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 37.3% (0/9 DA above threshold)
Min/Max: 0.0% / 40.9% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Below (0/9 DA) Median: 0.1d (0/9 DA above threshold)
Min/Max: 0.0d / 0.1d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
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 ≥19.7d - 51.8d (varies) (≥5/9 DA)
[Stricter] moria1: ≥328.3d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 37.3% (0/9 DA above threshold)
Min/Max: 0.0% / 40.9% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 7.9 more days) Median: 0.1d (0/9 DA above threshold)
Min/Max: 0.0d / 0.1d (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 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-05-14 22:45:07).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
0.00 Kbit/s
Advertised Bandwidth
Unknown
Rate Limit
922.75 Mbit/s
Burst Limit
1.05 Gbit/s
Total Data
N/A
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-05-14 22:45:07

Measured By
0/6 Bandwidth Authorities
Not measured by: bastet, gabelmoo, longclaw, 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 3h 15m 40s 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
4h 15m 40s ago (2026-05-14 19:00:00)
Last Seen
3h 15m 40s ago (2026-05-14 20:00:00)
Last Restarted
4h 31m 44s ago (2026-05-14 18:43:56)
Last Changed Address
2026-05-14 19:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-05-14 15:00 UTC

AROI Domain (?)
deuza.bzh
Operator Validation
Unvalidated
This Relay
Unvalidated
Error: No contact information
Contact
DeuZa <deuza42@pm.me> 760E 1B07 5183 80A1 1656 8B75 7706 90F2 2EBF 4742 | url:deuza.bzh proof:dns-rsa ciissversion:2 | Exit Node: Malicious traffic may originate from this IP, but it is not controlled by the operator. See https://www.torproject.org/ AND https://metrics.torproject.org/exonerator.html for more information.
Family Configuration
Family Support
MyFamily Only (2) — Legacy only. Consider migrating to Happy Families. | View Full Family (2)
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Members: 2 
58EBF3AEBCBFDA4DA2C53BA44AEB5DFA0F63DE18 (this relay)
E14A551A953D3EC38510FA83F53DE3FF2C0D50CD
Alleged Members: 0
none
Indirect Members: 0
none

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
Status
Not Tested
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 
  43
  53
  80
  443
  853
  989-990
  993
  995
  2082-2083
  2086-2087
  2095-2096
  5222
  6660-6669
  6697
  8080
  8443
  9418
  11371
  64738
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 45.9.168.96:*
accept *:43
accept *:53
accept *:80
accept *:443
accept *:853
accept *:989
accept *:990
accept *:993
accept *:995
accept *:2082-2083
accept *:2086-2087
accept *:2095-2096
accept *:5222
accept *:6660-6669
accept *:6697
accept *:8080
accept *:8443
accept *:9418
accept *:11371
accept *:64738
reject *:*

Last fetch was at Thu, 14 May 2026 23:15:38 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-05-14 22:45: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 Yes — Y Yes Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 224.0 Mbit/s OR 16.0 Mbit/s 38.8% | 98% 0.1d | 8d 0.1d | 51.0d 0.2d | 6.6d 38.8% | 98.0% 0.1d | 1.0d 2026-05-14 18:47:18 —
dannenberg (DE) Yes Yes Yes — N Yes Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 34.6% | 98% 0.1d | 8d 0.0d | 49.9d 0.2d | 6.6d 34.6% | 98.0% 0.1d | 1.0d 2026-05-14 18:47:18 —
dizum (NL) Yes Yes Yes — N Yes Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 37.3% | 98% 0.1d | 8d 0.0d | 19.7d 0.2d | 6.6d 37.3% | 98.0% 0.1d | 1.0d 2026-05-14 18:47:18 —
faravahar (US) Yes Yes Yes — N Yes Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 38.4% | 98% 0.1d | 8d 0.0d | 51.8d 0.2d | 6.6d 38.4% | 98.0% 0.1d | 1.0d 2026-05-14 18:47:18 —
gabelmoo (DE) Yes Yes Yes — Y Yes Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 320.0 Mbit/s OR 16.0 Mbit/s 34.0% | 98% 0.1d | 8d 0.0d | 52.3d 0.2d | 6.6d 34.0% | 98.0% 0.1d | 1.0d 2026-05-14 18:47:18 —
longclaw (US) Yes Yes Yes — Y Yes Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 256.0 Mbit/s OR 16.0 Mbit/s 40.9% | 98% 0.1d | 8d 0.1d | 58.6d 0.2d | 6.6d 40.9% | 98.0% 0.1d | 1.0d 2026-05-14 18:47:18 —
maatuska (SE) Yes Yes Yes — Y Yes Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 336.0 Mbit/s OR 16.0 Mbit/s 33.1% | 98% 0.1d | 8d 0.0d | 23.2d 0.2d | 6.6d 33.1% | 98.0% 0.1d | 1.0d 2026-05-14 18:47:18 —
moria1 (US) Yes Yes Yes — Y Yes Valid, V2Dir, Exit 0 bit/s | 8.4 Mbit/s 0 bit/s | 232.0 Mbit/s OR 16.0 Mbit/s 0.0% | 98% 0.0d | 8d 0.0d | 328.3d 0.2d | 6.6d 0.0% | 98.0% 0.0d | 9.8d 2026-05-14 18:47:18 —
tor26 (AT) Yes Yes Yes — Y Yes Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 304.0 Mbit/s OR 16.0 Mbit/s 40.2% | 98% 0.1d | 8d 0.1d | 55.0d 0.2d | 6.7d 40.2% | 98.0% 0.1d | 1.0d 2026-05-14 18:47:18 —

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