View Relay "Raspi53Tor"

Fingerprint: 3BD1376CD339EDAC6AEFCF355A703A16AF913496 | Family: 1 relay | raspitor@habmalnefrage.de | AS3320 | Germany | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, Fast, Stable (4)
BW Verified
6/6 BW Auths Measured 8 Kbit/s Median
Stability
Not Overloaded | UP 2d 21h 53m ago | UP 59% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
7y 1mo 1w ago
BW Weight
0.00% of Network | 10 Mbit/s Observed By Relay
Version
0.4.9.6 Recommended
Issues Detected:
  • Guard: bandwidth below threshold : Observed bandwidth 1.3 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: WFU below threshold : Weighted Fractional Uptime 80.9% is below 98% requirement
    Suggestion: WFU measures recent uptime (recent downtime weighs more heavily). To improve: 1) Minimize restarts, 2) Use systemd with Restart=always, 3) Monitor for OOM kills, 4) Schedule updates during low-traffic periods.
  • 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
  • HSDir: WFU below threshold : WFU 80.9% below 98% required for HSDir
    Suggestion: HSDir requires ≥98% WFU, Stable flag, and Time Known ≥25 hours (or ~10 days for moria1). Improve uptime consistency.
  • 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
p57a9dc7c.dip0.t-ipconnect.de
87.169.220.124:1058
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS3320
AS Name
Deutsche Telekom AG (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.22% consensus weight, 56 operators)

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: 8/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) 10.4 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 (1/9 DA) Median: 5.2d (1/9 DA above threshold)
Min/Max: 4.7d / 11338.7d (9/9 DA, Voting / Total Eligible)		 ≥17.9d - 58.6d (varies) (≥5/9 DA)
Uptime Below (0/9 DA) 2.9d (R) ≥3.3d - 3.4d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/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 Meets (8/9 DA) 8/9 DA assigned Stable ≥17.9d - 58.6d (varies) (≥5/9 DA)
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 81.3% (0/9 DA above threshold)
Min/Max: 79.5% / 85.5% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 13.8d (9/9 DA above threshold)
Min/Max: 10.0d / 15.5d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Meets (9/9 DA) 9/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 Meets (8/9 DA) 8/9 DA assigned Stable ≥17.9d - 58.6d (varies) (≥5/9 DA)
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 81.3% (0/9 DA above threshold)
Min/Max: 79.5% / 85.5% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 13.8d (9/9 DA above threshold)
Min/Max: 10.0d / 15.5d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 10.4 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-296.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-03-29 09:45:08).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
10.39 Mbit/s
Advertised Bandwidth
10.39 Mbit/s
Rate Limit
10.49 Mbit/s
Burst Limit
15.73 Mbit/s
Total Data
54 TB (5 years)
1mo: 578 GB | 6mo: 6.9 TB | 1y: 15 TB | 5y: 54 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-29 09:45:08

