View Relay "MyTorExitNode"

Fingerprint: 3F2F720D3E9B58EC6B955BBB1DA99C288814D930 | Family: 1 relay | your@email.com | AS14061 | Germany | Linux

Health Status

Consensus
In Consensus (8/9 Directory Auths)
Flags
Running, Valid, V2Dir, Exit (4)
DNS Health
Healthy (15.3s, 37th percentile) (via exitdnshealth.1aeo.com)
BW Verified
4/6 BW Auths Measured 4196 bit/s Median
Stability
Not Overloaded | UP 1d 22h 34m ago
Reachability
IPv4: 8/9 (Directory Auths)
First Seen
1d 21h 46m ago
BW Weight
0.00% of Network | 8 Mbit/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: bandwidth below threshold : Observed bandwidth 1.1 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 1.9 days is below 8 days requirement (6.1 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.
  • 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.
Notes:
  • Partial IPv4 reachability: 8/9 authorities can reach this relay

Connectivity and Location

Addresses
OR Address
165.227.163.170:9002
Exit Address
165.227.163.170
Reachability (Directory Authorities)
IPv4
8/9
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS14061
AS Name
DigitalOcean, LLC (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.49% consensus weight, 66 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Exit
Eligible Flags (4): Running: 8/9 | Valid: 8/9 | V2Dir: 8/9 | Fast: 3/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 8/9
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (8/9 DA) 8/9 authorities reached relay ≥5/9 DA ORPort reachable
IPv6 Reachability Below (0/1 DA) 0/1 tested authorities reached relay ≥1/1 tested (majority) (≥1/1 DA)
Valid Descriptor Meets (8/9 DA) 8/9 authorities assigned Valid Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir DirPort Available Meets (8/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 8.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: 1.9d (0/9 DA above threshold)
Min/Max: 0.9d / 1.9d (8/9 DA, Voting / Total Eligible)		 ≥38.3d - 62.2d (varies) (≥5/9 DA)
Uptime Below (0/9 DA) 1.9d (R) ≥8.3d - 11.1d (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 (0/9 DA) 0/9 DA assigned Stable ≥38.3d - 62.2d (varies) (≥5/9 DA)
Prereq: V2Dir Meets (8/9 DA) 8/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (8/9 DA) Majority: 100.0% (8/9 DA) ≥98.0% (≥5/9 DA)
Time Known Meets (6/9 DA) Median: 1.9d (0/9 DA above threshold)
Min/Max: 0.9d / 1.9d (8/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 (0/9 DA) 0/9 DA assigned Stable ≥38.3d - 62.2d (varies) (≥5/9 DA)
Prereq: V2Dir Meets (8/9 DA) 8/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (8/9 DA) Majority: 100.0% (8/9 DA) ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 6.1 more days) Median: 1.9d (0/9 DA above threshold)
Min/Max: 0.9d / 1.9d (8/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 8.5 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-312.0 Mbit/s (≥5/9 DA)
Exit Exit Policy Meets (8/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-04-20 10:15:08).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
8.46 Mbit/s
Advertised Bandwidth
8.39 Mbit/s
Rate Limit
8.39 Mbit/s
Burst Limit
16.78 Mbit/s
Total Data
3.0 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-04-20 10:15:08

Measured By
4/6 Bandwidth Authorities
Not measured by: bastet, longclaw
Median Measurement
4196.0 bit/s
Min / Max
8 bit/s / 8.4 Kbit/s
Deviation
8.4 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (0th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0000% (0th pctl)

Uptime and Stability

Uptime Metrics
Current Status
UP 1d 22h 34m 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
1d 21h 46m ago (2026-04-18 13:00:00)
Last Seen
1h 46m 39s ago (2026-04-20 09:00:00)
Last Restarted
1d 22h 34m ago (2026-04-18 12:12:04)
Last Changed Address
2026-04-18 13:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-04-20 03:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
your@email.com
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
3F2F720D3E9B58EC6B955BBB1DA99C288814D930 (this relay)
Alleged Members: 0
none
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
Healthy (avg. 15.3s, 37th percentile)
Query Domain
b677620a5d0b48c7934938f2eeea8acd.3f2f720d.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
3/3 instances succeeded
First Hop
zgato (DE) E7A62C0475EBCA7C64E7C291606197A547C63D27
Exit Address Used
165.227.163.170
Per-Instance Results
Cross Validation Attempt 1: Success, 18.5s (cv1_w1)
Cross Validation Attempt 2: Success, 16.8s (cv2_w1)
Cross Validation Attempt 3: Success, 10.5s (cv3_w1)
Tested: 2026-04-20 07:05:52 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 
  20-21
  43
  53
  80
  110
  143
  220
  443
  873
  989-990
  993
  995
  1194
  5222-5223
  5228
  8080
  8443
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 165.227.163.170:*
accept *:20-21
accept *:43
accept *:53
accept *:80
accept *:110
accept *:143
accept *:220
accept *:443
accept *:873
accept *:989-990
accept *:993
accept *:995
accept *:1194
accept *:5222-5223
accept *:5228
accept *:8080
accept *:8443
reject *:*

Last fetch was at Mon, 20 Apr 2026 10:46:38 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-04-20 10:15:08).

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) No — — — Y No — — — — — — — — — — —
dannenberg (DE) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Exit 8.5 Mbit/s | 816.0 Kbit/s 8.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.9d | 8d 1.9d | 38.3d 1.9d | 11.1d 100.0% | 98.0% 1.9d | 1.0d 2026-04-20 00:12:11 8.4 Kbit/s
dizum (NL) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Exit 8.5 Mbit/s | 816.0 Kbit/s 8.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.9d | 8d 1.9d | 40.3d 1.9d | 11.1d 100.0% | 98.0% 1.9d | 1.0d 2026-04-20 00:12:11 8.4 Kbit/s
faravahar (US) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Exit 8.5 Mbit/s | 816.0 Kbit/s 8.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.9d | 8d 1.9d | 61.2d 1.9d | 11.1d 100.0% | 98.0% 1.9d | 1.0d 2026-04-20 00:12:11 8.4 Kbit/s
gabelmoo (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 8.5 Mbit/s | 816.0 Kbit/s 8.5 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.9d | 8d 1.9d | 63.0d 1.9d | 11.1d 100.0% | 98.0% 1.9d | 1.0d 2026-04-20 00:12:11 8 bit/s
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 8.5 Mbit/s | 816.0 Kbit/s 8.5 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.9d | 8d 1.9d | 62.3d 1.9d | 11.1d 100.0% | 98.0% 1.9d | 1.0d 2026-04-20 00:12:11 8.4 Kbit/s
maatuska (SE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 8.5 Mbit/s | 816.0 Kbit/s 8.5 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.9d | 8d 0.9d | 61.4d 1.9d | 10.2d 100.0% | 98.0% 0.9d | 1.0d 2026-04-19 06:12:08 8 bit/s
moria1 (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 8.5 Mbit/s | 8.4 Mbit/s 8.5 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.6d | 8d 1.8d | 303.7d 1.9d | 11.0d 100.0% | 98.0% 1.6d | 9.9d 2026-04-20 00:12:11 8 bit/s
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 8.5 Mbit/s | 816.0 Kbit/s 8.5 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.9d | 8d 1.9d | 63.2d 1.9d | 11.1d 100.0% | 98.0% 1.9d | 1.0d 2026-04-20 00:12:11 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.