View Relay "OrionNebula"

Fingerprint: 90AA960DED041BF15E1C1A1B1D339410F1D4FB19 | Family: 1 relay | cmzi3f65f@mozmail.com | AS9009 | Romania | Linux

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
5/7 BW Auths Measured 13 Mbit/s Median
Stability
Overloaded | UP 3d 4h 57m ago | UP 84% (1M)
Reachability
IPv4: 9/9 | v6: 8/8 (Directory Auths)
BW Weight
0.00% of Network | 13 Mbit/s Observed By Relay
Version
0.4.9.12 Recommended
Issues Detected:
  • Guard: bandwidth below threshold : 0/9 authorities credit this relay with enough bandwidth for Guard (5 needed): at least 16.8 Mbit/s (AuthDirGuardBWGuarantee) or a place in their top 25% (80.0 Mbit/s – 288.0 Mbit/s). bastet, dannenberg, gabelmoo, moria1 and tor26 measured this relay at 12.8 Mbit/s – 15.2 Mbit/s. dizum, longclaw and maatuska used the relay-reported 12.6 Mbit/s.
    Suggestion: Guard requires a bandwidth of at least AuthDirGuardBWGuarantee (16.8 Mbit/s by default) or one in the top 25% of relays, judged by each authority the same way as for Fast. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx.
  • Guard: WFU below threshold : Weighted Fractional Uptime 96.6% is below 98% requirement
    Suggestion: WFU measures recent uptime (recent downtime weighs more heavily). To improve: 1) Minimize restarts, 2) Use systemd with Restart=always, 3) Monitor for OOM kills, 4) Schedule updates during low-traffic periods.
  • HSDir: WFU below threshold : WFU 96.6% below 98% required for HSDir
    Suggestion: HSDir requires ≥98% WFU, Stable flag, and Time Known ≥25 hours (or ~10 days for moria1). Improve uptime consistency.
  • Write Bandwidth Limit Hit : Write rate limit (13 Mbit/s) was hit 455 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 (13 Mbit/s) was hit 1,946 times. Relay is throttling inbound traffic.
    Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more download capacity.
Notes:

Addresses
OR Address
89.238.167.151:9005
[2001:ac8:8b:81:700:ad72:5823:ba84]:9005
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
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, 17 operators)

