View Relay "CapellaExit21"

Fingerprint: FEF270A500257FC7ED47B27E30EBB2C851F9784C | Family: 1 relay | mismoculas1977@protonmail.com | AS49447 | Netherlands | Linux

Health Status

Consensus
Not In Consensus (2/9 Directory Auths, need 5)
Flags
Running, Valid, V2Dir, Fast, Exit (5)
DNS Health
Not Tested (via exitdnshealth.1aeo.com)
BW Verified
1/6 BW Auths Measured 15 Kbit/s Median
Stability
Not Overloaded | DOWN 6d 8h 3m ago
Reachability
IPv4: 2/9 | v6: 0/7 (Directory Auths)
First Seen
6d 20h 3m ago
BW Weight
0.00% of Network | 28 Mbit/s Observed By Relay
Version
0.4.9.11 Recommended
Issues Detected:
  • Not in consensus : Only 2/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 2/9 authorities can reach this relay
    Suggestion: Authorities that cannot reach you: bastet, 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.
  • IPv6 not reachable : 0/7 authorities that test IPv6 can reach your IPv6 address
    Suggestion: Verify IPv6 is correctly configured: 1) Check ORPort binding includes IPv6 address, 2) Firewall allows IPv6 traffic, 3) IPv6 address is publicly routable. Test with: curl -6 http://ipv6.icanhazip.com/
  • 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: WFU below threshold : Weighted Fractional Uptime 51.9% 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.
  • Guard: Time Known below threshold : Time Known 5.9 days is below 8 days requirement (2.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 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: WFU below threshold : WFU 51.9% 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.
  • 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.
  • Low bandwidth authority measurements : Only 1/6 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.
  • StaleDesc flag assigned : Relay descriptor is older than 18 hours
    Suggestion: Your relay is not publishing fresh descriptors. Check: 1) Tor process is running, 2) Network connectivity, 3) Clock is synchronized (NTP). Restart Tor if needed.

Connectivity and Location

