View Relay "freedomsentinel"

Fingerprint: D15783D28B5759BB432D1A5EB70B0B12F3F410D7 | Family: 1 relay | superadmin@nigge.rs | AS9009 | Romania | Linux

Health Status

Consensus
In Consensus (7/7 Directory Auths)
Flags
Running, Valid, V2Dir, Fast, Exit (5)
DNS Health
Healthy (15.6s, 35th percentile) (via exitdnshealth.1aeo.com)
BW Verified
5/6 BW Auths Measured 27 Kbit/s Median
Stability
Overloaded | UP 5d 21h 45m ago | UP 99% (1M)
Reachability
IPv4: 7/7 | v6: 7/7 (Directory Auths)
First Seen
5d 22h 3m ago
BW Weight
0.00% of Network | 38 Mbit/s Observed By Relay
Version
0.4.9.11 Recommended
Issues Detected:
  • 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 5.6 days is below 8 days requirement (2.4 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.
  • 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.
  • General Overload Active : Relay reported general overload at 2026-07-19 01:00 UTC. This indicates OOM killer invocation, onionskin queue saturation, or TCP port exhaustion.
    Suggestion: Check CPU/memory with htop. Review logs for "out of memory" or "onionskins" warnings. Consider increasing MaxMemInQueues in torrc. Verify TCP ports available.

Connectivity and Location

Addresses
OR Address
159.20.97.83.ro.ovo.sc
83.97.20.159:9001
[2a04:9dc0:31::c0cc:9f]:9001
Exit Address
83.97.20.159
Reachability (Directory Authorities)
IPv4
7/7
IPv6
7/7
Location
Country
Romania Romania
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS9009
AS Name
M247 Europe SRL (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.28% consensus weight, 22 operators)

Flags and Eligibility

Current Flags (5): Running, Valid, V2Dir, Fast, Exit
Eligible Flags (5): Running: 7/7 | Valid: 7/7 | V2Dir: 7/7 | Fast: 7/7 | Stable: 2/7 | HSDir: 1/7 | Guard: 0/7 | Exit: 7/7
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (7/7 DA) 7/7 authorities reached relay ≥4/7 DA ORPort reachable
IPv6 Reachability Meets (7/7 DA) 7/7 tested authorities reached relay ≥4/7 tested (majority) (≥4/7 DA)
Valid Descriptor Meets (7/7 DA) 7/7 authorities assigned Valid Not blacklisted + valid descriptor (≥4/7 DA)
V2Dir DirPort Available Meets (7/7 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥4/7 DA)
Fast Speed Meets (7/7 DA) 38.6 Mbit/s (R) ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (1/7 DA) Median: 2.8d (1/7 DA above threshold)
Min/Max: 2.8d / 10062.1d (7/7 DA, Voting / Total Eligible)		 ≥8.4d - 15.1d (varies) (≥4/7 DA)
[Stricter] moria1: ≥9211.0d
Uptime Below (0/7 DA) 5.9d (R) ≥8.4d - 8.5d (varies) (≥4/7 DA)
HSDir Prereq: Fast Meets (7/7 DA) 7/7 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (2/7 DA) 2/7 DA assigned Stable ≥8.4d - 15.1d (varies) (≥4/7 DA)
[Stricter] moria1: ≥9211.0d
Prereq: V2Dir Meets (7/7 DA) 7/7 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥4/7 DA)
WFU Meets (7/7 DA) Median: 99.2% (7/7 DA above threshold)
Min/Max: 99.0% / 100.0% (7/7 DA, Voting / Total Eligible)		 ≥98.0% (≥4/7 DA)
Time Known Meets (6/7 DA) Median: 5.3d (0/7 DA above threshold)
Min/Max: 4.4d / 5.8d (7/7 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥4/7 DA)
[Stricter] moria1: ≥10.0d
Guard Prereq: Fast Meets (7/7 DA) 7/7 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (2/7 DA) 2/7 DA assigned Stable ≥8.4d - 15.1d (varies) (≥4/7 DA)
[Stricter] moria1: ≥9211.0d
Prereq: V2Dir Meets (7/7 DA) 7/7 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥4/7 DA)
WFU Meets (7/7 DA) Median: 99.2% (7/7 DA above threshold)
Min/Max: 99.0% / 100.0% (7/7 DA, Voting / Total Eligible)		 ≥98% (≥4/7 DA)
Time Known Below (0/7 DA) (need 2.7 more days) Median: 5.3d (0/7 DA above threshold)
Min/Max: 4.4d / 5.8d (7/7 DA, Voting / Total Eligible)		 ≥8 days (≥4/7 DA)
Bandwidth Meets (7/7 DA) 38.6 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-280.0 Mbit/s (≥4/7 DA)
Exit Exit Policy Meets (7/7 DA) Port 80: Yes | Port 443: Yes (R) Allows ≥1 /8 on ports 80 AND 443 (≥4/7 DA)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-07-19 22:00:24).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
38.61 Mbit/s
Advertised Bandwidth
38.61 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
205 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-07-19 22:00:24

