View Relay "SlugnetExitRelay01"
Fingerprint: 11A96B0A8A912807A43940C450CA550E4CB92F51 |
Family: 2 relays
|
cedabcbc08fbadd18668af818111c31bc6af8... |
AS40663
|
United States of America
|
Linux
- Consensus
- In Consensus (9/9 Directory Auths)
- DNS Health
- Healthy (14.5s, 42nd percentile) (via exitdnshealth.1aeo.com)
- BW Verified
- 5/7 BW Auths Measured 64 Mbit/s Median
- Stability
- Not Overloaded | UP 2d 14h 57m ago | UP 91% (1M)
- Reachability
- IPv4: 9/9 | v6: None configured(Directory Auths)
- BW Weight
- 0.00% of Network | 59 Mbit/s Observed By Relay
- Version
- 0.4.9.14 Not Recommended
Issues Detected:
-
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
: 4/9 authorities meet guard-wfu (≥98%; dizum: ≥97.84099999999999%; 5 needed). bastet, dannenberg, dizum, faravahar and maatuska measured 96.6%–97.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. -
Not eligible for Stable flag
: 0/9 authorities meet Stable (uptime or MTBF at or above their own median; 5 needed). bastet, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 do not.
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. -
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. -
Tor version not recommended
: Running Tor version 0.4.9.14 which is not on the recommended list.
Suggestion: Update to the latest stable Tor version. Outdated versions may have security vulnerabilities and could eventually be rejected by the network. See torproject.org/download for latest releases.
Addresses
- OR Address
-
sn-tor-exit01.slugnet.org
23.137.253.113:443 - Exit Address
- 23.137.253.113
Reachability (Directory Authorities)
- IPv4
- 9/9
- IPv6
- None configured
Location
- Country
-
United States of America
- Interactive Map
- View in RouteFluxMap
Eligible Flags (5):
Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 4/9 | HSDir: 1/9 | Guard: 4/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 | Meets (9/9 DA) | Tunnelled: Yes (no DirPort) (R) | Tunnelled directory via ORPort or DirPort (≥5/9 DA) |
| Fast | Speed | Meets (9/9 DA) | 49.6 Mbit/s – 392.0 Mbit/s (5 DA measured) 59.4 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 (0/9 DA) | Median: 4.7d (1/9 DA above threshold) Min/Max: 1.7d / 2676.6d (9/9 DA, Voting / Total Eligible) |
≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d |
| Uptime | Below (0/9 DA) | 2.6d (R) | ≥5.2d - 5.3d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Meets (9/9 DA) | 9/9 DA assigned Fast 49.6 Mbit/s – 392.0 Mbit/s (5 DA measured) 59.4 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 | Below (4/9 DA) | 4/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 (1/9 DA) | 2.6d (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 49.6 Mbit/s – 392.0 Mbit/s (5 DA measured) 59.4 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 | Below (4/9 DA) | 4/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 | Below (4/9 DA) | Median: 97.7% (4/9 DA above threshold) Min/Max: 96.6% / 98.6% (9/9 DA, Voting / Total Eligible) |
≥98%; dizum: ≥97.84099999999999% (≥5/9 DA) | |
| Time Known | Meets (9/9 DA) | Median: 13.9d (9/9 DA above threshold) Min/Max: 9.9d / 15.8d (9/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Meets (9/9 DA) | 49.6 Mbit/s – 392.0 Mbit/s (5 DA measured) 59.4 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
- 59.38 Mbit/s
- Advertised Bandwidth
- 59.38 Mbit/s
- Rate Limit
- 838.86 Mbit/s
- Burst Limit
- 1.68 Gbit/s
- Total Data
-
52 TB
(5 years)
1mo: 4.4 TB | 6mo: 25 TB | 1y: 41 TB | 5y: 52 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
- 64.8 Mbit/s (median of 5 measurements)
- Measured Min / Max
- 49.6 Mbit/s / 392.0 Mbit/s
- Deviation
- 342.4 Mbit/s [Warning] High variation
Network Participation:
Consensus Weight:
0.0038% of network
(44th pctl)
|
Guard:
N/A |
Middle:
N/A |
Exit:
0.0125% (24th pctl)
History
Uptime Metrics
- Current Status
- UP 2d 14h 57m ago
- Overall Uptime (1M/6M/1Y/5Y)
- 91.7%/89.6%/76.3%/74.4%
- Flag Uptime (1M/6M/1Y/5Y)
- Matches Overall Uptime (91.7%/89.6%/76.3%/74.4%)
- Hibernating
- No
Timestamps
- First Seen
- 1y 2mo 6d ago (2025-08-30 06:00:00)
- Last Seen
- 2h 15m 38s ago (2026-11-04 11:00:00)
- Last Restarted
- 2d 14h 57m ago (2026-11-01 22:18:30)
- Last Changed Address
- 2026-04-06 23: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 (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- cedabcbc08fbadd18668af818111c31bc6af8f91 slugnet Operator <operator@slugnet.org>
Family Configuration
- Family Support
- MyFamily Only (2) — Legacy only. Consider migrating to Happy Families. | View Full Family (2)
Happy Families (family-cert)
- Effective Members: 0
- none
MyFamily (legacy declarations)
- Effective Members: 2
10E53D8D001108E3C87B8DE99322D7EA8E2A6A87 11A96B0A8A912807A43940C450CA550E4CB92F51 (this relay)
- Alleged Members: 0
- none
- Indirect Members: 0
- none
- Platform
- Linux — Tor 0.4.9.14 on Linux
- Version
- 0.4.9.14 — Not Recommended
- Version Status
- Obsolete — Update urgently. See torproject.org/download
DNS Health
- Status
- Healthy (avg. 14.5s, 42nd percentile)
- Query Domain
03da3899a7754d169aa2fc12f3abd5d9.11a96b0a.tor.exit.validator.1aeo.com- DNS Result
-
Resolved to
64.65.4.1 - Upstream Resolver
-
Not enough data
Google 100% (~16 estimated queries) - Cross-Validation
- 4/4 instances succeeded
- First Hop
- articolo15 (FR) 0F72C6F221E76C5B07F617E9649D50CD933BD881
- Exit Address Used
23.137.253.113- Per-Instance Results
-
Cross Validation Attempt 1: Success, 13.5s (cv1_w1) Cross Validation Attempt 2: Success, 16.2s (cv2_w1) Cross Validation Attempt 3: Success, 15.3s (cv3_w1) Cross Validation Attempt 4: Success, 12.9s (cv4_w1)
Tested: 2026-11-03 20:05:50 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 20-21 43 53 80-81 443 1080 2082-2083 2222 2323 3000 3128 3478-3497 4083-4085 4200 4244 4444 5000 5222-5223 5228-5230 5280-5281 5353 5938 6400-6401 6660-7000 7890 8000 8008 8080 8082-8083 8090 8232-8233 8332-8333 8443-8444 8448 8888 9000-9001 9050-9051 9100-9102 9332-9333 9998-10000 12320 18080-18081 22555-22556 27146 28380-28381 30303 50001-50002 51235
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 23.137.253.113:* accept *:20-21 accept *:43 accept *:53 accept *:80-81 accept *:443 accept *:5222-5223 accept *:6660-7000 accept *:8008 accept *:2222 accept *:10000 accept *:8443 accept *:2082-2083 accept *:4083-4085 accept *:12320 accept *:9000 accept *:8888 accept *:8090 accept *:8083 accept *:8448 accept *:8082 accept *:8332-8333 accept *:50001-50002 accept *:18080-18081 accept *:9332-9333 accept *:9998-9999 accept *:22555-22556 accept *:8232-8233 accept *:30303 accept *:51235 accept *:3000 accept *:27146 accept *:8000 accept *:4200 accept *:9100-9102 accept *:4444 accept *:28380-28381 accept *:2323 accept *:3478-3497 accept *:5228-5230 accept *:4244 accept *:5280-5281 accept *:1080 accept *:7890 accept *:6400-6401 accept *:5938 accept *:8080 accept *:8444 accept *:3128 accept *:9050-9051 accept *:5353 accept *:5000 accept *:9001 reject *:*
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 | 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, V2Dir, Fast, Exit | 144.0 Mbit/s (M) | 816.0 Kbit/s | 144.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 96.6% | 98% | 12.3d | 8d | 1.9d | 8.4d | 2.6d | 5.2d | 2026-11-04 04:18:36 | 144.0 Mbit/s (M) |
| dannenberg (DE) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, V2Dir, Fast, Exit | 49.6 Mbit/s (M) | 816.0 Kbit/s | 49.6 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s | 96.6% | 98% | 12.5d | 8d | 1.7d | 9.3d | 2.6d | 5.3d | 2026-11-04 04:18:36 | 49.6 Mbit/s (M) |
| dizum (NL) | Yes | Yes | Yes | — | N | Yes | Running, Valid, V2Dir, Fast, Exit | 59.4 Mbit/s (R) | 816.0 Kbit/s | 59.4 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 96.8% | 98% | 15.0d | 8d | 4.7d | 6.7d | 2.6d | 5.3d | 2026-11-04 04:18:36 | 59.4 Mbit/s (R) |
| faravahar (US) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, V2Dir, Fast, Exit | 59.4 Mbit/s (R) | 816.0 Kbit/s | 59.4 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 97.7% | 98% | 12.1d | 8d | 2.8d | 6.5d | 2.6d | 5.3d | 2026-11-04 04:18:36 | 59.4 Mbit/s (R) |
| gabelmoo (DE) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, V2Dir, Fast, Stable, Guard, Exit | 60.8 Mbit/s (M) | 816.0 Kbit/s | 60.8 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s | 98.5% | 98% | 14.5d | 8d | 6.8d | 10.8d | 2.6d | 5.3d | 2026-11-04 04:18:36 | 60.8 Mbit/s (M) |
| longclaw (US) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, V2Dir, Fast, Stable, Guard, Exit | 59.4 Mbit/s (R) | 816.0 Kbit/s | 59.4 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 98.6% | 98% | 15.1d | 8d | 8.6d | 10.9d | 2.6d | 5.3d | 2026-11-04 04:18:36 | 59.4 Mbit/s (R) |
| maatuska (SE) | Yes | Yes | Yes | — | N | Yes | Running, Valid, V2Dir, Fast, Exit | 59.4 Mbit/s (R) | 816.0 Kbit/s | 59.4 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 97.4% | 98% | 13.9d | 8d | 2.2d | 2.4d | 2.6d | 5.3d | 2026-11-04 04:18:36 | 59.4 Mbit/s (R) |
| moria1 (US) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit | 392.0 Mbit/s (M) | 8.4 Mbit/s | 392.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 98.4% | 98% | 9.9d | 8d | 2676.6d | 7607.5d | 2.6d | 5.3d | 2026-11-04 04:18:36 | 392.0 Mbit/s (M) |
| tor26 (AT) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, V2Dir, Fast, Stable, Guard, Exit | 64.8 Mbit/s (M) | 816.0 Kbit/s | 64.8 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s | 98.6% | 98% | 15.8d | 8d | 7.2d | 10.6d | 2.6d | 5.3d | 2026-11-04 04:18:36 | 64.8 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.