View Relay "OrionNebula"

Fingerprint: B5AB8EE006D42545FF088ABE4807560FECCE8B11 | Family: 1 relay | cmzi3f65f@mozmail.com | AS9009 | Belgium | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, Fast, Stable (4)
BW Verified
6/7 BW Auths Measured 34 Kbit/s Median
Stability
Overloaded | UP 2w 14h 16m ago | UP 98% (1M)
Reachability
IPv4: 9/9 | v6: 8/8 (Directory Auths)
First Seen
2mo 2w 2d ago
BW Weight
0.00% of Network | 48 Mbit/s Observed By Relay
Version
0.4.9.5 Recommended
Issues Detected:
  • 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
  • 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-06-13 19: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.
  • Write Bandwidth Limit Hit : Write rate limit (42 Mbit/s) was hit 22 times. Relay is throttling outbound traffic.
    Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more upload capacity.
  • Read Bandwidth Limit Hit : Read rate limit (42 Mbit/s) was hit 44 times. Relay is throttling inbound traffic.
    Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more download capacity.
Notes:
  • Rate Limit Configuration: Configured limits: Rate=42 Mbit/s, Burst=84 Mbit/s. Limits hit: Write=22, Read=44.

Connectivity and Location

Addresses
OR Address
5.253.205.234:60713
[2001:ac8:27:a:89dd:1215:e83f:6ec6]:60713
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
Location
Country
Belgium Belgium
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS9009
AS Name
M247 Europe SRL (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.26% consensus weight, 23 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, Fast, Stable
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 9/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
IPv6 Reachability Meets (8/8 DA) 8/8 tested authorities reached relay ≥5/8 tested (majority) (≥5/8 DA)
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) 48.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 (1/9 DA) Median: 22.8d (1/9 DA above threshold)
Min/Max: 14.4d / 3652.9d (9/9 DA, Voting / Total Eligible)		 ≥30.6d - 54.6d (varies) (≥5/9 DA)
[Stricter] moria1: ≥297.5d
Uptime Meets (9/9 DA) 14.6d (R) ≥8.6d - 8.9d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/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 Meets (9/9 DA) 9/9 DA assigned Stable ≥30.6d - 54.6d (varies) (≥5/9 DA)
[Stricter] moria1: ≥297.5d
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) Median: 99.6% (9/9 DA above threshold)
Min/Max: 98.8% / 99.7% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 27.5d (9/9 DA above threshold)
Min/Max: 9.9d / 27.8d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Meets (9/9 DA) 9/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 Meets (9/9 DA) 9/9 DA assigned Stable ≥30.6d - 54.6d (varies) (≥5/9 DA)
[Stricter] moria1: ≥297.5d
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) Median: 99.6% (9/9 DA above threshold)
Min/Max: 98.8% / 99.7% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 27.5d (9/9 DA above threshold)
Min/Max: 9.9d / 27.8d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 48.6 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-320.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-06-15 11:15:07).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
48.60 Mbit/s
Advertised Bandwidth
41.94 Mbit/s
Rate Limit
41.94 Mbit/s
Burst Limit
83.89 Mbit/s
Total Data
9.9 TB (6 months)
1mo: 5.3 TB | 6mo: 9.9 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-06-15 11:15:07