Measured By
5/6 Bandwidth Authorities
Not measured by: bastet
Median Measurement
27.2 Kbit/s
Min / Max
15.2 Kbit/s / 72.0 Kbit/s
Deviation
56.8 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0014% of network (27th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0042% (20th pctl)

Uptime and Stability

Uptime Metrics
Current Status
UP 5d 21h 45m ago
Overall Uptime (1M/6M/1Y/5Y)
99.2%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (99.2%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
5d 22h 3m ago (2026-07-14 01:00:00)
Last Seen
3h 3m 13s ago (2026-07-19 20:00:00)
Last Restarted
5d 21h 45m ago (2026-07-14 01:18:04)
Last Changed Address
2026-07-14 01:00:00
[Warning] OVERLOADED — General overload at 2026-07-19 01:00 UTC
General Overload (from /details)
Status
Reported
When
2026-07-19 01:00 UTC (22 hours ago)

OOM killer, onionskin queue saturation, or TCP port exhaustion. Flag remains 72h after last event (Tor spec 328).

File Descriptor Exhaustion (from /bandwidth)
Status
Not Reported
Rate Limits (from /bandwidth)

No rate limit data from /bandwidth endpoint.

Recommendations
  • Check CPU/memory: htop
  • Review MaxMemInQueues in torrc

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-07-19 14:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
superadmin@nigge.rs
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
D15783D28B5759BB432D1A5EB70B0B12F3F410D7 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

Platform
Linux — Tor 0.4.9.11 on Linux
Version
0.4.9.11 — Recommended
Version Status
Recommended

Exit Health & Policy

DNS Health
Status
Healthy (avg. 15.6s, 35th percentile)
Query Domain
cf2f6b34ec794061baffc359f580b81c.d15783d2.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
1/1 instances succeeded
First Hop
TonyI (DK) 1C75E1F02A0A7CBB70E72D194298B3DA3A622CDF
Exit Address Used
83.97.20.159
Per-Instance Results
Cross Validation Attempt 1: Success, 15.6s (cv4_w4)
Tested: 2026-07-19 07:23:10 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
reject: 
  25
  119
  135-139
  445
  563
  1214
  4661-4666
  6346-6429
  6699
  6881-6999
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 83.97.20.159:*
reject *:25
reject *:119
reject *:135-139
reject *:445
reject *:563
reject *:1214
reject *:4661-4666
reject *:6346-6429
reject *:6699
reject *:6881-6999
accept *:*

Last fetch was at Sun, 19 Jul 2026 23:03:07 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-07-19 22:00:24).

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 Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 38.6 Mbit/s | 816.0 Kbit/s 38.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.2% | 98% 5.6d | 8d 2.8d | 21.3d 5.9d | 8.4d 99.2% | 98.0% 5.6d | 1.0d 2026-07-19 20:34:06 38.6 Kbit/s
dannenberg (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 38.6 Mbit/s | 816.0 Kbit/s 38.6 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 5.8d | 8d 5.8d | 8.4d 5.9d | 8.5d 100.0% | 98.0% 5.8d | 1.0d 2026-07-19 20:34:06 15.2 Kbit/s
dizum (NL) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Exit 38.6 Mbit/s | 816.0 Kbit/s 38.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.0% | 98% 5.6d | 8d 2.8d | 13.5d 5.9d | 8.5d 99.0% | 98.0% 5.6d | 1.0d 2026-07-19 20:34:06 38.6 Kbit/s
faravahar (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 38.6 Mbit/s | 816.0 Kbit/s 38.6 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 99.2% | 98% 5.3d | 8d 2.8d | 14.4d 5.9d | 8.5d 99.2% | 98.0% 5.3d | 1.0d 2026-07-19 20:34:06 27.2 Kbit/s
maatuska (SE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 38.6 Mbit/s | 816.0 Kbit/s 38.6 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 99.2% | 98% 5.3d | 8d 2.8d | 15.1d 5.9d | 8.5d 99.2% | 98.0% 5.3d | 1.0d 2026-07-19 20:34:06 72.0 Kbit/s
moria1 (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, Exit 38.6 Mbit/s | 8.4 Mbit/s 38.6 Mbit/s | 208.0 Mbit/s OR 16.0 Mbit/s 99.0% | 98% 4.4d | 8d 10062.1d | 9211.0d 5.9d | 8.5d 99.0% | 98.0% 4.4d | 10.0d 2026-07-19 20:34:06 16.8 Kbit/s
tor26 (AT) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 38.6 Mbit/s | 816.0 Kbit/s 38.6 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 99.2% | 98% 5.3d | 8d 2.8d | 21.1d 5.9d | 8.5d 99.2% | 98.0% 5.3d | 1.0d 2026-07-19 20:34:06 21.6 Kbit/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.