View Relay "simp13s3c"

Fingerprint: A8F7230F6F5B640F3A01B5FAAFC8AF9481873DEE | Family: 1 relay | AS28753 | Germany | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Exit (4)
DNS Health
Healthy (12.1s, 13th percentile) (via exitdnshealth.1aeo.com)
BW Verified
5/7 BW Auths Measured 8 bit/s Median
Stability
Not Overloaded | UP 1d 3m 10s ago
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
23h 46m 38s ago
BW Weight
0.00% of Network | 0 Kbit/s Observed By Relay
Version
0.4.9.11 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 1.0 days is below 8 days requirement (7.0 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 23.1 hours below 25 hours (dir-spec default)
    Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.
  • 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
212.95.50.243:9001
Exit Address
212.95.50.243
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS28753
AS Name
Leaseweb Deutschland GmbH (BGP.tools)
AS Rarity
Epic (score: 3/5, 0.26% consensus weight, 9 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: 1.0d (0/9 DA above threshold)
Min/Max: 0.3d / 1.0d (9/9 DA, Voting / Total Eligible)		 ≥22.1d - 59.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥646.2d
Uptime Below (0/9 DA) 1.0d (R) ≥3.8d - 3.8d (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 ≥22.1d - 59.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥646.2d
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 Below (0/9 DA) Median: 1.0d (0/9 DA above threshold)
Min/Max: 0.3d / 1.0d (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 ≥22.1d - 59.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥646.2d
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 7.0 more days) Median: 1.0d (0/9 DA above threshold)
Min/Max: 0.3d / 1.0d (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-320.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-06-30 14:45:07).

Bandwidth Metrics

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

Source: CollecTor — fetched 2026-06-30 14:45:07

Measured By
5/7 Bandwidth Authorities
Not measured by: bastet, dannenberg
Median Measurement
8 bit/s
Min / Max
0 bit/s / 8 bit/s
Deviation
8 bit/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 3m 10s 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
23h 46m 38s ago (2026-06-29 15:00:00)
Last Seen
2h 46m 38s ago (2026-06-30 12:00:00)
Last Restarted
1d 3m 10s ago (2026-06-29 14:43:28)
Last Changed Address
2026-06-29 15:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-06-30 07:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
none
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
A8F7230F6F5B640F3A01B5FAAFC8AF9481873DEE (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

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

Exit Health & Policy

DNS Health
Status
Healthy (avg. 12.1s, 13th percentile)
Query Domain
18a85f7b628d4cccac60199aa796e3bb.a8f7230f.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
4/4 instances succeeded
First Hop
Zilith (FR) B4ECCA36F61E502B2BE7F08EB089DCE22353EBBE
Exit Address Used
212.95.50.243
Per-Instance Results
Cross Validation Attempt 1: Success, 12.9s (cv1_w3)
Cross Validation Attempt 2: Success, 13.1s (cv2_w3)
Cross Validation Attempt 3: Success, 10.7s (cv3_w3)
Cross Validation Attempt 4: Success, 11.6s (cv4_w3)
Tested: 2026-06-30 07:16:52 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 
  20-23
  43
  53
  79-81
  88
  110
  143
  194
  220
  389
  443
  464
  531
  543-544
  554
  563
  636
  853
  873
  902-904
  981
  989-995
  1194
  1723
  1755
  2082-2083
  2086-2087
  2095-2096
  5222-5223
  5228
  5900
  6660-6669
  6679
  6697
  8000
  8008
  8080
  8082
  8087-8088
  8443
  8888
  10000
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 212.95.50.243:*
accept *:20-21
accept *:22
accept *:23
accept *:43
accept *:53
accept *:79
accept *:80-81
accept *:88
accept *:110
accept *:143
accept *:194
accept *:220
accept *:389
accept *:443
accept *:464
accept *:531
accept *:543-544
accept *:554
accept *:563
accept *:636
accept *:853
accept *:873
accept *:902-904
accept *:981
accept *:989-990
accept *:991
accept *:992
accept *:993
accept *:994
accept *:995
accept *:1194
accept *:1723
accept *:1755
accept *:2082
accept *:2083
accept *:2086-2087
accept *:2095-2096
accept *:5222-5223
accept *:5228
accept *:5900
accept *:6660-6669
accept *:6679
accept *:6697
accept *:8000
accept *:8008
accept *:8080
accept *:8082
accept *:8087-8088
accept *:8443
accept *:8888
accept *:10000
reject *:*

Last fetch was at Tue, 30 Jun 2026 14:46:38 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-06-30 14: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 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.0d | 8d 1.0d | 59.0d 1.0d | 3.8d 100.0% | 98.0% 0.96d | 1.04d 2026-06-30 09:11:31 —
dannenberg (DE) Yes Yes Yes — Y 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% 1.0d | 8d 1.0d | 22.1d 1.0d | 3.8d 100.0% | 98.0% 0.96d | 1.04d 2026-06-30 09:11:31 —
dizum (NL) Yes Yes Yes — N 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% 1.0d | 8d 1.0d | 49.2d 1.0d | 3.8d 100.0% | 98.0% 0.96d | 1.04d 2026-06-30 09:11:31 —
faravahar (US) Yes Yes Yes — N 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% 1.0d | 8d 1.0d | 59.9d 1.0d | 3.9d 100.0% | 98.0% 0.96d | 1.04d 2026-06-30 09:11:31 —
gabelmoo (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 312.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.3d | 8d 0.3d | 60.1d 1.0d | 4.3d 100.0% | 98.0% 0.3d | 1.0d 2026-06-29 14:43:30 8 bit/s
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 248.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.0d | 8d 1.0d | 60.0d 1.0d | 3.8d 100.0% | 98.0% 0.96d | 1.04d 2026-06-30 09:11:31 8 bit/s
maatuska (SE) Yes Yes Yes — Y 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% 1.0d | 8d 1.0d | 44.0d 1.0d | 3.8d 100.0% | 98.0% 0.96d | 1.04d 2026-06-30 09:11:31 8 bit/s
moria1 (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 0 bit/s | 8.4 Mbit/s 0 bit/s | 256.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.9d | 8d 1.0d | 646.2d 1.0d | 3.9d 100.0% | 98.0% 0.9d | 9.8d 2026-06-30 09:11:31 8 bit/s
tor26 (AT) Yes Yes Yes — Y 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% 1.0d | 8d 1.0d | 60.4d 1.0d | 4.0d 100.0% | 98.0% 0.96d | 1.04d 2026-06-30 09:11:31 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.