Measured By
6/7 Bandwidth Authorities
Not measured by: dannenberg
Median Measurement
34.4 Kbit/s
Min / Max
12.8 Kbit/s / 41.9 Kbit/s
Deviation
29.1 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0017% of network (29th pctl) | Guard: N/A | Middle: 0.0050% (50th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 2w 14h 16m ago
Overall Uptime (1M/6M/1Y/5Y)
98.3%/99.3%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
—/97.0%/—/—
Hibernating
No
Timestamps
First Seen
2mo 2w 2d ago (2026-03-30 18:00:00)
Last Seen
1h 16m 5s ago (2026-06-15 11:00:00)
Last Restarted
2w 14h 16m ago (2026-05-31 22:00:00)
Last Changed Address
2026-04-06 23:00:00
[Warning] OVERLOADED — General overload at 2026-06-13 19:00 UTC; Rate limits hit W:22 R:44 (limit: 42 Mbit/s)
General Overload (from /details)
Status
Reported
When
2026-06-13 19:00 UTC (1 days 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)
Rate Limit
41.94 Mbit/s
Burst Limit
83.89 Mbit/s
Write Limit Hit
22 times
Read Limit Hit
44 times
Last Reported
1 days ago
Recommendations
  • Check CPU/memory: htop
  • Review MaxMemInQueues in torrc
  • Consider increasing RelayBandwidthRate
  • Check if ISP is throttling traffic

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-06-15 04:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
cmzi3f65f@mozmail.com
Family Configuration
Family Support
MyFamily Only (1) — Legacy only. Consider migrating to Happy Families.
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
B5AB8EE006D42545FF088ABE4807560FECCE8B11 (this relay)
Alleged Member: 1
(they don't list you back) 
347585E3B037D9E7BD894D3283AF792969800FFA
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 Mon, 15 Jun 2026 12:16:04 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-06-15 11: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 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, Fast, Stable 48.6 Mbit/s | 816.0 Kbit/s 48.6 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 99.6% | 98% 27.8d | 8d 22.8d | 57.3d 14.6d | 9.6d 99.6% | 98.0% 27.8d | 1.0d 2026-06-15 04:00:41 12.8 Kbit/s
dannenberg (DE) Yes Yes No — Y Yes Yes Running, Valid, Fast, Stable 48.6 Mbit/s | 816.0 Kbit/s 48.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.6% | 98% 27.8d | 8d 22.8d | 30.6d 14.6d | 8.6d 99.6% | 98.0% 27.8d | 1.0d 2026-06-15 04:00:41 41.9 Kbit/s
dizum (NL) Yes Yes No — N Yes Yes Running, Valid, Fast, Stable 48.6 Mbit/s | 816.0 Kbit/s 48.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.2% | 98% 17.9d | 8d 14.4d | 34.3d 14.6d | 8.8d 99.2% | 98.0% 17.9d | 1.0d 2026-06-15 04:00:41 41.9 Kbit/s
faravahar (US) Yes Yes No — N Yes Yes Running, Valid, Fast, Stable 48.6 Mbit/s | 816.0 Kbit/s 48.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.6% | 98% 27.8d | 8d 22.8d | 52.5d 14.6d | 8.8d 99.6% | 98.0% 27.8d | 1.0d 2026-06-15 04:00:41 41.9 Kbit/s
gabelmoo (DE) Yes Yes No — Y Yes Yes Running, Valid, Fast, Stable 48.6 Mbit/s | 816.0 Kbit/s 48.6 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 99.5% | 98% 27.8d | 8d 22.8d | 54.9d 14.6d | 9.0d 99.5% | 98.0% 27.8d | 1.0d 2026-06-15 04:00:41 30.4 Kbit/s
longclaw (US) Yes Yes No — Y Yes — Running, Valid, Fast, Stable 48.6 Mbit/s | 816.0 Kbit/s 48.6 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 99.7% | 98% 27.0d | 8d 22.2d | 60.3d 14.6d | 8.9d 99.7% | 98.0% 27.0d | 1.0d 2026-06-15 04:00:41 27.2 Kbit/s
maatuska (SE) Yes Yes No — Y Yes Yes Running, Valid, Fast, Stable 48.6 Mbit/s | 816.0 Kbit/s 48.6 Mbit/s | 320.0 Mbit/s OR 16.0 Mbit/s 99.5% | 98% 23.4d | 8d 19.0d | 31.1d 14.6d | 8.8d 99.5% | 98.0% 23.4d | 1.0d 2026-06-15 04:00:41 34.4 Kbit/s
moria1 (US) Yes Yes No — Y Yes Yes Running, Valid, Fast, Stable 48.6 Mbit/s | 8.4 Mbit/s 48.6 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 98.8% | 98% 9.9d | 8d 3652.9d | 297.5d 14.6d | 9.0d 98.8% | 98.0% 9.9d | 9.8d 2026-06-15 04:00:41 34.4 Kbit/s
tor26 (AT) Yes Yes No — Y Yes Yes Running, Valid, Fast, Stable 48.6 Mbit/s | 816.0 Kbit/s 48.6 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 99.6% | 98% 27.5d | 8d 22.6d | 54.6d 14.6d | 9.0d 99.6% | 98.0% 27.5d | 1.0d 2026-06-15 04:00:41 27.2 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.