View Relay "simp13s3c"

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

Consensus
In Consensus (9/9 Directory Auths)
DNS Health
Healthy (19.0s, 93rd percentile) (via exitdnshealth.1aeo.com)
BW Verified
6/7 BW Auths Measured 104 Mbit/s Median
Stability
Not Overloaded | UP 1w 2d 3h ago | UP 99% (1M)
Reachability
IPv4: 9/9 | v6: None configured(Directory Auths)
BW Weight
0.01% of Network | 113 Mbit/s Observed By Relay
Version
0.4.9.14 Not Recommended
Issues Detected:
  • 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.
  • Tor version not recommended : Running Tor version 0.4.9.14 which is not on the recommended list.
    Suggestion: Update to the latest stable Tor version. Outdated versions may have security vulnerabilities and could eventually be rejected by the network. See torproject.org/download for latest releases.
Notes:
  • Guard: WFU near threshold: Weighted Fractional Uptime is just above the Guard bar at maatuska (98.4%, need ≥98%) and moria1 (98.2%, need ≥98%). Recent downtime weighs more than older downtime. Avoid restarts while it is this close; a short outage can drop the Guard flag.
    Suggestion: Recent downtime weighs more than older downtime. Minimize restarts, use systemd Restart=always, and watch for OOM kills until each authority has more room above its own guard-wfu.
  • Guard: Time Known near threshold: Time Known is just under the Guard bar at E30CF7B3 (5.3 days, need ≥5 days 10 hours 41 minutes 56 seconds). This is weighted time, so the day count is shorter than calendar uptime, and it falls while the relay is unreachable. Stay reachable so it can move clear of the bar.
    Suggestion: Weighted time-known falls while the relay is unreachable and resets if the identity key changes. Authorities cap it at 8 days (AuthDirVoteGuardGuaranteeTimeKnown), about a few weeks of continuous uptime. Stay up with the same key.

Addresses
OR Address
212.95.50.243:9001
Exit Address
212.95.50.243
Reachability (Directory Authorities)
IPv4
9/9
IPv6
None configured
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, 6 operators)

Current Flags (8): Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit
Eligible Flags (8): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 6/9 | HSDir: 6/9 | Guard: 6/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) 80.0 Mbit/s – 192.0 Mbit/s (6 DA measured)
80.0 Mbit/s (3 DA relay-reported)
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (4/9 DA) Median: 6.0d (2/9 DA above threshold)
Min/Max: 2.4d / 15271.5d (9/9 DA, Voting / Total Eligible)
≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12669.7d
Uptime Meets (9/9 DA) 9.2d (R) ≥5.0d - 5.1d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
80.0 Mbit/s – 192.0 Mbit/s (6 DA measured)
80.0 Mbit/s (3 DA relay-reported)
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Meets (6/9 DA) 6/9 DA assigned Stable ≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12669.7d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Uptime Meets (9/9 DA) 9.2d (R) ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA)
[Stricter] moria1: ≥98% WFU and ≥9.7d Time Known
Guard Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
80.0 Mbit/s – 192.0 Mbit/s (6 DA measured)
80.0 Mbit/s (3 DA relay-reported)
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Meets (6/9 DA) 6/9 DA assigned Stable ≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12669.7d
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) Median: 99.3% (9/9 DA above threshold)
Min/Max: 98.2% / 99.8% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Partial (8/9 DA) Median: 18.6d (8/9 DA above threshold)
Min/Max: 5.3d / 43.8d (9/9 DA, Voting / Total Eligible)
≥8 days; E30CF7B3: ≥5 days 10 hours 41 minutes 56 seconds (≥5/9 DA)
Bandwidth Meets (9/9 DA) 80.0 Mbit/s – 192.0 Mbit/s (6 DA measured)
80.0 Mbit/s (3 DA relay-reported)
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-248.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-11-20 08:45:05).

