View Relay "SaltyCookies"
Fingerprint: 12F3369E046656A3266B834DA7C7CDBE0B59F8E0 |
Family: 1 relay
|
Operator <saltycookies-operator proton me> |
AS44925
|
Iceland
|
Linux
- Consensus
- In Consensus (9/9 Directory Auths)
- DNS Health
- Healthy (17.1s, 71st percentile) (via exitdnshealth.1aeo.com)
- BW Verified
- 5/7 BW Auths Measured 10 Mbit/s Median
- Stability
- Not Overloaded | UP 4d 10h 45m ago
- Reachability
- IPv4: 9/9 | v6: None configured(Directory Auths)
- BW Weight
- 0.00% of Network | 24 Mbit/s Observed By Relay
- Version
- 0.4.9.15 Recommended
Issues Detected:
-
Guard: WFU below threshold
: 0/9 authorities meet guard-wfu (≥98%; dizum: ≥97.997%; 5 needed). bastet, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 measured 45.5%–53.7%.
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: 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 becauseDirCache 0is set in torrc.
Suggestion: RemoveDirCache 0from torrc (DirCache is enabled by default in Tor ≥0.3.3). Restart Tor and verify the descriptor includestunnelled-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.
Addresses
- OR Address
- 185.112.146.167:443
- Exit Address
- 185.112.146.167
Reachability (Directory Authorities)
- IPv4
- 9/9
- IPv6
- None configured
Location
- Country
-
Iceland
- Interactive Map
- View in RouteFluxMap
Eligible Flags (6):
Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 9/9 | HSDir: 0/9 | Guard: 0/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 |
| 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) | 8.0 Mbit/s – 23.2 Mbit/s (5 DA measured) 16.8 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 (3/9 DA) | Median: 6.8d (1/9 DA above threshold) Min/Max: 3.8d / 3100.3d (9/9 DA, Voting / Total Eligible) |
≥2.5d - 9.9d (varies) (≥5/9 DA) [Stricter] moria1: ≥7511.4d |
| Uptime | Below (0/9 DA) | 4.4d (R) | ≥5.6d - 5.6d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Meets (9/9 DA) | 9/9 DA assigned Fast 8.0 Mbit/s – 23.2 Mbit/s (5 DA measured) 16.8 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 (9/9 DA) | 9/9 DA assigned Stable | ≥2.5d - 9.9d (varies) (≥5/9 DA) [Stricter] moria1: ≥7511.4d |
|
| Prereq: V2Dir | Below (0/9 DA) | 0/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| Uptime | Meets (9/9 DA) | 4.4d (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.9d Time Known |
|
| Guard | Prereq: Fast | Meets (9/9 DA) | 9/9 DA assigned Fast 8.0 Mbit/s – 23.2 Mbit/s (5 DA measured) 16.8 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 (9/9 DA) | 9/9 DA assigned Stable | ≥2.5d - 9.9d (varies) (≥5/9 DA) [Stricter] moria1: ≥7511.4d |
|
| Prereq: V2Dir | Below (0/9 DA) | 0/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Below (0/9 DA) | Median: 48.4% (0/9 DA above threshold) Min/Max: 45.5% / 53.7% (9/9 DA, Voting / Total Eligible) |
≥98%; dizum: ≥97.997% (≥5/9 DA) | |
| Time Known | Meets (9/9 DA) | Median: 16.6d (9/9 DA above threshold) Min/Max: 9.9d / 18.5d (9/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Partial (6/9 DA) | 8.0 Mbit/s – 23.2 Mbit/s (5 DA measured) 16.8 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-05 09:45:06).
Capacity (Relay Reported)
- Observed Bandwidth
- 24.95 Mbit/s
- Advertised Bandwidth
- 16.78 Mbit/s
- Rate Limit
- 16.78 Mbit/s
- Burst Limit
- 41.94 Mbit/s
- Total Data
- 423 GB (1 month)
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-05 09:45:06
- Measured By
-
5/7
Bandwidth Authorities
Not measured by: faravahar, longclaw - Consensus Weight
- 10.4 Mbit/s (median of 5 measurements)
- Measured Min / Max
- 8.0 Mbit/s / 23.2 Mbit/s
- Deviation
- 15.2 Mbit/s [Warning] High variation
Network Participation:
Consensus Weight:
0.0007% of network
(17th pctl)
|
Guard:
N/A |
Middle:
N/A |
Exit:
0.0021% (3th pctl)
History
Uptime Metrics
- Current Status
- UP 4d 10h 45m 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
- 4d 9h 45m ago (2026-11-01 01:00:00)
- Last Seen
- 1h 45m 10s ago (2026-11-05 09:00:00)
- Last Restarted
- 4d 10h 45m ago (2026-11-01 00:00:00)
- Last Changed Address
- 2026-11-01 01:00:00
Overload Status:
Not Overloaded — No overload conditions reported.
Evaluated 2026-11-05 10:45 UTC. /details snapshot 2026-11-05 09:00:00 UTC (cached 13s ago). /bandwidth snapshot 2026-11-05 08:00:00 UTC (cached 1h 29m 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-05 01:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- Operator <saltycookies-operator proton me>
Family Configuration
- Family Support
- None — No family membership configured
Happy Families (family-cert)
- Effective Members: 0
- none
MyFamily (legacy declarations)
- Effective Member: 1
12F3369E046656A3266B834DA7C7CDBE0B59F8E0 (this relay)
- Alleged Members: 0
- none
- Indirect Members: 0
- none
DNS Health
- Status
- Healthy (avg. 17.1s, 71st percentile)
- Query Domain
38be02e097b944ed8388702884004ba9.12f3369e.tor.exit.validator.1aeo.com- DNS Result
-
Resolved to
64.65.4.1 - Upstream Resolver
-
Not enough data
Local AS 67%, Local /22 33% (~22 estimated queries) - Cross-Validation
- 4/4 instances succeeded
- First Hop
- londonondatrack (US) 3E0FFFEC0B0FB54282F24607BCBE03EAB81F1907
- Exit Address Used
185.112.146.167- Per-Instance Results
-
Cross Validation Attempt 1: Success, 16.5s (cv1_w1) Cross Validation Attempt 2: Success, 19.1s (cv2_w1) Cross Validation Attempt 3: Success, 16.7s (cv3_w1) Cross Validation Attempt 4: Success, 16.1s (cv4_w1)
Tested: 2026-11-05 08:05:24 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 20-21 43 53 80 110 143 220 443 873 989-993 995 1194 1293 3690 4321 5222-5223 5228 9418 11371 64738
IPv6 Exit Policy Summary
NoneFull 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 185.112.146.167:* accept *:20-21 accept *:43 accept *:53 accept *:80 accept *:110 accept *:143 accept *:220 accept *:443 accept *:873 accept *:989-990 accept *:991 accept *:992 accept *:993 accept *:995 accept *:1194 accept *:1293 accept *:3690 accept *:4321 accept *:5222-5223 accept *:5228 accept *:9418 accept *:11371 accept *:64738 reject *:*
Last fetch was at Thu, 05 Nov 2026 10:45:09 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-05 09:45:06).
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 | 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 | Running, Valid, Fast, Stable, Exit | 22.4 Mbit/s (M) | 816.0 Kbit/s | 22.4 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s | 45.6% | 98% | 16.6d | 8d | 6.4d | 9.0d | 4.4d | 5.9d | 2026-11-05 00:23:41 | 22.4 Mbit/s (M) |
| dannenberg (DE) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, Fast, Stable, Exit | 8.0 Mbit/s (M) | 816.0 Kbit/s | 8.0 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s | 48.4% | 98% | 16.6d | 8d | 6.8d | 9.9d | 4.4d | 5.6d | 2026-11-05 00:23:41 | 8.0 Mbit/s (M) |
| dizum (NL) | Yes | Yes | Yes | — | N | Yes | Running, Valid, Fast, Stable, Exit | 16.8 Mbit/s (R) | 816.0 Kbit/s | 16.8 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 48.7% | 98% | 17.6d | 8d | 7.3d | 7.1d | 4.4d | 5.6d | 2026-11-05 00:23:41 | 16.8 Mbit/s (R) |
| faravahar (US) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, Fast, Stable, Exit | 16.8 Mbit/s (R) | 816.0 Kbit/s | 16.8 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 48.4% | 98% | 16.6d | 8d | 6.8d | 6.8d | 4.4d | 5.6d | 2026-11-05 00:23:41 | 16.8 Mbit/s (R) |
| gabelmoo (DE) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, Fast, Stable, Exit | 10.4 Mbit/s (M) | 816.0 Kbit/s | 10.4 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s | 46.7% | 98% | 16.9d | 8d | 6.7d | 11.3d | 4.4d | 5.6d | 2026-11-05 00:23:41 | 10.4 Mbit/s (M) |
| longclaw (US) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, Fast, Stable, Exit | 16.8 Mbit/s (R) | 816.0 Kbit/s | 16.8 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 53.4% | 98% | 18.4d | 8d | 8.4d | 11.5d | 4.4d | 5.6d | 2026-11-05 00:23:41 | 16.8 Mbit/s (R) |
| maatuska (SE) | Yes | Yes | Yes | — | N | Yes | Running, Valid, Fast, Stable, Exit | 16.8 Mbit/s (R) | 816.0 Kbit/s | 16.8 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 45.5% | 98% | 15.8d | 8d | 3.8d | 2.5d | 4.4d | 5.6d | 2026-11-05 00:23:41 | 16.8 Mbit/s (R) |
| moria1 (US) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, Fast, Stable, Exit | 23.2 Mbit/s (M) | 8.4 Mbit/s | 23.2 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s | 50.4% | 98% | 9.9d | 8d | 3100.3d | 7511.4d | 4.4d | 5.6d | 2026-11-05 00:23:41 | 23.2 Mbit/s (M) |
| tor26 (AT) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, Fast, Stable, Exit | 10.4 Mbit/s (M) | 816.0 Kbit/s | 10.4 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s | 53.7% | 98% | 18.5d | 8d | 8.5d | 11.3d | 4.4d | 5.6d | 2026-11-05 00:23:41 | 10.4 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.