View Relay "JohnFilch123"

Fingerprint: 07BBC583B96DF5B22B7B18AB4FCF0712D76FAEB3 | Family: 1 relay | relay operator - contact:... | AS208208 | United States of America | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid (2)
BW Verified
4/6 BW Auths Measured
Stability
Not Overloaded | UP 1d 13m 30s ago
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
23h 16m 38s ago
BW Weight
0.00% of Network | 0 Kbit/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: Time Known below threshold : Time Known 0.9 days is below 8 days requirement (7.1 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 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: Time Known below threshold : Time Known 21.3 hours below 25 hours (dir-spec default)
    Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.

Connectivity and Location

Addresses
OR Address
undefined.hostname.localhost
69.42.220.127:9001
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
United States of America United States of America
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS208208
AS Name
Marco Lingl trading as Cyberse GmbH & Co. KG (BGP.tools)
AS Rarity
Epic (score: 3/5, 0.07% consensus weight, 6 operators)

Flags and Eligibility

Current Flags (2): Running, Valid
Eligible Flags (3): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 0/9 | Stable: 0/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 Below (0/9 DA) 8 bit/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: 0.9d (0/9 DA above threshold)
Min/Max: 0.9d / 0.9d (9/9 DA, Voting / Total Eligible)		 ≥11.3d - 54.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥373.6d
Uptime Below (0/9 DA) 1.0d (R) ≥13.6d - 14.8d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (0/9 DA) 0/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 (0/9 DA) 0/9 DA assigned Stable ≥11.3d - 54.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥373.6d
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) Majority: 100.0% (9/9 DA) ≥98.0% (≥5/9 DA)
Time Known Below (0/9 DA) Median: 0.9d (0/9 DA above threshold)
Min/Max: 0.9d / 0.9d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Below (0/9 DA) 0/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 (0/9 DA) 0/9 DA assigned Stable ≥11.3d - 54.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥373.6d
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) Majority: 100.0% (9/9 DA) ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 7.1 more days) Median: 0.9d (0/9 DA above threshold)
Min/Max: 0.9d / 0.9d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 8 bit/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-13 22:15:07).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
0.00 Kbit/s
Advertised Bandwidth
Unknown
Rate Limit
15.27 Mbit/s
Burst Limit
30.54 Mbit/s
Total Data
N/A
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-13 22:15:07

Measured By
4/6 Bandwidth Authorities
Not measured by: longclaw, moria1
Median Measurement
0 bit/s
Min / Max
0 bit/s / 8 bit/s
Network Participation: Consensus Weight: 0.0000% of network (0th pctl) | Guard: N/A | Middle: 0.0000% (0th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 1d 13m 30s ago
Overall Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (0.0%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
23h 16m 38s ago (2026-03-12 23:00:00)
Last Seen
4h 16m 38s ago (2026-03-13 18:00:00)
Last Restarted
1d 13m 30s ago (2026-03-12 22:03:08)
Last Changed Address
2026-03-12 23:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

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

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
relay operator - contact: lucasvandekwq [at] rambler [dot] ru
Family Configuration
Family Support
MyFamily Only (1) — Legacy only. Consider migrating to Happy Families.
Happy Families (family-cert)
Effective 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 Fri, 13 Mar 2026 22:16:37 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-03-13 22:15:07).

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 0 bit/s | 816.0 Kbit/s 0 bit/s | 208.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.9d | 8d 0.9d | 56.1d 1.0d | 14.5d 100.0% | 98.0% 0.9d | 1.0d 2026-03-13 17:03:11 8 bit/s
dannenberg (DE) Yes Yes No — N Yes Running, Valid 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.9d | 8d 0.9d | 11.3d 1.0d | 14.8d 100.0% | 98.0% 0.9d | 1.0d 2026-03-13 17:03:11 —
dizum (NL) Yes Yes No — N Yes Running, Valid 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.9d | 8d 0.9d | 44.2d 1.0d | 13.6d 100.0% | 98.0% 0.9d | 1.0d 2026-03-13 17:03:11 —
faravahar (US) Yes Yes No — N Yes Running, Valid 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.9d | 8d 0.9d | 51.9d 1.0d | 14.9d 100.0% | 98.0% 0.9d | 1.0d 2026-03-13 17:03:11 —
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid 0 bit/s | 816.0 Kbit/s 0 bit/s | 280.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.9d | 8d 0.9d | 58.0d 1.0d | 14.9d 100.0% | 98.0% 0.9d | 1.0d 2026-03-13 17:03:11 8 bit/s
longclaw (US) Yes Yes No — Y Yes Running, Valid 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.9d | 8d 0.9d | 59.1d 1.0d | 14.6d 100.0% | 98.0% 0.9d | 1.0d 2026-03-13 17:03:11 —
maatuska (SE) Yes Yes No — Y Yes Running, Valid 0 bit/s | 816.0 Kbit/s 0 bit/s | 296.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.9d | 8d 0.9d | 39.1d 1.0d | 14.7d 100.0% | 98.0% 0.9d | 1.0d 2026-03-13 17:03:11 8 bit/s
moria1 (US) Yes Yes No — Y Yes Running, Valid 0 bit/s | 8.4 Mbit/s 0 bit/s | 224.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.9d | 8d 0.9d | 373.6d 1.0d | 16.7d 100.0% | 98.0% 0.9d | 9.9d 2026-03-13 17:03:11 —
tor26 (AT) Yes Yes No — Y Yes Running, Valid 0 bit/s | 816.0 Kbit/s 0 bit/s | 272.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.9d | 8d 0.9d | 54.7d 1.0d | 15.3d 100.0% | 98.0% 0.9d | 1.0d 2026-03-13 17:03:11 8 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.