View Relay "yoann"

Fingerprint: 0726DB131E3916625C24E361216C66903120F58A | Family: 2 relays | Administratorrolland22@gmail.com | AS206996 | Germany | Windows

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Fast, Exit (5)
DNS Health
DNS wrong_ip (failed last 3 scans) (via exitdnshealth.1aeo.com)
BW Verified
4/7 BW Auths Measured 6536 bit/s Median
Stability
Not Overloaded | UP 1d 13h 54m ago
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
4d 16h 45m ago
BW Weight
0.00% of Network | 6 Mbit/s Observed By Relay
Version
0.4.9.7 Recommended
Issues Detected:
  • 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: bandwidth below threshold : Observed bandwidth 0.8 MB/s is below 2 MB/s minimum (AuthDirGuardBWGuarantee)
    Suggestion: Guard requires ≥2 MB/s bandwidth OR being in top 25% of network. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx or ARM.
  • 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 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.
  • 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.

Connectivity and Location

Addresses
OR Address
pink-cat-38907.zap.cloud
185.249.198.156:9001
Exit Address
185.249.198.156
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS206996
AS Name
ZAP-Hosting GmbH (BGP.tools)
AS Rarity
Epic (score: 3/5, 0.08% consensus weight, 5 operators)

Flags and Eligibility

Current Flags (5): Running, Valid, V2Dir, Fast, Exit
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 5/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 Meets (9/9 DA) 6.5 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 (0/9 DA) Median: 4.7d (0/9 DA above threshold)
Min/Max: 4.7d / 4.7d (9/9 DA, Voting / Total Eligible)		 ≥21.2d - 52.1d (varies) (≥5/9 DA)
[Stricter] moria1: ≥338.6d
Uptime Below (0/9 DA) 1.6d (R) ≥13.3d - 13.7d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (5/9 DA) 5/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 ≥21.2d - 52.1d (varies) (≥5/9 DA)
[Stricter] moria1: ≥338.6d
Prereq: V2Dir Meets (9/9 DA) 9/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 Meets (8/9 DA) Median: 4.7d (0/9 DA above threshold)
Min/Max: 3.7d / 4.7d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Meets (5/9 DA) 5/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 ≥21.2d - 52.1d (varies) (≥5/9 DA)
[Stricter] moria1: ≥338.6d
Prereq: V2Dir Meets (9/9 DA) 9/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 3.3 more days) Median: 4.7d (0/9 DA above threshold)
Min/Max: 3.7d / 4.7d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 6.5 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 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-27 08:45:07).

Bandwidth Metrics

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

Source: CollecTor — fetched 2026-05-27 08:45:07

Measured By
4/7 Bandwidth Authorities
Not measured by: bastet, dannenberg, maatuska
Median Measurement
6536 bit/s
Min / Max
240 bit/s / 12.0 Kbit/s
Deviation
11.8 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (3th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0001% (1th pctl)

Uptime and Stability

Uptime Metrics
Current Status
UP 1d 13h 54m ago
Overall Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (0.0%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
4d 16h 45m ago (2026-05-22 16:00:00)
Last Seen
1h 45m 44s ago (2026-05-27 07:00:00)
Last Restarted
1d 13h 54m ago (2026-05-25 18:50:56)
Last Changed Address
2026-05-22 16:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-05-27 01:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
Administratorrolland22@gmail.com
Family Configuration
Family Support
None — No family membership configured | View Full Family (2)
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
0726DB131E3916625C24E361216C66903120F58A (this relay)
Alleged Member: 1
(they don't list you back) 
96809111B83F1E3308F8F88ABE4E2E2B7F40DE49
Indirect Members: 0
none

Software and Version

Platform
Windows — Tor 0.4.9.7 on Windows 8 [or later]
Version
0.4.9.7 — Recommended
Version Status
Recommended

Exit Health & Policy

DNS Health
Status
wrong_ip (failed last 3 scans)
Error
DNS Error: Expected 64.65.4.1, got 149.248.211.216
Query Domain
68a8d62e19c84593af389f9f0340c45e.0726db13.tor.exit.validator.1aeo.com
DNS Result
Resolved to 149.248.211.216 (expected 64.65.4.1)
Cross-Validation
0/4 instances succeeded
First Hop
jstark1809n0n0n0 (NO) EEA85567CD7EBEB1CBC70AEE97C45E0019BDBDF9
Exit Address Used
185.249.198.156
Per-Instance Results
Cross Validation Attempt 1: Wrong_ip, 19.6s (cv1_w1)
Cross Validation Attempt 2: Wrong_ip, 15.6s (cv2_w1)
Cross Validation Attempt 3: Wrong_ip, 25.4s (cv3_w1)
Cross Validation Attempt 4: Wrong_ip, 14.4s (cv4_w1)
Tested: 2026-05-26 19:05:23 UTC
Source: exitdnshealth.1aeo.com
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 185.249.198.156:*
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 Wed, 27 May 2026 08:45:43 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-05-27 08: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 Running, Valid, V2Dir, Exit 6.5 Mbit/s | 816.0 Kbit/s 6.5 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 4.7d | 8d 4.7d | 50.7d 1.6d | 13.3d 100.0% | 98.0% 4.7d | 1.0d 2026-05-26 22:03:12 6536 bit/s
dannenberg (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 6.5 Mbit/s | 816.0 Kbit/s 6.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 4.7d | 8d 4.7d | 46.5d 1.6d | 13.6d 100.0% | 98.0% 4.7d | 1.0d 2026-05-26 22:03:12 6536 bit/s
dizum (NL) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Exit 6.5 Mbit/s | 816.0 Kbit/s 6.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 4.7d | 8d 4.7d | 21.2d 1.6d | 13.6d 100.0% | 98.0% 4.7d | 1.0d 2026-05-26 22:03:12 6536 bit/s
faravahar (US) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Exit 6.5 Mbit/s | 816.0 Kbit/s 6.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 4.7d | 8d 4.7d | 52.1d 1.6d | 13.7d 100.0% | 98.0% 4.7d | 1.0d 2026-05-26 22:03:12 6536 bit/s
gabelmoo (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 6.5 Mbit/s | 816.0 Kbit/s 6.5 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 4.7d | 8d 4.7d | 53.0d 1.6d | 13.8d 100.0% | 98.0% 4.7d | 1.0d 2026-05-26 22:03:12 240 bit/s
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 6.5 Mbit/s | 816.0 Kbit/s 6.5 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 4.7d | 8d 4.7d | 57.8d 1.6d | 13.7d 100.0% | 98.0% 4.7d | 1.0d 2026-05-26 22:03:12 12.0 Kbit/s
maatuska (SE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 6.5 Mbit/s | 816.0 Kbit/s 6.5 Mbit/s | 328.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 4.7d | 8d 4.7d | 24.6d 1.6d | 13.5d 100.0% | 98.0% 4.7d | 1.0d 2026-05-26 22:03:12 6536 bit/s
moria1 (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 6.5 Mbit/s | 8.4 Mbit/s 6.5 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.7d | 8d 4.7d | 338.6d 1.6d | 14.1d 100.0% | 98.0% 3.7d | 9.9d 2026-05-26 22:03:12 10.4 Kbit/s
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 6.5 Mbit/s | 816.0 Kbit/s 6.5 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 4.7d | 8d 4.7d | 54.0d 1.6d | 13.7d 100.0% | 98.0% 4.7d | 1.0d 2026-05-26 22:03:12 368 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.