Current Flags (5): Running, Valid, V2Dir, 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 Meets (9/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 12.8 Mbit/s – 15.2 Mbit/s (5 DA measured)
12.6 Mbit/s (3 DA relay-reported)
faravahar: not published
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Partial (5/9 DA) Median: 10.4d (7/9 DA above threshold)
Min/Max: 5.9d / 7338.1d (9/9 DA, Voting / Total Eligible)
≥6.4d - 10.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥9669.9d
Uptime Below (0/9 DA) 3.2d (R) ≥5.1d - 5.2d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
12.8 Mbit/s – 15.2 Mbit/s (5 DA measured)
12.6 Mbit/s (3 DA relay-reported)
faravahar: not published
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Meets (9/9 DA) 9/9 DA assigned Stable ≥6.4d - 10.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥9669.9d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 96.4% (0/9 DA above threshold)
Min/Max: 95.7% / 96.6% (9/9 DA, Voting / Total Eligible)
≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 16.6d (9/9 DA above threshold)
Min/Max: 9.8d / 17.3d (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
12.8 Mbit/s – 15.2 Mbit/s (5 DA measured)
12.6 Mbit/s (3 DA relay-reported)
faravahar: not published
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Meets (9/9 DA) 9/9 DA assigned Stable ≥6.4d - 10.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥9669.9d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 96.4% (0/9 DA above threshold)
Min/Max: 95.7% / 96.6% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 16.6d (9/9 DA above threshold)
Min/Max: 9.8d / 17.3d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 12.8 Mbit/s – 15.2 Mbit/s (5 DA measured)
12.6 Mbit/s (3 DA relay-reported)
faravahar: not published
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-288.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-10-16 02:45:05).

Capacity (Relay Reported)
Observed Bandwidth
13.98 Mbit/s
Advertised Bandwidth
12.58 Mbit/s
Rate Limit
12.58 Mbit/s
Burst Limit
16.78 Mbit/s
Total Data
56 TB (6 months)
1mo: 25 TB | 6mo: 56 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-10-16 02:45:05

Measured By
5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Consensus Weight
13.6 Mbit/s (median of 5 measurements)
Measured Min / Max
12.8 Mbit/s / 15.2 Mbit/s
Network Participation: Consensus Weight: 0.0009% of network (16th pctl) | Guard: N/A | Middle: 0.0025% (29th pctl) | Exit: N/A
History
Throughput and write/read, last 6 months Throughput and write/read, last 30 days
1M 6M

Uptime Metrics
Current Status
UP 3d 4h 57m ago
Overall Uptime (1M/6M/1Y/5Y)
84.5%/88.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
—/86.4%/—/—
Hibernating
No
Timestamps
First Seen
1mo 2w 1d ago (2026-08-31 23:00:00)
Last Seen
1h 45m 9s ago (2026-10-16 02:00:00)
Last Restarted
3d 4h 57m ago (2026-10-12 22:47:56)
Last Changed Address
2026-08-31 23:00:00
[Warning] OVERLOADED — Rate limits hit W:455 R:1946 (limit: 13 Mbit/s)
General Overload (from /details)
Status
Reported
When
2026-10-13 00:00 UTC (3 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
12.58 Mbit/s
Burst Limit
2.1 MB
Write Limit Hit
455 times
Read Limit Hit
1,946 times
Last Reported
23 hours ago
Recommendations
  • Check CPU/memory: htop
  • Review MaxMemInQueues in torrc
  • Consider increasing RelayBandwidthRate
  • Check if ISP is throttling traffic
History
Uptime, last 6 months Uptime, last 30 days
1M 6M

Operator Identity

Source: AROI Validation API — 2026-10-15 19: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
90AA960DED041BF15E1C1A1B1D339410F1D4FB19 (this relay)
Alleged Member: 1
(they don't list you back)
B5AB8EE006D42545FF088ABE4807560FECCE8B11 (not in the network)
Indirect Members: 0
none

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

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, 16 Oct 2026 03:45:08 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-10-16 02:45:05).

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 (BW|T) Guard BW (BW|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 14.4 Mbit/s (M) | 816.0 Kbit/s 14.4 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 96.6% | 98% 16.6d | 8d 10.4d | 10.0d 3.2d | 5.1d 96.6% | 98.0% 16.6d | 1.0d 2026-10-15 22:48:26 14.4 Mbit/s (M)
dannenberg (DE) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable 13.6 Mbit/s (M) | 816.0 Kbit/s 13.6 Mbit/s (M) | 288.0 Mbit/s OR 16.8 Mbit/s 96.5% | 98% 16.6d | 8d 9.4d | 6.4d 3.2d | 5.2d 96.5% | 98.0% 16.6d | 1.0d 2026-10-15 22:48:26 13.6 Mbit/s (M)
dizum (NL) Yes Yes No — N Yes Yes Running, Valid, V2Dir, Fast, Stable 12.6 Mbit/s (R) | 816.0 Kbit/s 12.6 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 96.5% | 98% 16.6d | 8d 10.4d | 10.2d 3.2d | 5.2d 96.5% | 98.0% 16.6d | 1.0d 2026-10-15 22:48:26 12.6 Mbit/s (R)
faravahar (US) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable not published | 816.0 Kbit/s not published | 288.0 Mbit/s OR 16.8 Mbit/s 96.4% | 98% 16.8d | 8d 10.4d | 10.8d 3.2d | 5.5d 96.4% | 98.0% 16.8d | 1.0d 2026-10-15 22:48:26 12.6 Mbit/s (R)
gabelmoo (DE) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable 15.2 Mbit/s (M) | 816.0 Kbit/s 15.2 Mbit/s (M) | 264.0 Mbit/s OR 16.8 Mbit/s 95.8% | 98% 14.2d | 8d 5.9d | 10.1d 3.2d | 5.2d 95.8% | 98.0% 14.2d | 1.0d 2026-10-15 22:48:26 15.2 Mbit/s (M)
longclaw (US) Yes Yes No — Y Yes — Running, Valid, V2Dir, Fast, Stable 12.6 Mbit/s (R) | 816.0 Kbit/s 12.6 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 96.4% | 98% 16.8d | 8d 10.4d | 10.4d 3.2d | 5.2d 96.4% | 98.0% 16.8d | 1.0d 2026-10-15 22:48:26 12.6 Mbit/s (R)
maatuska (SE) Yes Yes No — N Yes Yes Running, Valid, V2Dir, Fast, Stable 12.6 Mbit/s (R) | 816.0 Kbit/s 12.6 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 96.4% | 98% 16.6d | 8d 10.4d | 9.9d 3.2d | 5.2d 96.4% | 98.0% 16.6d | 1.0d 2026-10-15 22:48:26 12.6 Mbit/s (R)
moria1 (US) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable 13.6 Mbit/s (M) | 8.4 Mbit/s 13.6 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 95.7% | 98% 9.8d | 8d 7338.1d | 9669.9d 3.2d | 5.2d 95.7% | 98.0% 9.81d | 9.82d 2026-10-15 22:48:26 13.6 Mbit/s (M)
tor26 (AT) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable 12.8 Mbit/s (M) | 816.0 Kbit/s 12.8 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s 96.6% | 98% 17.3d | 8d 12.6d | 10.4d 3.2d | 5.1d 96.6% | 98.0% 17.3d | 1.0d 2026-10-15 22:48:26 12.8 Mbit/s (M)

— = not tested/available • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known • Bandwidth source: (M) bandwidth-scanner measurement, (R) relay-reported, (U) unmeasured, counted as 0

Bandwidth Values Explained:
Measured (M) = An authority's bandwidth-scanner measurement of your relay (Measured= in its vote). An authority that has one uses it for the Fast and Guard flags, and the consensus weight is the median of these measurements when 3 or more authorities have one.
Relay-reported (R) = The bandwidth your relay advertises: the lower of its observed bandwidth and its rate limit, capped at 10 MB/s (Bandwidth= in every vote). An authority without a measurement uses it for flags, unless it has measurements for enough other relays (ignoring-advertised-bws=1); then your relay counts as 0 (U). It sets the consensus weight only when fewer than 3 authorities measured the relay, capped at 20 KB/s (maxunmeasuredbw) while 3 or more authorities publish measurements.
Not published = The authority has no measurement of your relay in its vote and ignores relay-reported bandwidth, yet it voted Fast or its vote has no measurements at all: it judges your relay by a measurement kept from an earlier bandwidth file (0 if none), which its vote doesn't show.
Why different? A low measurement means the bandwidth scanners see your relay underperforming compared with other relays that report a similar speed. Votes list both values in kilobytes per second. Rules: Assigning flags in a vote, Computing a consensus.
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.