View Relay "rinderwahnRelayEE"

Fingerprint: 0F3282AAB40DA937151A5E9F02327485EAE5AEC0 | Family: 2 relays | torrelaysaregreat@gmail.com... | AS202759 | Estonia | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, Fast, Stable (4)
BW Verified
5/7 BW Auths Measured 22 Mbit/s Median
Stability
Not Overloaded | UP 1d 15h 19m ago | UP 100% (1M)
Reachability
IPv4: 9/9 | v6: None configured(Directory Auths)
First Seen
1y 4w 1d ago
BW Weight
0.00% of Network | 79 Mbit/s Observed By Relay
Version
0.4.9.15 Recommended
Issues Detected:
  • HSDir: requires V2Dir (tunnelled-dir-server) : HSDir requires the relay to support tunnelled directory requests (V2Dir flag). This relay is missing V2Dir — the descriptor likely does not include tunnelled-dir-server, usually because DirCache 0 is set in torrc.
    Suggestion: Remove DirCache 0 from torrc (DirCache is enabled by default in Tor ≥0.3.3). Restart Tor and verify the descriptor includes tunnelled-dir-server. You can check with: grep tunnelled-dir-server /var/lib/tor/cached-descriptors

Connectivity and Location

Addresses
OR Address
5.253.176.99:443
Reachability (Directory Authorities)
IPv4
9/9
IPv6
None configured
Location
Country
Estonia Estonia
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS202759
AS Name
RJ Network OU (BGP.tools)
AS Rarity
Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

Flags and Eligibility

