View Relay "defecTOR"

Fingerprint: 90A4D98D290AF2790EA6F977B465F036CB31BBA1 | Operator: deuza.bzh (6 relays) ✓ Validated | Family: 1 relay | DeuZa <deuza42@pm.me> 760E 1B07 5183... | AS16276 | Canada | Linux

Health Status

Consensus
In Consensus (7/7 Directory Auths)
Flags
Running, Valid, V2Dir, Exit (4)
DNS Health
Not Tested (via exitdnshealth.1aeo.com)
BW Verified
0/5 BW Auths Measured
Stability
Not Overloaded | UP 3h 32m 47s ago
Reachability
IPv4: 7/9 | v6: 6/8 (Directory Auths)
First Seen
2h 45m 41s ago
BW Weight
0 Kbit/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: 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: Time Known below threshold : Time Known 1.6 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/5 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.
Notes:
  • Partial IPv4 reachability: 7/9 authorities can reach this relay

Connectivity and Location

Addresses
OR Address
hermine.deuza.bzh
144.217.79.193:9001
[2607:5300:203:13c1::1]:9001
Reachability (Directory Authorities)
IPv4
7/9
IPv6
6/8 (1 don't test)
Location
Country
Canada Canada
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS16276
AS Name
OVH SAS (BGP.tools)
AS Rarity
Common (score: 0/5, 11.66% consensus weight, 194 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Exit
Eligible Flags (4): Running: 7/7 | Valid: 7/7 | V2Dir: 7/7 | Fast: 0/7 | Stable: 0/7 | HSDir: 0/7 | Guard: 0/7 | Exit: 7/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
IPv6 Reachability Meets (6/6 DA) 6/6 tested authorities reached relay ≥4/6 tested (majority) (≥4/6 DA)
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 (0/7 DA) Median: 0.1d (0/7 DA above threshold)
Min/Max: 0.1d / 0.1d (7/7 DA, Voting / Total Eligible)		 ≥16.1d - 54.3d (varies) (≥4/7 DA)
[Stricter] moria1: ≥336.6d
Uptime Below (0/7 DA) 0.1d (R) ≥9.9d - 9.9d (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 (0/7 DA) 0/7 DA assigned Stable ≥16.1d - 54.3d (varies) (≥4/7 DA)
[Stricter] moria1: ≥336.6d
Prereq: V2Dir Meets (7/7 DA) 7/7 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥4/7 DA)
WFU Meets (7/7 DA) Majority: 100.0% (7/7 DA) ≥98.0% (≥4/7 DA)
Time Known Below (0/7 DA) Median: 0.1d (0/7 DA above threshold)
Min/Max: 0.1d / 0.1d (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 (0/7 DA) 0/7 DA assigned Stable ≥16.1d - 54.3d (varies) (≥4/7 DA)
[Stricter] moria1: ≥336.6d
Prereq: V2Dir Meets (7/7 DA) 7/7 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥4/7 DA)
WFU Meets (7/7 DA) Majority: 100.0% (7/7 DA) ≥98% (≥4/7 DA)
Time Known Below (0/7 DA) (need 7.9 more days) Median: 0.1d (0/7 DA above threshold)
Min/Max: 0.1d / 0.1d (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-320.0 Mbit/s (≥4/7 DA)
Exit Exit Policy Meets (7/7 DA) Port 80: Yes | Port 443: Yes (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-05-03 05:15: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-03 05:15:07

Measured By
0/5 Bandwidth Authorities
Not measured by: 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
UP 3h 32m 47s 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
2h 45m 41s ago (2026-05-03 03:00:00)
Last Seen
1h 45m 41s ago (2026-05-03 04:00:00)
Last Restarted
3h 32m 47s ago (2026-05-03 02:12:54)
Last Changed Address
2026-05-03 03:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

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

AROI Domain (?)
deuza.bzh
Operator Validation
Validated (1/6 relays)
This Relay
Unvalidated
Error: DNS-RSA: Lookup failed: The DNS response does not contain an answer to the question: 90a4d98d290af2790ea6f977b465f036cb31bba1.deuza.bzh. IN TXT
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
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
90A4D98D290AF2790EA6F977B465F036CB31BBA1 (this relay)
Alleged Member: 1
(they don't list you back) 
24361A58CE048807CB15FB0D69B056AB7D980010
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
Not Tested
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 
  43
  53
  80
  110
  143
  443
  989-990
  993
  995
  5222
  6660-6669
IPv6 Exit Policy Summary
accept: 
  43
  53
  80
  110
  143
  443
  989-990
  993
  995
  1293
  5222
  6660-6669
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 144.217.79.193:*
accept *:43
accept *:53
accept *:80
accept *:110
accept *:143
accept *:443
accept *:989
accept *:990
accept *:993
accept *:995
accept *:5222
accept *:6660-6669
reject *:*

Last fetch was at Sun, 03 May 2026 05:45:39 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-05-03 05: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 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) No — — — N No — — — — — — — — — — — —
dannenberg (DE) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 48.6d 0.1d | 9.9d 100.0% | 98.0% 0.1d | 1.0d 2026-05-03 02:17:47 —
dizum (NL) No — — — N No — — — — — — — — — — — —
faravahar (US) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 54.8d 0.1d | 9.9d 100.0% | 98.0% 0.1d | 1.0d 2026-05-03 02:17:47 —
gabelmoo (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 304.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 54.3d 0.1d | 9.9d 100.0% | 98.0% 0.1d | 1.0d 2026-05-03 02:17:47 —
longclaw (US) Yes Yes Yes — Y Yes — Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 240.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 59.0d 0.1d | 9.9d 100.0% | 98.0% 0.1d | 1.0d 2026-05-03 02:17:47 —
maatuska (SE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 320.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 16.1d 0.1d | 9.9d 100.0% | 98.0% 0.1d | 1.0d 2026-05-03 02:17:47 —
moria1 (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 8.4 Mbit/s 0 bit/s | 224.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 336.6d 0.1d | 9.9d 100.0% | 98.0% 0.1d | 9.9d 2026-05-03 02:17:47 —
tor26 (AT) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 288.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 54.3d 0.1d | 9.9d 100.0% | 98.0% 0.1d | 1.0d 2026-05-03 02:17:47 —

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