Measured By
6/6 Bandwidth Authorities
Median Measurement
8.0 Kbit/s
Min / Max
3360 bit/s / 10.4 Kbit/s
Deviation
7024 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0004% of network (14th pctl) | Guard: N/A | Middle: 0.0012% (26th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 2d 21h 53m ago
Overall Uptime (1M/6M/1Y/5Y)
59.9%/91.0%/95.2%/88.9%
Flag Uptime (1M/6M/1Y/5Y)
59.4%/—/—/87.4%
Hibernating
No
Timestamps
First Seen
7y 1mo 1w ago (2019-02-18 00:00:00)
Last Seen
2h 46m 39s ago (2026-03-29 08:00:00)
Last Restarted
2d 21h 53m ago (2026-03-26 12:52:59)
Last Changed Address
2026-03-11 15:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-03-29 02:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
raspitor@habmalnefrage.de
Family Configuration
Family Support
MyFamily Only (1) — Legacy only. Consider migrating to Happy Families.
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
3BD1376CD339EDAC6AEFCF355A703A16AF913496 (this relay)
Alleged Members: 2
(they don't list you back) 
41CB74AD13AA9CE0F05682536CD9287409CC78DD
EB1CB0138DF8D78A1B9C63148F232B88802BA486
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
Not an exit relay — DNS health testing does not apply.
IPv4 Exit Policy Summary
reject: 
  1-65535
IPv6 Exit Policy Summary
None
Full Exit Policy
reject *:*

Last fetch was at Sun, 29 Mar 2026 10:46:38 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-03-29 09:45: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) Yes Yes No — Y Yes Running, Valid, Fast, Stable 10.4 Mbit/s | 816.0 Kbit/s 10.4 Mbit/s | 200.0 Mbit/s OR 16.0 Mbit/s 80.9% | 98% 14.2d | 8d 5.2d | 63.4d 2.9d | 3.3d 80.9% | 98.0% 14.2d | 1.0d 2026-03-28 19:14:14 8.0 Kbit/s
dannenberg (DE) Yes Yes No — N Yes Running, Valid, Fast, Stable 10.4 Mbit/s | 816.0 Kbit/s 10.4 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 83.0% | 98% 15.5d | 8d 8.8d | 17.9d 2.9d | 3.3d 83.0% | 98.0% 15.5d | 1.0d 2026-03-28 19:14:14 10.4 Kbit/s
dizum (NL) Yes Yes No — N Yes Running, Valid, Fast 10.4 Mbit/s | 816.0 Kbit/s 10.4 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 79.5% | 98% 13.2d | 8d 4.7d | 42.9d 2.9d | 3.4d 79.5% | 98.0% 13.2d | 1.0d 2026-03-28 19:14:14 10.4 Kbit/s
faravahar (US) Yes Yes No — N Yes Running, Valid, Fast, Stable 10.4 Mbit/s | 816.0 Kbit/s 10.4 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 81.4% | 98% 13.8d | 8d 5.1d | 56.4d 2.9d | 3.4d 81.4% | 98.0% 13.8d | 1.0d 2026-03-28 19:14:14 10.4 Kbit/s
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid, Fast, Stable 10.4 Mbit/s | 816.0 Kbit/s 10.4 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 80.9% | 98% 14.2d | 8d 5.2d | 62.1d 2.9d | 3.4d 80.9% | 98.0% 14.2d | 1.0d 2026-03-28 19:14:14 3360 bit/s
longclaw (US) Yes Yes No — Y Yes Running, Valid, Fast, Stable 10.4 Mbit/s | 816.0 Kbit/s 10.4 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 82.9% | 98% 13.5d | 8d 5.2d | 62.6d 2.9d | 3.3d 82.9% | 98.0% 13.5d | 1.0d 2026-03-28 19:14:14 5680 bit/s
maatuska (SE) Yes Yes No — Y Yes Running, Valid, Fast, Stable 10.4 Mbit/s | 816.0 Kbit/s 10.4 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 81.2% | 98% 14.3d | 8d 5.2d | 50.7d 2.9d | 3.3d 81.2% | 98.0% 14.3d | 1.0d 2026-03-28 19:14:14 5600 bit/s
moria1 (US) Yes Yes No — Y Yes Running, Valid, Fast, Stable 10.4 Mbit/s | 8.4 Mbit/s 10.4 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 85.5% | 98% 10.0d | 8d 11338.7d | 291.4d 2.9d | 4.1d 85.5% | 98.0% 10.0d | 9.9d 2026-03-28 19:14:14 8.8 Kbit/s
tor26 (AT) Yes Yes No — Y Yes Running, Valid, Fast, Stable 10.4 Mbit/s | 816.0 Kbit/s 10.4 Mbit/s | 264.0 Mbit/s OR 16.0 Mbit/s 81.3% | 98% 13.8d | 8d 5.2d | 58.6d 2.9d | 3.9d 81.3% | 98.0% 13.8d | 1.0d 2026-03-28 19:14:14 3440 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.