View Relay "sartre1"
Fingerprint: 114F6F2A3A6E8AB9AC2BD54B8C5A204C1CA5942B |
Family: 1 relay
|
email:schroedingers_cat[]riseup.net... |
AS200651
|
Finland
|
Linux
- Consensus
- In Consensus (9/9 Directory Auths)
- DNS Health
- Not Tested (via exitdnshealth.1aeo.com)
- BW Verified
- 4/7 BW Auths Measured 216 Mbit/s Median
- Stability
- Not Overloaded | UP 3h 15m 20s ago
- Reachability
- IPv4: 9/9 | v6: 8/8 (Directory Auths)
- BW Weight
- 0.01% of Network | 0 Kbit/s Observed By Relay
- Version
- 0.4.9.11 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: bandwidth below threshold
: 4/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 – 288.0 Mbit/s). dizum, longclaw and maatuska used the relay-reported unknown.
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: WFU below threshold
: Weighted Fractional Uptime 6.2% 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. -
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: 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 -
HSDir: WFU below threshold
: WFU 6.2% 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. -
Tor version not recommended
: Running Tor version 0.4.9.11 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
-
185.246.191.53:9001
[2a06:1700:1:43::efa:fee4]:9001
Reachability (Directory Authorities)
- IPv4
- 9/9
- IPv6
- 8/8 (1 don't test)
Location
- Country
-
Finland
- Interactive Map
- View in RouteFluxMap
Eligible Flags (5):
Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 6/9 | Stable: 1/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 |
| 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 | Below (0/9 DA) | No DirPort, no tunnelled-dir-server (R) | Tunnelled directory via ORPort or DirPort (≥5/9 DA) |
| Fast | Speed | Partial (6/9 DA) | 152.0 Mbit/s – 248.0 Mbit/s (4 DA measured) 0 bit/s (3 DA relay-reported) faravahar, moria1: not published |
≥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.2d (1/9 DA above threshold) Min/Max: 0.2d / 2410.5d (9/9 DA, Voting / Total Eligible) |
≥5.3d - 10.8d (varies) (≥5/9 DA) [Stricter] moria1: ≥9237.3d |
| Uptime | Below (0/9 DA) | 0.1d (R) | ≥3.8d - 3.8d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Meets (6/9 DA) | 6/9 DA assigned Fast 152.0 Mbit/s – 248.0 Mbit/s (4 DA measured) 0 bit/s (3 DA relay-reported) faravahar, moria1: not published |
≥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 (1/9 DA) | 1/9 DA assigned Stable | ≥5.3d - 10.8d (varies) (≥5/9 DA) [Stricter] moria1: ≥9237.3d |
|
| 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: 6.2% (0/9 DA above threshold) Min/Max: 5.0% / 8.8% (9/9 DA, Voting / Total Eligible) |
≥98.0% (≥5/9 DA) | |
| Time Known | Meets (9/9 DA) | Median: 22.6d (9/9 DA above threshold) Min/Max: 10.0d / 22.6d (9/9 DA, Voting / Total Eligible) |
≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.8d |
|
| Guard | Prereq: Fast | Meets (6/9 DA) | 6/9 DA assigned Fast 152.0 Mbit/s – 248.0 Mbit/s (4 DA measured) 0 bit/s (3 DA relay-reported) faravahar, moria1: not published |
≥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 (1/9 DA) | 1/9 DA assigned Stable | ≥5.3d - 10.8d (varies) (≥5/9 DA) [Stricter] moria1: ≥9237.3d |
|
| 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: 6.2% (0/9 DA above threshold) Min/Max: 5.0% / 8.8% (9/9 DA, Voting / Total Eligible) |
≥98% (≥5/9 DA) | |
| Time Known | Meets (9/9 DA) | Median: 22.6d (9/9 DA above threshold) Min/Max: 10.0d / 22.6d (9/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Below (4/9 DA) | 152.0 Mbit/s – 248.0 Mbit/s (4 DA measured) 0 bit/s (3 DA relay-reported) faravahar, moria1: not published |
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-288.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-10-13 02:45:08).
Capacity (Relay Reported)
- Observed Bandwidth
- 0.00 Kbit/s
- Advertised Bandwidth
- Unknown
- 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-13 02:45:08
- Measured By
-
4/7
Bandwidth Authorities
Not measured by: faravahar, longclaw, moria1 - Consensus Weight
- 216.0 Mbit/s (median of 4 measurements)
- Measured Min / Max
- 152.0 Mbit/s / 248.0 Mbit/s
Network Participation:
Consensus Weight:
0.0134% of network
(72th pctl)
|
Guard:
N/A |
Middle:
N/A |
Exit:
0.0429% (68th pctl)
Uptime Metrics
- Current Status
- UP 3h 15m 20s 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 19s ago (2026-10-13 01:00:00)
- Last Seen
- 1h 15m 19s ago (2026-10-13 02:00:00)
- Last Restarted
- 3h 15m 20s ago (2026-10-12 23:59:59)
- Last Changed Address
- 2026-10-13 01:00:00
Overload Status:
Not Overloaded — No overload conditions reported.
Operator Identity
Source: AROI Validation API — 2026-10-12 18:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- email:schroedingers_cat[]riseup.net pgp:4A74E1B84035C1C989D0EA8C4209E0AFB4D47D88 hoster:https://flokinet.is/ dnslocation:local dnsqname:y dnssec:y ciissversion:2
Family Configuration
- Family Support
- None — No family membership configured
Happy Families (family-cert)
- Effective Members: 0
- none
MyFamily (legacy declarations)
- Effective Member: 1
114F6F2A3A6E8AB9AC2BD54B8C5A204C1CA5942B (this relay)
- Alleged Members: 0
- none
- Indirect Members: 0
- none
- Platform
- Linux — Tor 0.4.9.11 on Linux
- Version
- 0.4.9.11 — Not Recommended
- Version Status
- Obsolete — Update urgently. See torproject.org/download
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.246.191.53:* 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 Tue, 13 Oct 2026 03:15:18 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-10-13 02:45:08).
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) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, Fast, Exit | 216.0 Mbit/s (M) | 816.0 Kbit/s | 216.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 6.2% | 98% | 22.6d | 8d | 1.2d | 10.6d | 0.1d | 3.9d | 6.2% | 98.0% | 22.6d | 1.0d | 2026-10-13 00:03:48 | 216.0 Mbit/s (M) |
| dannenberg (DE) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, Fast, Exit | 152.0 Mbit/s (M) | 816.0 Kbit/s | 152.0 Mbit/s (M) | 288.0 Mbit/s OR 16.8 Mbit/s | 5.0% | 98% | 21.2d | 8d | 0.2d | 5.3d | 0.1d | 3.8d | 5.0% | 98.0% | 21.2d | 1.0d | 2026-10-13 00:03:48 | 152.0 Mbit/s (M) |
| dizum (NL) | Yes | Yes | Yes | — | N | Yes | Yes | Running, Valid, Exit | 0 bit/s (R) | 816.0 Kbit/s | 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 6.2% | 98% | 22.5d | 8d | 1.2d | 10.8d | 0.1d | 3.8d | 6.2% | 98.0% | 22.5d | 1.0d | 2026-10-13 00:03:48 | — |
| faravahar (US) | Yes | Yes | Yes | — | Y | Yes | Yes | Valid, Fast, Exit | not published | 816.0 Kbit/s | not published | 288.0 Mbit/s OR 16.8 Mbit/s | 6.2% | 98% | 22.6d | 8d | 1.2d | 11.7d | 0.1d | 3.8d | 6.2% | 98.0% | 22.6d | 1.0d | 2026-10-13 00:03:48 | — |
| gabelmoo (DE) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, Fast, Exit | 248.0 Mbit/s (M) | 816.0 Kbit/s | 248.0 Mbit/s (M) | 264.0 Mbit/s OR 16.8 Mbit/s | 6.2% | 98% | 22.6d | 8d | 1.2d | 10.6d | 0.1d | 3.8d | 6.2% | 98.0% | 22.6d | 1.0d | 2026-10-13 00:03:48 | 248.0 Mbit/s (M) |
| longclaw (US) | Yes | Yes | Yes | — | Y | Yes | — | Running, Valid, Exit | 0 bit/s (R) | 816.0 Kbit/s | 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 6.2% | 98% | 22.6d | 8d | 1.2d | 11.1d | 0.1d | 3.8d | 6.2% | 98.0% | 22.6d | 1.0d | 2026-10-13 00:03:48 | — |
| maatuska (SE) | Yes | Yes | Yes | — | N | Yes | Yes | Running, Valid, Exit | 0 bit/s (R) | 816.0 Kbit/s | 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 6.0% | 98% | 22.5d | 8d | 1.2d | 10.5d | 0.1d | 3.8d | 6.0% | 98.0% | 22.5d | 1.0d | 2026-10-13 00:03:48 | — |
| moria1 (US) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, Fast, Stable, Exit | not published | 8.4 Mbit/s | not published | 208.0 Mbit/s OR 16.8 Mbit/s | 8.8% | 98% | 10.0d | 8d | 2410.5d | 9237.3d | 0.1d | 3.8d | 8.8% | 98.0% | 10.0d | 9.8d | 2026-10-13 00:03:48 | — |
| tor26 (AT) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, Fast, Exit | 216.0 Mbit/s (M) | 816.0 Kbit/s | 216.0 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s | 6.2% | 98% | 22.6d | 8d | 1.2d | 10.9d | 0.1d | 3.8d | 6.2% | 98.0% | 22.6d | 1.0d | 2026-10-13 00:03:48 | 216.0 Mbit/s (M) |
— = 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 (
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.