View Relay "Unnamed"

Fingerprint: D8A2CD055918D0A7FF5C9AEAA876F1DC82C38DED | Family: 1 relay | foolish5264@inbox.lv | AS200651 | Finland | Linux

Health Status

Consensus
Not In Consensus (1/9 Directory Auths, need 5)
Flags
Running, Valid, Fast, Stable, MiddleOnly, BadExit (6)
BW Verified
1/7 BW Auths Measured 8 bit/s Median
Stability
Not Overloaded | DOWN 1d 17h 7m ago | UP 100% (1M)
Reachability
IPv4: 1/9 | v6: 1/9 (Directory Auths)
First Seen
6d 22h 7m ago
BW Weight
0.01% of Network | 63 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: Time Known below threshold : Time Known 5.1 days is below 8 days requirement (2.9 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.
  • 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
  • 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.
  • BadExit flag assigned : This relay has been flagged as a bad exit by directory authorities. BadExit means authorities detected malicious behavior (traffic modification, SSL stripping, etc.).
    Suggestion: Contact bad-relays@lists.torproject.org to understand and resolve this issue.
  • MiddleOnly restriction active : This relay has been restricted to middle position only by directory authorities. MiddleOnly removes Guard, Exit, HSDir, and V2Dir flags, and adds BadExit. This significantly limits the relay's role in the network.
    Suggestion: This may indicate suspicious behavior patterns, Sybil risk indicators, or policy violations. Contact bad-relays@lists.torproject.org for more information.
  • 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.

Connectivity and Location

Addresses
OR Address
37.228.129.155:9001
[2a06:1700:1:52::1194:5ce1]:9001
Reachability (Directory Authorities)
IPv4
1/9
IPv6
1/9
Location
Country
Finland Finland
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS200651
AS Name
FlokiNET ehf (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.69% consensus weight, 25 operators)

Flags and Eligibility

Current Flags (6): Running, Valid, Fast, Stable, MiddleOnly, BadExit
Eligible Flags (0): Running: 1/9 | Valid: 1/9 | V2Dir: 1/9 | Fast: 0/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 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 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) 63.6 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: 5.1d (0/9 DA above threshold) ≥3.2d - 11.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥6577.2d
Uptime Meets (9/9 DA) 7.0d (R) ≥3.3d - 3.3d (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 (1/9 DA) 1/9 DA assigned Stable ≥3.2d - 11.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥6577.2d
Prereq: V2Dir Below (0/9 DA) 0/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: 5.1d (0/9 DA above threshold) ≥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 (1/9 DA) 1/9 DA assigned Stable ≥3.2d - 11.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥6577.2d
Prereq: V2Dir Below (0/9 DA) 0/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 2.9 more days) Median: 5.1d (0/9 DA above threshold) ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 63.6 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 Partial (0/9 DA) (only port 80) Port 80: Yes | Port 443: Yes (R) Allows ≥1 /8 on ports 80 AND 443 (≥5/9 DA)
MiddleOnly Restriction (by DA) Flagged (1/9 DA) 1/9 authorities assigned MiddleOnly Suspicious behavior, Sybil risk, or policy violation

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-11-08 08:01:41).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
63.62 Mbit/s
Advertised Bandwidth
63.62 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
123 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
8 bit/s
Min / Max
8 bit/s / 8 bit/s
Network Participation: Consensus Weight: 0.0059% of network (56th pctl) | Guard: N/A | Middle: N/A | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
DOWN 1d 17h 7m ago
Overall Uptime (1M/6M/1Y/5Y)
100.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (100.0%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
6d 22h 7m ago (2026-11-01 10:00:00)
Last Seen
1d 17h 7m ago (2026-11-06 15:00:00)
Last Restarted
6d 23h 13m ago (2026-11-01 08:54:01)
Last Changed Address
2026-11-01 10:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

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
foolish5264@inbox.lv
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
D8A2CD055918D0A7FF5C9AEAA876F1DC82C38DED (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

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

Exit Health & Policy

DNS Health
Not an exit relay — DNS health testing does not apply.
IPv4 Exit Policy Summary
reject: 
  22-23
  25
  110
  143
  445
  465
  587
  631
  993
  995
  2525
  3389
  5900
  5998-6063
  6667
  6697
  11211
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 37.228.129.155:*
reject *:6697
reject *:6029-6031
reject *:6054-6056
reject *:6039-6042
reject *:6012-6015
reject *:11211
reject *:6057-6060
reject *:6020-6023
reject *:5900
reject *:6061-6063
reject *:5998-5999
reject *:6005-6007
reject *:6051-6053
reject *:465
reject *:110
reject *:445
reject *:6024-6026
reject *:993
reject *:6045-6048
reject *:6036-6038
reject *:587
reject *:3389
reject *:6667
reject *:143
reject *:2525
reject *:6003-6004
reject *:6000-6002
reject *:6008-6011
reject *:6027-6028
reject *:6016-6019
reject *:995
reject *:22-23
reject *:6049-6050
reject *:25
reject *:631
reject *:6032-6035
reject *:6043-6044
accept *:*

Last fetch was at Sun, 08 Nov 2026 08:06:52 GMT.

Consensus Evaluation

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

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 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 Yes Y Yes Yes Running, Valid, Stable, MiddleOnly 63.6 Mbit/s | 816.0 Kbit/s 63.6 Mbit/s | 184.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 5.1d | 8d 5.1d | 9.7d 7.0d | 5.7d 100.0% | 98.0% 5.1d | 1.0d 2026-11-05 22:09:28 8 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.