View Relay "SieNCoAd"
Fingerprint: 31EF78B9019D61CF259B223DB9F80940994EDA34 |
Operator: allium.observer v3
(2 relays)
✓ Validated
|
Family: 2 relays
|
email:a78i2efsewr0neeknk[]proton.me... |
AS60404
|
Netherlands
|
Linux
- Consensus
- In Consensus (9/9 Directory Auths)
- DNS Health
- Healthy (13.1s, 26th percentile) (via exitdnshealth.1aeo.com)
- BW Verified
- 5/7 BW Auths Measured 216 Mbit/s Median
- Stability
- Not Overloaded | UP 17h 7m 40s ago | UP 99% (1M)
- Reachability
- IPv4: 9/9 | v6: 8/8(Directory Auths)
- BW Weight
- 0.01% of Network | 152 Mbit/s Observed By Relay
- Version
- 0.4.9.15 Recommended
Issues Detected:
-
HSDir: uptime below 96 hours
: Only 0/9 authorities voted HSDir, though this relay has Fast, Stable and V2Dir
Suggestion: HSDir needs 96 hours of uptime as each authority sees it (MinUptimeHidServDirectoryV2): the time since your relay restarted, or since that authority last failed to reach it if that is shorter. Keep the relay running and reachable. -
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.
Notes:
- Guard: WFU near threshold: Weighted Fractional Uptime is just above the Guard bar at maatuska (98.0%, need ≥98%) and just under the Guard bar at dizum (97.7%, need ≥97.84099999999999%). Recent downtime weighs more than older downtime. Avoid restarts while it is this close; a short outage can drop the Guard flag.
Suggestion: Recent downtime weighs more than older downtime. Minimize restarts, use systemd Restart=always, and watch for OOM kills until each authority has more room above its own guard-wfu. - Guard: bandwidth near threshold: Bandwidth counted for Guard is just under the Guard bar at moria1 (16.0 Mbit/s, need ≥16.8 Mbit/s). The bar is the lower of AuthDirGuardBWGuarantee and that authority's top 25%. A dip in the bandwidth it counts can drop the Guard flag.
Suggestion: The bandwidth that counts is that authority's measurement when it has one, otherwise the relay-reported rate. Keep it above the lower of AuthDirGuardBWGuarantee (2 MB by default) and that authority's top 25%.
Addresses
- OR Address
-
tor-exit-3.allium.observer
5.255.101.10:443
[2a04:52c0:106:394:3218:d72f:49fa:8738]:443 - Exit Address
- 5.255.101.10
Reachability (Directory Authorities)
- IPv4
- 9/9
- IPv6
- 8/8 (1 don't test)
Location
- Country
-
Netherlands
- Interactive Map
- View in RouteFluxMap
Eligible Flags (7):
Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 7/9 | HSDir: 0/9 | Guard: 5/9 | Exit: 9/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) | 14.4 Mbit/s – 312.0 Mbit/s (5 DA measured) 80.0 Mbit/s (4 DA relay-reported) |
≥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 (2/9 DA) | Median: 8.0d (1/9 DA above threshold) Min/Max: 2.4d / 10588.9d (9/9 DA, Voting / Total Eligible) |
≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d |
| Uptime | Below (0/9 DA) | 0.7d (R) | ≥5.2d - 5.3d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Meets (9/9 DA) | 9/9 DA assigned Fast 14.4 Mbit/s – 312.0 Mbit/s (5 DA measured) 80.0 Mbit/s (4 DA relay-reported) |
≥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 (7/9 DA) | 7/9 DA assigned Stable | ≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d |
|
| Prereq: V2Dir | Meets (9/9 DA) | 9/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| Uptime | Below (0/9 DA) | 0.7d (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.8d Time Known |
|
| Guard | Prereq: Fast | Meets (9/9 DA) | 9/9 DA assigned Fast 14.4 Mbit/s – 312.0 Mbit/s (5 DA measured) 80.0 Mbit/s (4 DA relay-reported) |
≥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 (7/9 DA) | 7/9 DA assigned Stable | ≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d |
|
| Prereq: V2Dir | Meets (9/9 DA) | 9/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Partial (8/9 DA) | Median: 99.2% (8/9 DA above threshold) Min/Max: 97.7% / 99.6% (9/9 DA, Voting / Total Eligible) |
≥98%; dizum: ≥97.84099999999999% (≥5/9 DA) | |
| Time Known | Meets (9/9 DA) | Median: 14.6d (9/9 DA above threshold) Min/Max: 9.7d / 18.7d (9/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Partial (7/9 DA) | 14.4 Mbit/s – 312.0 Mbit/s (5 DA measured) 80.0 Mbit/s (4 DA relay-reported) |
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-272.0 Mbit/s) (≥5/9 DA) | |
| Exit | Exit Policy | Meets (9/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-11-04 12:45:10).
Capacity (Relay Reported)
- Observed Bandwidth
- 152.28 Mbit/s
- Advertised Bandwidth
- 152.28 Mbit/s
- Rate Limit
- 251.66 Mbit/s
- Burst Limit
- 503.32 Mbit/s
- Total Data
-
990 TB
(5 years)
1mo: 28 TB | 6mo: 162 TB | 1y: 398 TB | 5y: 990 TB
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-04 12:45:10
- Measured By
-
5/7
Bandwidth Authorities
Not measured by: faravahar, longclaw - Consensus Weight
- 216.0 Mbit/s (median of 5 measurements)
- Measured Min / Max
- 14.4 Mbit/s / 312.0 Mbit/s
- Deviation
- 297.6 Mbit/s [Warning] High variation
Network Participation:
Consensus Weight:
0.0136% of network
(73th pctl)
|
Guard:
N/A |
Middle:
N/A |
Exit:
0.0444% (68th pctl)
History
Uptime Metrics
- Current Status
- UP 17h 7m 40s ago
- Overall Uptime (1M/6M/1Y/5Y)
- 99.1%/99.6%/97.8%/73.1%
- Flag Uptime (1M/6M/1Y/5Y)
- Matches Overall Uptime (99.1%/99.6%/97.8%/73.1%)
- Hibernating
- No
Timestamps
- First Seen
- 3y 12mo 1d ago (2022-11-09 00:00:00)
- Last Seen
- 2h 15m 37s ago (2026-11-04 11:00:00)
- Last Restarted
- 17h 7m 40s ago (2026-11-03 20:07:57)
- Last Changed Address
- 2026-09-26 11:00:00
Overload Status:
Not Overloaded — No overload conditions reported.
Evaluated 2026-11-04 13:15 UTC. /details snapshot 2026-11-04 11:00:00 UTC (cached 19s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 5h 30m ago).
General Overload (from /details)
- Status
- No general overload report in available data
File Descriptor Exhaustion (from /bandwidth)
- Status
- No file-descriptor exhaustion report in available data
Rate Limits (from /bandwidth)
- Status
- No rate-limit report in available data
- Rate Limit
- —
- Burst Limit
- —
- Write counter
- —
- Read counter
- —
About these reports and MetricsPort
Allium’s eligibility windows are applied to the reported timestamps: 72 hours for general overload and file-descriptor exhaustion, 24 hours for a rate-limit hit. A report at the cutoff is historical. An older report can remain visible after Onionoo or Allium’s cache still has it. The cutoff does not prove the relay recovered at that moment. Allium caches the bandwidth document for 12 hours by default. The snapshot time is when Onionoo published that document. It is not the relay’s event time, and it is not necessarily the extra-info publication time. Cache age is how old Allium’s copy is.
MetricsPort counters are cumulative. Compare samples, and account for process restarts. A nonzero total alone does not show ongoing activity. Gauges describe current values. An unavailable metric is unknown, not zero. Allium does not have this relay’s MetricsPort readings and does not invent them.
The port below is an example for an endpoint you have already configured. MetricsPort must be enabled with restricted access and must not be exposed publicly. Setup stays in the Tor overload troubleshooting guide.
curl http://127.0.0.1:9035/metrics
History
Operator Identity
Source: AROI Validation API — 2026-11-04 04:00 UTC
- AROI Domain (?)
- allium.observer
- Operator Validation
- Validated (2/2 relays)
- This Relay
- Validated (dns-familyid-ed25519)
- Contact
- email:a78i2efsewr0neeknk[]proton.me url:allium.observer proof:dns-familyid-ed25519 abuse:a78i2efsewr0neeknk[]proton.me ciissversion:3 hoster:LiteServer cost:3.75EUR uplinkbw:1000 memory:2048 cpu:2 virtualization:kvm xmr:82sdVXSFUJcici5mPxoAZB6fSpJP5mW2FEiJfu7jbShUDCiyRNfAJ6ZPdmpDgEj8mFVwHqSgXRK6LDs1JMRazaQuVjtPbEk os:debian/13 tls:openssl aesni:y autoupdate:y confmgmt:manual dnslocation:local dnsqname:y dnssec:y dnslocalrootzone:y trafficacct:12288
Family Configuration
- Family Support
- Happy Families (2) — Has family-cert in server descriptor (guide) | View Full Family (2)
Happy Families (family-cert)
- Effective Members: 2
31EF78B9019D61CF259B223DB9F80940994EDA34 (this relay) EF85B8F53A394B7BD79698D2FC01171FDD96C823
MyFamily (legacy declarations) — none
DNS Health
- Status
- Healthy (avg. 13.1s, 26th percentile)
- Query Domain
4c688bea018742ea92e90cddffc2eb05.31ef78b9.tor.exit.validator.1aeo.com- DNS Result
-
Resolved to
64.65.4.1 - Upstream Resolver
-
Other
Other 100% (~147 estimated queries) - Cross-Validation
- 3/3 instances succeeded
- First Hop
- htx02 (FR) A07D56AC8FF3B7539B314222B658B1190AB66514
- Exit Address Used
5.255.101.10- Per-Instance Results
-
Cross Validation Attempt 1: Success, 7.4s (cv1_w1) Cross Validation Attempt 2: Success, 16.5s (cv2_w1) Cross Validation Attempt 3: Success, 15.5s (cv3_w1)
Tested: 2026-11-03 20:05:21 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
reject: 22 25 465 587 993 6660-6667 6697
IPv6 Exit Policy Summary
reject: 22 25 465 587 993 6660-6667 6697
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 5.255.101.10:* reject *:22 reject *:25 reject *:465 reject *:587 reject *:993 reject *:6660-6667 reject *:6697 accept *:*
Last fetch was at Wed, 04 Nov 2026 13:15:37 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-04 12:45:10).
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) | Desc Published | Cons Wt (Authority) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| bastet (US) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Exit | 14.4 Mbit/s (M) | 816.0 Kbit/s | 14.4 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 98.9% | 98% | 12.9d | 8d | 4.2d | 8.4d | 0.7d | 5.2d | 2026-11-03 20:07:59 | 14.4 Mbit/s (M) |
| dannenberg (DE) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, Guard, Exit | 216.0 Mbit/s (M) | 816.0 Kbit/s | 216.0 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s | 99.5% | 98% | 18.1d | 8d | 8.0d | 9.3d | 0.7d | 5.3d | 2026-11-03 20:07:59 | 216.0 Mbit/s (M) |
| dizum (NL) | Yes | Yes | Yes | — | N | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, Exit | 80.0 Mbit/s (R) | 816.0 Kbit/s | 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 97.7% | 98% | 14.1d | 8d | 5.5d | 6.7d | 0.7d | 5.3d | 2026-11-03 20:07:59 | 80.0 Mbit/s (R) |
| faravahar (US) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Exit | 80.0 Mbit/s (R) | 816.0 Kbit/s | 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 99.2% | 98% | 13.9d | 8d | 4.1d | 6.5d | 0.7d | 5.3d | 2026-11-03 20:07:59 | 80.0 Mbit/s (R) |
| gabelmoo (DE) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, Guard, Exit | 312.0 Mbit/s (M) | 816.0 Kbit/s | 312.0 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s | 99.5% | 98% | 17.6d | 8d | 8.6d | 10.8d | 0.7d | 5.3d | 2026-11-03 20:07:59 | 312.0 Mbit/s (M) |
| longclaw (US) | Yes | Yes | Yes | — | Y | Yes | N/T | Running, Valid, V2Dir, Fast, Stable, Guard, Exit | 80.0 Mbit/s (R) | 816.0 Kbit/s | 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 99.6% | 98% | 18.7d | 8d | 8.9d | 10.9d | 0.7d | 5.3d | 2026-11-03 20:07:59 | 80.0 Mbit/s (R) |
| maatuska (SE) | Yes | Yes | Yes | — | N | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, Guard, Exit | 80.0 Mbit/s (R) | 816.0 Kbit/s | 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 98.0% | 98% | 14.6d | 8d | 2.4d | 2.4d | 0.7d | 5.3d | 2026-11-03 20:07:59 | 80.0 Mbit/s (R) |
| moria1 (US) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, Exit | 16.0 Mbit/s (M) | 8.4 Mbit/s | 16.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 99.1% | 98% | 9.7d | 8d | 10588.9d | 7607.5d | 0.7d | 5.3d | 2026-11-03 20:07:59 | 16.0 Mbit/s (M) |
| tor26 (AT) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, Guard, Exit | 232.0 Mbit/s (M) | 816.0 Kbit/s | 232.0 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s | 99.5% | 98% | 18.6d | 8d | 8.3d | 10.6d | 0.7d | 5.3d | 2026-11-03 20:07:59 | 232.0 Mbit/s (M) |
N/T = this authority does not test IPv6 • — = not in this vote • 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 (
Relay-reported (R) = The bandwidth your relay advertises: the lower of its observed bandwidth and its rate limit, capped at 10 MB/s (
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.
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.
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.