View Relay "alliumobserver"

Fingerprint: EF85B8F53A394B7BD79698D2FC01171FDD96C823 | Operator: allium.observer v3 (2 relays) ✓ Validated ⚠ this relay: Misconfigured| Family: 1 relay | email:a78i2efsewr0neeknk[]proton.me... | AS53667 | Luxembourg | Linux

Health Status

Consensus
In Consensus (6/9 Directory Auths)
Flags
Running, Valid, V2Dir, Exit (4)
DNS Health
Not Tested (via exitdnshealth.1aeo.com)
BW Verified
1/7 BW Auths Measured 160 Kbit/s Median
Stability
Not Overloaded | UP 12h 39m 39s ago
Reachability
IPv4: 6/9 | v6: 5/8 (Directory Auths)
First Seen
2h 15m 40s ago
BW Weight
0.00% of Network | 1 Mbit/s Observed By Relay
Version
0.4.9.14 Recommended
Issues Detected:
  • Not getting the Fast flag : Only 3/9 authorities vote Fast (5 needed). gabelmoo measured this relay at 8.0 Kbit/s, below the Fast threshold (816.0 Kbit/s). dannenberg and moria1 counted this relay as 0 (no measurement, relay-reported bandwidth ignored).
    Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports. A low measurement means the scanners see your relay underperforming compared with other relays that report a similar speed. Clients only build circuits through Fast relays, so a relay near the threshold can gain and lose most of its traffic from one hourly consensus to the next.
  • Guard: requires Fast flag : Guard flag requires having the Fast flag first
    Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports.
  • 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: 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 – 280.0 Mbit/s). gabelmoo measured this relay at 8.0 Kbit/s. dizum, longclaw and maatuska used the relay-reported 1.6 Mbit/s. dannenberg and moria1 counted this relay as 0 (no measurement, relay-reported bandwidth ignored).
    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: Time Known below threshold : Time Known 3.5 days is below 8 days requirement (4.5 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 Fast flag : HSDir flag requires having the Fast flag first
    Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports.
  • 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.
  • 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.
Notes:

Connectivity and Location

Addresses
OR Address
tor-exit-1.allium.observer
107.189.8.181:443
[2605:6400:30:f49b:e2ee:34f8:c854:6f63]:443
Reachability (Directory Authorities)
IPv4
6/9
IPv6
5/8 (1 don't test)
Location
Country
Luxembourg Luxembourg
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS53667
AS Name
FranTech Solutions (BGP.tools)
AS Rarity
Emerging (score: 1/5, 0.78% consensus weight, 53 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Exit
Eligible Flags (4): Running: 6/9 | Valid: 6/9 | V2Dir: 6/9 | Fast: 3/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 6/9
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (6/9 DA) 6/9 authorities reached relay ≥5/9 DA ORPort reachable
IPv6 Reachability Meets (5/8 DA) 5/8 tested authorities reached relay ≥5/8 tested (majority) (≥5/8 DA)
Valid Descriptor Meets (6/9 DA) 6/9 authorities assigned Valid Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir DirPort Available Meets (6/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Below (3/9 DA) 8.0 Kbit/s (1 DA measured)
1.6 Mbit/s (3 DA relay-reported)
0 bit/s (2 DA unmeasured, counted as 0)		 ≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (0/9 DA) Median: 1.9d (0/9 DA above threshold)
Min/Max: 0.0d / 3.5d (6/9 DA, Voting / Total Eligible)		 ≥5.2d - 10.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8884.5d
Uptime Below (0/9 DA) 0.5d (R) ≥3.4d - 3.4d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (3/9 DA) 3/9 DA assigned Fast
8.0 Kbit/s (1 DA measured)
1.6 Mbit/s (3 DA relay-reported)
0 bit/s (2 DA unmeasured, counted as 0)		 ≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (0/9 DA) 0/9 DA assigned Stable ≥5.2d - 10.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8884.5d
Prereq: V2Dir Meets (6/9 DA) 6/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (6/9 DA) Majority: 100.0% (6/9 DA) ≥98.0% (≥5/9 DA)
Time Known Below (2/9 DA) Median: 1.6d (0/9 DA above threshold)
Min/Max: 0.0d / 3.5d (6/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Below (3/9 DA) 3/9 DA assigned Fast
8.0 Kbit/s (1 DA measured)
1.6 Mbit/s (3 DA relay-reported)
0 bit/s (2 DA unmeasured, counted as 0)		 ≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (0/9 DA) 0/9 DA assigned Stable ≥5.2d - 10.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8884.5d
Prereq: V2Dir Meets (6/9 DA) 6/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (6/9 DA) Majority: 100.0% (6/9 DA) ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 6.4 more days) Median: 1.6d (0/9 DA above threshold)
Min/Max: 0.0d / 3.5d (6/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 8.0 Kbit/s (1 DA measured)
1.6 Mbit/s (3 DA relay-reported)
0 bit/s (2 DA unmeasured, counted as 0)		 ≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-280.0 Mbit/s) (≥5/9 DA)
Exit Exit Policy Meets (6/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-10-12 15:45:07).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
1.56 Mbit/s
Advertised Bandwidth
1.56 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
N/A
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-10-12 15:45:07

Measured By
1/7 Bandwidth Authorities
Not measured by: bastet, dannenberg, faravahar, longclaw, moria1, tor26
Consensus Weight
160.0 Kbit/s (Unmeasured)
Measured Min / Max
8.0 Kbit/s / 8.0 Kbit/s
Network Participation: Consensus Weight: 0.0000% of network (3th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0000% (1th pctl)

Uptime and Stability

Uptime Metrics
Current Status
UP 12h 39m 39s ago
Overall Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
N/A
Hibernating
No
Timestamps
First Seen
2h 15m 40s ago (2026-10-12 14:00:00)
Last Seen
1h 15m 40s ago (2026-10-12 15:00:00)
Last Restarted
12h 39m 39s ago (2026-10-12 03:36:01)
Last Changed Address
2026-10-12 14:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-10-12 08:00 UTC

AROI Domain (?)
allium.observer
Operator Validation
Validated (1/2 relays)
This Relay
Unvalidated
Error: Not yet processed by validator (relay may be new)
Contact
email:a78i2efsewr0neeknk[]proton.me url:allium.observer proof:dns-familyid-ed25519 abuse:a78i2efsewr0neeknk[]proton.me ciissversion:3 hoster:buyvm.net cost:8.5USD uplinkbw:1000 memory:2000 cpu:1 virtualization:kvm xmr:82sdVXSFUJcici5mPxoAZB6fSpJP5mW2FEiJfu7jbShUDCiyRNfAJ6ZPdmpDgEj8mFVwHqSgXRK6LDs1JMRazaQuVjtPbEk os:debian/13 tls:openssl aesni:y autoupdate:y confmgmt:ansible dnslocation:local dnsqname:y dnssec:y dnslocalrootzone:y trafficacct:unmetered
Family Configuration
Family Support
Happy Families (2) — Has family-cert in server descriptor (guide)
Happy Families (family-cert)
Effective Members: 2 
31EF78B9019D61CF259B223DB9F80940994EDA34
EF85B8F53A394B7BD79698D2FC01171FDD96C823 (this relay)
MyFamily (legacy declarations) — none

Software and Version

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

Exit Health & Policy

DNS Health
Status
Not Tested
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
reject: 
  25
  465
  587
IPv6 Exit Policy Summary
reject: 
  25
  465
  587
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 107.189.8.181:*
reject *:25
reject *:465
reject *:587
accept *:*

Last fetch was at Mon, 12 Oct 2026 16:15:39 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-10-12 15:45: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 (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) No — — — Y No — — — — — — — — — — — —
dannenberg (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 0 bit/s (U) | 816.0 Kbit/s 0 bit/s (U) | 280.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 3.5d | 8d 3.5d | 5.2d 0.5d | 3.4d 100.0% | 98.0% 3.5d | 1.0d 2026-10-12 11:53:52 1.6 Mbit/s (R)
dizum (NL) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Exit 1.6 Mbit/s (R) | 816.0 Kbit/s 1.6 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 3.5d | 8d 3.5d | 10.9d 0.5d | 3.4d 100.0% | 98.0% 3.5d | 1.0d 2026-10-12 11:53:52 1.6 Mbit/s (R)
faravahar (US) No — — — Y No — — — — — — — — — — — —
gabelmoo (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 8.0 Kbit/s (M) | 816.0 Kbit/s 8.0 Kbit/s (M) | 264.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 10.8d 0.5d | 3.4d 100.0% | 98.0% 0.1d | 1.0d 2026-10-12 11:53:52 1.6 Mbit/s (R)
longclaw (US) Yes Yes Yes — Y Yes — Running, Valid, V2Dir, Fast, Exit 1.6 Mbit/s (R) | 816.0 Kbit/s 1.6 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.0d | 8d 0.0d | 11.2d 0.5d | 3.4d 100.0% | 98.0% 0.0d | 1.0d 2026-10-12 11:53:52 1.6 Mbit/s (R)
maatuska (SE) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Exit 1.6 Mbit/s (R) | 816.0 Kbit/s 1.6 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.3d | 8d 0.3d | 10.5d 0.5d | 3.4d 100.0% | 98.0% 0.3d | 1.0d 2026-10-12 11:53:52 1.6 Mbit/s (R)
moria1 (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 0 bit/s (U) | 8.4 Mbit/s 0 bit/s (U) | 200.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 2.9d | 8d 3.5d | 8884.5d 0.5d | 3.4d 100.0% | 98.0% 2.9d | 9.8d 2026-10-12 11:53:52 1.6 Mbit/s (R)
tor26 (AT) No — — — Y No — — — — — — — — — — — —

— = 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.