Current Flags (4): Running, Valid, Fast, Stable
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 9/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 0/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 Below (0/9 DA) No DirPort, no tunnelled-dir-server (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 19.2 Mbit/s – 25.6 Mbit/s (5 DA measured)
16.8 Mbit/s (4 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 Partial (8/9 DA) Median: 50.2d (8/9 DA above threshold)
Min/Max: 7.1d / 96.3d (9/9 DA, Voting / Total Eligible)		 ≥2.4d - 9.5d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7621.1d
Uptime Below (0/9 DA) 1.6d (R) ≥5.2d - 5.5d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
19.2 Mbit/s – 25.6 Mbit/s (5 DA measured)
16.8 Mbit/s (4 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 (9/9 DA) 9/9 DA assigned Stable ≥2.4d - 9.5d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7621.1d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Uptime Below (0/9 DA) 1.6d (R) ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA)
[Stricter] moria1: ≥98% WFU and ≥9.9d Time Known
Guard Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
19.2 Mbit/s – 25.6 Mbit/s (5 DA measured)
16.8 Mbit/s (4 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 (9/9 DA) 9/9 DA assigned Stable ≥2.4d - 9.5d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7621.1d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (9/9 DA) Median: 100.0% (9/9 DA above threshold)
Min/Max: 99.2% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98%; dizum: ≥97.87300000000001% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 40.4d (9/9 DA above threshold)
Min/Max: 9.8d / 75.5d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 19.2 Mbit/s – 25.6 Mbit/s (5 DA measured)
16.8 Mbit/s (4 DA relay-reported)		 ≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-272.0 Mbit/s) (≥5/9 DA)
Exit Exit Policy Below (0/9 DA) Port 80: No | Port 443: No (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-04 18:45:05).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
79.75 Mbit/s
Advertised Bandwidth
16.78 Mbit/s
Rate Limit
16.78 Mbit/s
Burst Limit
8.59 Gbit/s
Total Data
79 TB (5 years)
1mo: 13 TB | 6mo: 50 TB | 1y: 73 TB | 5y: 79 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-04 18:45:05

Measured By
5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Consensus Weight
22.4 Mbit/s (median of 5 measurements)
Measured Min / Max
19.2 Mbit/s / 25.6 Mbit/s
Network Participation: Consensus Weight: 0.0014% of network (24th pctl) | Guard: N/A | Middle: 0.0042% (50th pctl) | Exit: N/A
History
Throughput and write/read, last 6 months Throughput and write/read, last year Throughput and write/read, last 5 years Throughput and write/read, last 30 days
1M 6M 1Y 5Y

Uptime and Stability

Uptime Metrics
Current Status
UP 1d 15h 19m ago
Overall Uptime (1M/6M/1Y/5Y)
100.0%/99.3%/99.4%/99.4%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (100.0%/99.3%/99.4%/99.4%)
Hibernating
No
Timestamps
First Seen
1y 4w 1d ago (2025-10-06 15:00:00)
Last Seen
1h 45m 16s ago (2026-11-04 17:00:00)
Last Restarted
1d 15h 19m ago (2026-11-03 03:25:59)
Last Changed Address
2026-04-06 23:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Evaluated 2026-11-04 18:45 UTC. /details snapshot 2026-11-04 17:00:00 UTC (cached 21s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 11h 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 year Uptime, last 5 years Uptime, last 30 days
1M 6M 1Y 5Y

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-11-04 10:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
torrelaysaregreat@gmail.com xmr:84czj1u2Q4dJ7bzf41TyDFS1i1GPKX5DQGgqZFg85LFge7LLUpCvEMyfjDfAnsZv291gtyMqUsTmxZojB7cRVckyUuih9ar
Family Configuration
Family Support
MyFamily Only (2) — Legacy only. Consider migrating to Happy Families. | View Full Family (2)
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Members: 2 
0AB9590938A6296412D08E824F04317D388F7A18
0F3282AAB40DA937151A5E9F02327485EAE5AEC0 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

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

Exit Health & Policy

DNS Health
Not an exit relay — DNS health testing does not apply.
IPv4 Exit Policy Summary
accept: 
  43
  79
  873
  1194
  1293
  1723
  8332-8333
  11371
  18080-18083
  18088-18089
  28080-28083
  28088-28089
  34567-34568
  38080-38083
  38088-38089
  64738
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 5.253.176.99:*
accept *:43
accept *:79
accept *:873
accept *:1194
accept *:1293
accept *:1723
accept *:8332-8333
accept *:11371
accept *:18080
accept *:18081
accept *:18082
accept *:18083
accept *:18088
accept *:18089
accept *:28080
accept *:28081
accept *:28082
accept *:28083
accept *:28088
accept *:28089
accept *:34567
accept *:34568
accept *:38080
accept *:38081
accept *:38082
accept *:38083
accept *:38088
accept *:38089
accept *:64738
reject *:*

Last fetch was at Wed, 04 Nov 2026 18:45:16 GMT.

Consensus Evaluation

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

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 (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)
bastet (US) Yes Yes No — Y Yes Running, Valid, Fast, Stable 21.6 Mbit/s (M) | 816.0 Kbit/s 21.6 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 99.9% | 98% 26.5d | 8d 17.3d | 8.4d 1.6d | 5.2d 2026-11-03 21:26:04 21.6 Mbit/s (M)
dannenberg (DE) Yes Yes No — Y Yes Running, Valid, Fast, Stable 25.6 Mbit/s (M) | 816.0 Kbit/s 25.6 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 64.0d | 8d 63.9d | 9.5d 1.6d | 5.5d 2026-11-04 15:26:07 25.6 Mbit/s (M)
dizum (NL) Yes Yes No — N Yes Running, Valid, Fast, Stable 16.8 Mbit/s (R) | 816.0 Kbit/s 16.8 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.2% | 98% 31.7d | 8d 21.4d | 6.8d 1.6d | 5.5d 2026-11-04 15:26:07 16.8 Mbit/s (R)
faravahar (US) Yes Yes No — Y Yes Running, Valid, Fast, Stable 16.8 Mbit/s (R) | 816.0 Kbit/s 16.8 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 40.4d | 8d 25.2d | 6.6d 1.6d | 5.5d 2026-11-04 15:26:07 16.8 Mbit/s (R)
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid, Fast, Stable 22.4 Mbit/s (M) | 816.0 Kbit/s 22.4 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 50.5d | 8d 50.2d | 10.9d 1.6d | 5.5d 2026-11-04 15:26:07 22.4 Mbit/s (M)
longclaw (US) Yes Yes No — Y Yes Running, Valid, Fast, Stable 16.8 Mbit/s (R) | 816.0 Kbit/s 16.8 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 75.5d | 8d 75.4d | 11.1d 1.6d | 5.5d 2026-11-04 15:26:07 16.8 Mbit/s (R)
maatuska (SE) Yes Yes No — N Yes Running, Valid, Fast, Stable 16.8 Mbit/s (R) | 816.0 Kbit/s 16.8 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.6% | 98% 30.4d | 8d 7.1d | 2.4d 1.6d | 5.5d 2026-11-04 15:26:07 16.8 Mbit/s (R)
moria1 (US) Yes Yes No — Y Yes Running, Valid, Fast, Stable 19.2 Mbit/s (M) | 8.4 Mbit/s 19.2 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 9.8d | 8d 96.3d | 7621.1d 1.6d | 5.5d 2026-11-04 15:26:07 19.2 Mbit/s (M)
tor26 (AT) Yes Yes No — Y Yes Running, Valid, Fast, Stable 23.2 Mbit/s (M) | 816.0 Kbit/s 23.2 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 75.5d | 8d 75.4d | 10.8d 1.6d | 5.5d 2026-11-04 15:26:07 23.2 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.