View Relay "SimpleRelay"

Fingerprint: F6A15529089F0A6B9D5A8929E74F5A422A216550 | Family: 1 relay | k56157602@gmail.com | AS202831 | Germany | Linux

Consensus
Not In Consensus (1/9 Directory Auths, need 5)
BW Verified
1/7 BW Auths Measured 3200 bit/s Median
Stability
Not Overloaded | DOWN 1d 14h 7m ago | UP 99% (1M)
Reachability
IPv4: 1/9 | v6: 1/9 (Directory Auths)
BW Weight
0.00% of Network | 22 Mbit/s Observed By Relay
Version
0.4.9.14 Not Recommended
Issues Detected:
  • Not in consensus : Only 1/9 authorities voted for this relay (need 5)
    Suggestion: Verify your relay is reachable from multiple geographic locations. Check firewall rules allow incoming connections on your ORPort from all directory authority IP addresses.
  • IPv4 reachability issues : Only 1/9 authorities can reach this relay
    Suggestion: Authorities that cannot reach you: dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1, tor26. Check: 1) Firewall allows incoming TCP on ORPort, 2) No ISP-level blocking, 3) Tor is running and listening. Use 'nc -zv your-ip your-orport' from external hosts to test.
  • 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 6.8 days is below 8 days requirement (1.2 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 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.
  • Low bandwidth authority measurements : Only 1/7 bandwidth authorities measured this relay. Minimum 3 measurements needed for accurate consensus weight.
    Suggestion: Low measurement count can indicate connectivity issues. Check: 1) Relay is reachable from multiple geographic locations, 2) ORPort accepts connections from bandwidth scanners, 3) RelayBandwidthRate in torrc matches actual capacity. New relays may take 1-2 days to be measured by all authorities.
  • 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.

Addresses
OR Address
31.77.251.136:9001
[2a0c:b641:614:218::1]:9001
Reachability (Directory Authorities)
IPv4
1/9
IPv6
1/9
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS202831
AS Name
Packet Loss LTD (BGP.tools)
AS Rarity
Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

Current Flags (4): Running, Valid, V2Dir, Fast
Eligible Flags (0): Running: 1/9 | Valid: 1/9 | V2Dir: 1/9 | Fast: 1/9 | Stable: 1/9 | HSDir: 1/9 | Guard: 0/9 | Exit: 0/9
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Below (1/9 DA) 1/9 authorities reached relay ≥5/9 DA ORPort reachable
IPv6 Reachability Partial (1/9 DA) 1/9 tested authorities reached relay ≥5/9 tested (majority) (≥5/9 DA)
Valid Descriptor Partial (1/9 DA) 1/9 authorities assigned Valid Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir DirPort Available Meets (1/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 22.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 (0/9 DA) Median: 6.8d (0/9 DA above threshold) ≥3.2d - 11.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥6577.2d
Uptime Below (0/9 DA) 1.6d (R) ≥3.3d - 3.3d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (1/9 DA) 1/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 ≥3.2d - 11.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥6577.2d
Prereq: V2Dir Below (1/9 DA) 1/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (1/9 DA) Median: 100.0% (1/9 DA above threshold) ≥98.0% (≥5/9 DA)
Time Known Below (1/9 DA) Median: 6.8d (0/9 DA above threshold) ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Below (1/9 DA) 1/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 ≥3.2d - 11.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥6577.2d
Prereq: V2Dir Below (1/9 DA) 1/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (1/9 DA) Median: 100.0% (1/9 DA above threshold) ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 1.2 more days) Median: 6.8d (0/9 DA above threshold) ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 22.4 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-280.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-08 08:01:41).

Capacity (Relay Reported)
Observed Bandwidth
22.43 Mbit/s
Advertised Bandwidth
22.43 Mbit/s
Rate Limit
24.58 Mbit/s
Burst Limit
40.96 Mbit/s
Total Data
92 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-08 08:01:41

Measured By
1/7 Bandwidth Authorities
Not measured by: dannenberg, faravahar, gabelmoo, longclaw, moria1, tor26
Median Measurement
3200 bit/s
Min / Max
3200 bit/s / 3200 bit/s
Network Participation: Consensus Weight: 0.0010% of network (22th pctl) | Guard: N/A | Middle: N/A | Exit: N/A

Uptime Metrics
Current Status
DOWN 1d 14h 7m ago
Overall Uptime (1M/6M/1Y/5Y)
99.4%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
51.2%/—/—/—
Hibernating
No
Timestamps
First Seen
1w 1d 16h ago (2026-10-30 16:00:00)
Last Seen
1d 14h 7m ago (2026-11-06 18:00:00)
Last Restarted
1d 14h 39m ago (2026-11-06 17:27:36)
Last Changed Address
2026-10-30 16:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator Identity

Source: AROI Validation API — 2026-11-07 23:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
k56157602@gmail.com
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1
F6A15529089F0A6B9D5A8929E74F5A422A216550 (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
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, 08 Nov 2026 08:06:52 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-11-08 08:01:41).

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 v6 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 Yes Running, Valid, V2Dir, Fast, Stable, HSDir 22.4 Mbit/s | 816.0 Kbit/s 22.4 Mbit/s | 184.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 6.8d | 8d 6.8d | 9.7d 1.6d | 5.7d 100.0% | 98.0% 6.8d | 1.0d 2026-11-05 21:14:01 3200 bit/s
dannenberg (DE) No — — — Y No — — — — — — — — — — — —
dizum (NL) No — — — N No — — — — — — — — — — — —
faravahar (US) No — — — Y No — — — — — — — — — — — —
gabelmoo (DE) No — — — Y No — — — — — — — — — — — —
longclaw (US) No — — — Y No — — — — — — — — — — — —
maatuska (SE) No — — — N No — — — — — — — — — — — —
moria1 (US) No — — — Y No — — — — — — — — — — — —
tor26 (AT) No — — — Y No — — — — — — — — — — — —

— = 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.