View Relay "simpletorrelay"

Fingerprint: B679C6B8846FEE5369CDC19A0D2D036F4100F5FA | Family: 1 relay | Random Person <fin1010@arcor.de> | AS6805 | Germany | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid (2)
BW Verified
5/6 BW Auths Measured 88 bit/s Median
Stability
Not Overloaded | UP 18h 52m 21s ago | UP 44% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
7y 3w 6d ago
BW Weight
0.00% of Network | 1 Mbit/s Observed By Relay
Version
0.4.9.5 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 0.2 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 49.4% 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.
  • 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: 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 49.4% 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
dynamic-002-243-142-169.2.243.pool.telefonica.de
2.243.142.169:9001
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS6805
AS Name
Telefonica Germany GmbH & Co.OHG (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 7 operators)

Flags and Eligibility

Current Flags (2): Running, Valid
Eligible Flags (3): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 4/9 | Stable: 1/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) 1.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 (1/9 DA) Median: 0.8d (1/9 DA above threshold)
Min/Max: 0.8d / 17738.0d (9/9 DA, Voting / Total Eligible)		 ≥11.3d - 53.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥366.0d
Uptime Below (0/9 DA) 0.8d (R) ≥9.7d - 12.6d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (4/9 DA) 4/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 (1/9 DA) 1/9 DA assigned Stable ≥11.3d - 53.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥366.0d
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: 48.9% (0/9 DA above threshold)
Min/Max: 48.4% / 58.1% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 11.9d (9/9 DA above threshold)
Min/Max: 10.0d / 12.4d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Below (4/9 DA) 4/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 (1/9 DA) 1/9 DA assigned Stable ≥11.3d - 53.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥366.0d
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: 48.9% (0/9 DA above threshold)
Min/Max: 48.4% / 58.1% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 11.9d (9/9 DA above threshold)
Min/Max: 10.0d / 12.4d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 1.5 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-15 19:15:08).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
1.50 Mbit/s
Advertised Bandwidth
819.20 Kbit/s
Rate Limit
819.20 Kbit/s
Burst Limit
1.64 Mbit/s
Total Data
1.2 TB (5 years)
1mo: 14 GB | 6mo: 41 GB | 1y: 418 GB | 5y: 1.2 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-15 19:15:08

Measured By
5/6 Bandwidth Authorities
Not measured by: longclaw
Median Measurement
88 bit/s
Min / Max
24 bit/s / 816 bit/s
Deviation
792 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (1th pctl) | Guard: N/A | Middle: 0.0000% (1th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 18h 52m 21s ago
Overall Uptime (1M/6M/1Y/5Y)
44.5%/45.5%/47.0%/59.2%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (44.5%/45.5%/47.0%/59.2%)
Hibernating
No
Timestamps
First Seen
7y 3w 6d ago (2019-02-18 00:00:00)
Last Seen
1h 15m 39s ago (2026-03-15 18:00:00)
Last Restarted
18h 52m 21s ago (2026-03-15 00:23:18)
Last Changed Address
2026-03-15 01:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-03-15 12:00 UTC

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

Software and Version

Platform
Linux — Tor 0.4.9.5 on Linux
Version
0.4.9.5 — 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, 15 Mar 2026 19:15:38 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-03-15 19: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) Yes Yes No — Y Yes Running, Valid 1.5 Mbit/s | 816.0 Kbit/s 1.5 Mbit/s | 208.0 Mbit/s OR 16.0 Mbit/s 49.4% | 98% 12.1d | 8d 0.8d | 56.9d 0.8d | 11.9d 49.4% | 98.0% 12.1d | 1.0d 2026-03-15 00:26:19 88 bit/s
dannenberg (DE) Yes Yes No — N Yes Running, Valid, Fast 1.5 Mbit/s | 816.0 Kbit/s 1.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 49.2% | 98% 11.9d | 8d 0.8d | 11.3d 0.8d | 12.6d 49.2% | 98.0% 11.9d | 1.0d 2026-03-15 00:26:19 816 bit/s
dizum (NL) Yes Yes No — N Yes Running, Valid, Fast 1.5 Mbit/s | 816.0 Kbit/s 1.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 48.4% | 98% 12.4d | 8d 0.8d | 43.1d 0.8d | 9.7d 48.4% | 98.0% 12.4d | 1.0d 2026-03-15 00:26:19 816 bit/s
faravahar (US) Yes Yes No — N Yes Running, Valid, Fast 1.5 Mbit/s | 816.0 Kbit/s 1.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 48.9% | 98% 11.8d | 8d 0.8d | 53.0d 0.8d | 12.7d 48.9% | 98.0% 11.8d | 1.0d 2026-03-15 00:26:19 816 bit/s
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid 1.5 Mbit/s | 816.0 Kbit/s 1.5 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 48.8% | 98% 12.4d | 8d 0.8d | 58.1d 0.8d | 12.6d 48.8% | 98.0% 12.4d | 1.0d 2026-03-15 00:26:19 24 bit/s
longclaw (US) Yes Yes No — Y Yes Running, Valid, Fast 1.5 Mbit/s | 816.0 Kbit/s 1.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 51.1% | 98% 11.0d | 8d 0.8d | 61.0d 0.8d | 12.7d 51.1% | 98.0% 11.0d | 1.0d 2026-03-15 00:26:19 816 bit/s
maatuska (SE) Yes Yes No — Y Yes Running, Valid 1.5 Mbit/s | 816.0 Kbit/s 1.5 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 48.8% | 98% 12.4d | 8d 0.8d | 40.7d 0.8d | 12.6d 48.8% | 98.0% 12.4d | 1.0d 2026-03-15 00:26:19 24 bit/s
moria1 (US) Yes Yes No — Y Yes Running, Valid, Stable 1.5 Mbit/s | 8.4 Mbit/s 1.5 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 58.1% | 98% 10.0d | 8d 17738.0d | 366.0d 0.8d | 15.4d 58.1% | 98.0% 10.0d | 9.9d 2026-03-15 00:26:19 80 bit/s
tor26 (AT) Yes Yes No — Y Yes Running, Valid 1.5 Mbit/s | 816.0 Kbit/s 1.5 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 48.4% | 98% 11.8d | 8d 0.8d | 53.7d 0.8d | 12.7d 48.4% | 98.0% 11.8d | 1.0d 2026-03-15 00:26:19 24 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.