Capacity (Relay Reported)
Observed Bandwidth
113.98 Mbit/s
Advertised Bandwidth
83.89 Mbit/s
Rate Limit
83.89 Mbit/s
Burst Limit
109.05 Mbit/s
Total Data
215 TB (6 months)
1mo: 38 TB | 6mo: 215 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-20 08:45:05

Measured By
6/7 Bandwidth Authorities
Not measured by: faravahar
Consensus Weight
104.0 Mbit/s (median of 6 measurements)
Measured Min / Max
80.0 Mbit/s / 192.0 Mbit/s
Deviation
112.0 Mbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0071% of network (56th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0219% (44th pctl)
History
Throughput and write/read, last 6 months Throughput and write/read, last 30 days
1M 6M

Uptime Metrics
Current Status
UP 1w 2d 3h ago
Overall Uptime (1M/6M/1Y/5Y)
99.3%/99.7%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (99.3%/99.7%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
4mo 3w 2d ago (2026-06-29 15:00:00)
Last Seen
1h 45m 32s ago (2026-11-20 08:00:00)
Last Restarted
1w 2d 3h ago (2026-11-11 05:56:05)
Last Changed Address
2026-06-29 15:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Evaluated 2026-11-20 09:45 UTC. /details snapshot 2026-11-20 08:00:00 UTC (cached 37s ago). /bandwidth snapshot 2026-11-20 02:00:00 UTC (cached 6h 30m ago).

General Overload (from /details)
Status
No general overload report in available data
File Descriptor Exhaustion (from /bandwidth)
Status
No file-descriptor exhaustion report in available data
Rate Limits (from /bandwidth)
Status
No rate-limit report in available data
Rate Limit
—
Burst Limit
—
Write counter
—
Read counter
—
About these reports and MetricsPort

Allium’s eligibility windows are applied to the reported timestamps: 72 hours for general overload and file-descriptor exhaustion, 24 hours for a rate-limit hit. A report at the cutoff is historical. An older report can remain visible after Onionoo or Allium’s cache still has it. The cutoff does not prove the relay recovered at that moment. Allium caches the bandwidth document for 12 hours by default. The snapshot time is when Onionoo published that document. It is not the relay’s event time, and it is not necessarily the extra-info publication time. Cache age is how old Allium’s copy is.

MetricsPort counters are cumulative. Compare samples, and account for process restarts. A nonzero total alone does not show ongoing activity. Gauges describe current values. An unavailable metric is unknown, not zero. Allium does not have this relay’s MetricsPort readings and does not invent them.

The port below is an example for an endpoint you have already configured. MetricsPort must be enabled with restricted access and must not be exposed publicly. Setup stays in the Tor overload troubleshooting guide.

curl http://127.0.0.1:9035/metrics
History
Uptime, last 6 months Uptime, last 30 days
1M 6M

Operator Identity

Source: AROI Validation API — 2026-11-19 23: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

Platform
Linux — Tor 0.4.9.14 on Linux
Version
0.4.9.14 — Not Recommended
Version Status
Obsolete — Update urgently. See torproject.org/download

DNS Health
Status
Healthy (avg. 19.0s, 93rd percentile)
Query Domain
7e2be20aa8314763bf5d6ee3371d4c6f.a8f7230f.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Upstream Resolver
Local /24 (exit's own network)
Local /24 100% (~58 estimated queries)
Cross-Validation
4/4 instances succeeded
First Hop
0xdeadbeef (DE) BD57D2802AB2331CC0527BE8ABF2FFC4621CA1FB
Exit Address Used
212.95.50.243
Per-Instance Results
Cross Validation Attempt 1: Success, 23.0s (cv1_w3)
Cross Validation Attempt 2: Success, 19.7s (cv2_w3)
Cross Validation Attempt 3: Success, 13.9s (cv3_w3)
Cross Validation Attempt 4: Success, 19.5s (cv4_w3)
Tested: 2026-11-19 20:13:19 UTC
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 Fri, 20 Nov 2026 09:45:32 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-11-20 08:45:05).

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 (BW|T) Guard BW (BW|Threshold) Guard WFU (M|T) Guard TK (M|T) Stable MTBF (M|T) Stable Uptime (Relay|T) Desc Published Cons Wt (Authority)
E30CF7B3 Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 104.0 Mbit/s (M) | 816.0 Kbit/s 104.0 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s 99.0% | 98% 5.3d | 5d 2.4d | 3.9d 9.2d | 5.1d 2026-11-19 15:57:12 104.0 Mbit/s (M)
dannenberg (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 192.0 Mbit/s (M) | 816.0 Kbit/s 192.0 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 99.4% | 98% 18.6d | 8d 6.0d | 8.2d 9.2d | 5.1d 2026-11-19 15:57:12 192.0 Mbit/s (M)
dizum (NL) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.3% | 98% 20.4d | 8d 8.1d | 6.8d 9.2d | 5.1d 2026-11-19 15:57:12 80.0 Mbit/s (R)
faravahar (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.3% | 98% 16.0d | 8d 4.9d | 7.0d 9.2d | 5.1d 2026-11-19 15:57:12 80.0 Mbit/s (R)
gabelmoo (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 120.0 Mbit/s (M) | 816.0 Kbit/s 120.0 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 99.5% | 98% 18.7d | 8d 6.9d | 8.3d 9.2d | 5.1d 2026-11-19 15:57:12 120.0 Mbit/s (M)
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 80.0 Mbit/s (M) | 816.0 Kbit/s 80.0 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 99.4% | 98% 18.6d | 8d 5.0d | 9.1d 9.2d | 5.1d 2026-11-19 15:57:12 80.0 Mbit/s (M)
maatuska (SE) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 98.4% | 98% 14.7d | 8d 3.6d | 2.3d 9.2d | 5.1d 2026-11-19 15:57:12 80.0 Mbit/s (R)
moria1 (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 88.0 Mbit/s (M) | 8.4 Mbit/s 88.0 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s 98.2% | 98% 9.8d | 8d 15271.5d | 12669.7d 9.2d | 5.0d 2026-11-19 15:57:12 88.0 Mbit/s (M)
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 104.0 Mbit/s (M) | 816.0 Kbit/s 104.0 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 99.8% | 98% 43.8d | 8d 16.4d | 8.2d 9.2d | 5.1d 2026-11-19 15:57:12 104.0 Mbit/s (M)

N/T = this authority does not test IPv6 • — = not in this vote • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known • Bandwidth source: (M) bandwidth-scanner measurement, (R) relay-reported, (U) unmeasured, counted as 0

Bandwidth Values Explained:
Measured (M) = An authority's bandwidth-scanner measurement of your relay (Measured= in its vote). An authority that has one uses it for the Fast and Guard flags, and the consensus weight is the median of these measurements when 3 or more authorities have one.
Relay-reported (R) = The bandwidth your relay advertises: the lower of its observed bandwidth and its rate limit, capped at 10 MB/s (Bandwidth= in every vote). An authority without a measurement uses it for flags, unless it has measurements for enough other relays (ignoring-advertised-bws=1); then your relay counts as 0 (U). It sets the consensus weight only when fewer than 3 authorities measured the relay, capped at 20 KB/s (maxunmeasuredbw) while 3 or more authorities publish measurements.
Not published = The authority has no measurement of your relay in its vote and ignores relay-reported bandwidth, yet it voted Fast or its vote has no measurements at all: it judges your relay by a measurement kept from an earlier bandwidth file (0 if none), which its vote doesn't show.
Why different? A low measurement means the bandwidth scanners see your relay underperforming compared with other relays that report a similar speed. Votes list both values in kilobytes per second. Rules: Assigning flags in a vote, Computing a consensus.
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.