Addresses
OR Address
45.9.148.122:443
Reachability (Directory Authorities)
IPv4
2/9
IPv6
0/7 (2 don't test)
Location
Country
Netherlands Netherlands
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS49447
AS Name
Nice IT Services Group Inc. (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 4 operators)

Flags and Eligibility

Current Flags (5): Running, Valid, V2Dir, Fast, Exit
Eligible Flags (0): Running: 2/9 | Valid: 2/9 | V2Dir: 2/9 | Fast: 2/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 2/9
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Below (2/9 DA) 2/9 authorities reached relay ≥5/9 DA ORPort reachable
IPv6 Reachability Below (0/7 DA) 0/7 tested authorities reached relay ≥4/7 tested (majority) (≥4/7 DA)
Valid Descriptor Partial (2/9 DA) 2/9 authorities assigned Valid Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir DirPort Available Meets (2/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 28.1 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: 4.0d (0/9 DA above threshold)
Min/Max: 4.0d / 4.0d (2/9 DA, Voting / Total Eligible)		 ≥7.8d - 13.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7051.8d
Uptime Below (0/9 DA) 4.2d (R) ≥9.7d - 10.2d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (2/9 DA) 2/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 ≥7.8d - 13.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7051.8d
Prereq: V2Dir Below (2/9 DA) 2/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 51.7% (0/9 DA above threshold)
Min/Max: 51.5% / 51.9% (2/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Below (2/9 DA) Median: 5.8d (0/9 DA above threshold)
Min/Max: 5.7d / 5.9d (2/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Below (2/9 DA) 2/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 ≥7.8d - 13.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7051.8d
Prereq: V2Dir Below (2/9 DA) 2/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 51.7% (0/9 DA above threshold)
Min/Max: 51.5% / 51.9% (2/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 2.2 more days) Median: 5.8d (0/9 DA above threshold)
Min/Max: 5.7d / 5.9d (2/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 28.1 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 Partial (2/9 DA) Port 80: Yes | Port 443: Yes (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-08-24 00:01:31).

Bandwidth Metrics

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

Source: CollecTor — fetched 2026-08-24 00:01:31

Measured By
1/6 Bandwidth Authorities
Not measured by: faravahar, gabelmoo, longclaw, moria1, tor26
Median Measurement
15.2 Kbit/s
Min / Max
2320 bit/s / 28.1 Kbit/s
Deviation
25.8 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0001% of network (9th pctl) | Guard: N/A | Middle: N/A | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
DOWN 6d 8h 3m 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
6d 20h 3m ago (2026-08-17 04:00:00)
Last Seen
6d 8h 3m ago (2026-08-17 16:00:00)
Last Restarted
4d 5h 53m ago (2026-08-19 18:09:21)
Last Changed Address
2026-08-17 04:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-08-23 16:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
mismoculas1977@protonmail.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 
FEF270A500257FC7ED47B27E30EBB2C851F9784C (this relay)
Alleged Members: 22
(they don't list you back) 
0EBC43A4625DE8628B099BAEDE6DF6091F5B7FB3
1A32E111AFC9BEA3609DAB7D92868C0A617CBB6C
1CD4FA8825CA2AD174E0C389333267EBFA441113
1E21501478A9B923CF4AF08F1EA7B45B01A99697
24AD4012C62847A4A6A0E38D57B3951343D05345
2ABC7240B1158685C8F39511EB795F3C3F8574B9
389F1AC7765C1D5E236D7EC6262C4351A40849AA
39773B1A744124C6D31168BD53A8A03B22943C98
526C87600980B4BAD48C26290F257E46C24BCBFA
54022795FE0D536B809F4941CF99854FE55A5CE1
5ADF4644BF5B061163F4A7279E80D24FDF2C8A70
629827CD11BB2928292C4F07A8ED0F0A1D3AD3FA
73E9BD682DE4CB8E99BCBF40AFFE0BC00EDD463B
8D2388EC538339F3E8CE4868ADA12DDA31F79B15
99A98A0EE949CC6B1FCAD9E91BAA03B4F61803F3
A6A8C51F22279E325898D22E5A3BEC895C6EF0CC
BC7BA936F7FC5566654F82859EA1AB75F0531041
C73FE3E5C0E6B10D8DB3EA5A39DDC662898CAF8A
D1BDAB069904D4CAF4B55195A4A2D692DB88BF64
DB8716127C9CCEA3B02C5A1DDAB44BDE01201D5B
E616DC976DD7EA185B8ACA8220D05E74042A3EAE
ECE98F425A40ACC69BF52232F56B38DBCE37786D
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
Not Tested
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 
  80
  443
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 45.9.148.122:*
accept *:80
accept *:443
reject *:*

Last fetch was at Mon, 24 Aug 2026 00:03:03 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-08-24 00:01:31).

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) No — — — N No — — — — — — — — — — — —
dannenberg (DE) Yes Yes Yes — Y Yes — Valid, V2Dir, Fast, Exit, StaleDesc 28.1 Mbit/s | 816.0 Kbit/s 28.1 Mbit/s | 320.0 Mbit/s OR 16.0 Mbit/s 51.9% | 98% 5.9d | 8d 4.0d | 13.4d 4.2d | 11.7d 51.9% | 98.0% 5.9d | 1.0d 2026-08-23 00:53:31 [Stale] 2320 bit/s
dizum (NL) Yes Yes Yes — N Yes — Valid, V2Dir, Fast, Exit, StaleDesc 28.1 Mbit/s | 816.0 Kbit/s 28.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 51.5% | 98% 5.7d | 8d 4.0d | 12.8d 4.2d | 10.0d 51.5% | 98.0% 5.7d | 1.0d 2026-08-23 00:53:31 [Stale] 28.1 Kbit/s
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.