View Relay "prsv"
Fingerprint: 368DC03C48FCC94105C90B6D86AE0EF76ADB4818 |
Operator: prsv.ch v2
(324 relays)
✓ Validated
⚠ this relay: Misconfigured|
Family: 308 relays
|
email:admin[]prsv.ch... |
AS20860
|
United Kingdom of Great Britain and Northern Ireland
|
Linux
- Consensus
- In Consensus (8/10 Directory Auths)
- BW Verified
- 5/8 BW Auths Measured 616 Mbit/s Median
- Stability
- Incomplete | UP 1h 57m 3s ago
- Reachability
- IPv4: 8/10 | v6: 7/7(Directory Auths)
- BW Weight
- 0.04% of Network | 0 Kbit/s Observed By Relay
- Version
- 0.4.9.12 Not Recommended
Issues Detected:
-
Not getting the Fast flag
: Only 5/10 authorities vote Fast (6 needed). dizum, longclaw and maatuska used the relay-reported unknown, below the Fast threshold (816.0 Kbit/s).
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
: 5/10 authorities credit this relay with enough bandwidth for Guard (6 needed): at least 16.8 Mbit/s (AuthDirGuardBWGuarantee) or a place in their top 25% (80.0 Mbit/s – 256.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
: 1/10 authorities meet guard-wfu (≥98%; maatuska: ≥97.051%; 6 needed). dannenberg, dizum, gabelmoo, longclaw, maatuska, moria1 and tor26 measured 6.5%–11.5%.
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/10 authorities meet Stable (uptime or MTBF at or above their own median; 6 needed). E30CF7B3, dannenberg, dizum, 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 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. -
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.12 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.
Notes:
- Partial IPv4 reachability: 8/10 authorities can reach this relay
Suggestion: Some authorities cannot reach you: 5947BB57, faravahar. This may be temporary or due to geographic routing issues.
Addresses
- OR Address
-
new
81.168.83.241:9000
[2001:1b40:5700:98be::1]:9000
Reachability (Directory Authorities)
- IPv4
- 8/10
- IPv6
- 7/7 (1 don't test)
Location
- Country
-
United Kingdom of Great Britain and Northern Ireland
- Interactive Map
- View in RouteFluxMap
Eligible Flags (3):
Running: 8/10 | Valid: 8/10 | V2Dir: 8/10 | Fast: 5/10 | Stable: 1/10 | HSDir: 0/10 | Guard: 0/10 | Exit: 0/10
Eligibility Flag Vote Details
| Flag | Metric | Status | Relay Value | Threshold Required |
|---|---|---|---|---|
| Running | IPv4 Reachability | Meets (8/10 DA) | 8/10 authorities reached relay | ≥6/10 DA ORPort reachable |
| IPv6 Reachability | Meets (7/7 DA) | 7/7 tested authorities reached relay | ≥4/7 tested (majority) (≥4/7 DA) | |
| Valid | Descriptor | Meets (8/10 DA) | 8/10 authorities assigned Valid | Not blacklisted + valid descriptor (≥6/10 DA) |
| V2Dir | DirPort Available | Meets (8/10 DA) | Tunnelled: Yes (no DirPort) (R) | Tunnelled directory via ORPort or DirPort (≥6/10 DA) |
| Fast | Speed | Below (5/10 DA) | 296.0 Mbit/s – 728.0 Mbit/s (5 DA measured) 0 bit/s (3 DA relay-reported) |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥6/10 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Stable | MTBF | Below (0/10 DA) | Median: 1.2d (1/10 DA above threshold) Min/Max: 0.0d / 4283.1d (8/10 DA, Voting / Total Eligible) |
≥0.0d - 8.7d (varies) (≥6/10 DA) [Stricter] moria1: ≥10768.2d |
| Uptime | Below (0/10 DA) | 0.1d (R) | ≥2.0d - 2.4d (varies) (≥6/10 DA) [Stricter] 5947BB57: ≥5.9d |
|
| HSDir | Prereq: Fast | Below (5/10 DA) | 5/10 DA assigned Fast 296.0 Mbit/s – 728.0 Mbit/s (5 DA measured) 0 bit/s (3 DA relay-reported) |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥6/10 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Below (1/10 DA) | 1/10 DA assigned Stable | ≥0.0d - 8.7d (varies) (≥6/10 DA) [Stricter] moria1: ≥10768.2d |
|
| Prereq: V2Dir | Meets (8/10 DA) | 8/10 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥6/10 DA) | |
| Uptime | Below (0/10 DA) | 0.1d (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥6/10 DA) [Stricter] moria1: ≥98% WFU and ≥9.7d Time Known |
|
| Guard | Prereq: Fast | Below (5/10 DA) | 5/10 DA assigned Fast 296.0 Mbit/s – 728.0 Mbit/s (5 DA measured) 0 bit/s (3 DA relay-reported) |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥6/10 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Below (1/10 DA) | 1/10 DA assigned Stable | ≥0.0d - 8.7d (varies) (≥6/10 DA) [Stricter] moria1: ≥10768.2d |
|
| Prereq: V2Dir | Meets (8/10 DA) | 8/10 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥6/10 DA) | |
| WFU | Below (1/10 DA) | Median: 6.7% (1/10 DA above threshold) Min/Max: 6.5% / 100.0% (8/10 DA, Voting / Total Eligible) |
≥98%; maatuska: ≥97.051% (≥6/10 DA) | |
| Time Known | Partial (7/10 DA) | Median: 22.7d (7/10 DA above threshold) Min/Max: 0.02d / 22.8d (8/10 DA, Voting / Total Eligible) |
≥8 days; E30CF7B3: ≥2 days 13 minutes 8 seconds (≥6/10 DA) | |
| Bandwidth | Below (5/10 DA) | 296.0 Mbit/s – 728.0 Mbit/s (5 DA measured) 0 bit/s (3 DA relay-reported) |
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-256.0 Mbit/s) (≥6/10 DA) | |
| Exit | Exit Policy | Below (0/10 DA) | Port 80: No | Port 443: No (R) | Allows ≥1 /8 on ports 80 AND 443 (≥6/10 DA) |
(DA) = Dir. Auth. Measured |
(R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-11-14 22:45:06).
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-11-14 22:45:06
- Measured By
-
5/8
Bandwidth Authorities
Not measured by: 5947BB57, faravahar, longclaw - Consensus Weight
- 616.0 Mbit/s (median of 5 measurements)
- Measured Min / Max
- 296.0 Mbit/s / 728.0 Mbit/s
- Deviation
- 432.0 Mbit/s [Warning] High variation
Network Participation:
Consensus Weight:
0.0430% of network
(96th pctl)
|
Guard:
N/A |
Middle:
0.1230% (97th pctl) |
Exit:
N/A
Uptime Metrics
- Current Status
- UP 1h 57m 3s 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
- 1h 15m 27s ago (2026-11-14 22:00:00)
- Last Seen
- 1h 15m 27s ago (2026-11-14 22:00:00)
- Last Restarted
- 1h 57m 3s ago (2026-11-14 21:18:24)
- Last Changed Address
- 2026-11-14 22:00:00
Overload status:
Incomplete — not every signal could be evaluated.
(No bandwidth record available for this relay)
Evaluated 2026-11-14 23:15 UTC. /details snapshot 2026-11-14 22:00:00 UTC (cached 28s ago). /bandwidth snapshot 2026-11-14 20:00:00 UTC (cached 1h 30m ago).
General Overload (from /details)
- Status
- No general overload report in available data
File Descriptor Exhaustion (from /bandwidth)
- Status
- No bandwidth record available for this relay
Rate Limits (from /bandwidth)
- Status
- No bandwidth record available for this relay
- 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
Operator Identity
Source: AROI Validation API — 2026-11-14 14:00 UTC
- AROI Domain (?)
- prsv.ch
- Operator Validation
- Validated (322/324 relays)
- This Relay
-
Unvalidated
Error: Not yet processed by validator (relay may be new) - Contact
- email:admin[]prsv.ch url:https://prsv.ch/ proof:uri-rsa ciissversion:2
Family Configuration
- Family Support
- MyFamily Only (4) — Legacy only. Consider migrating to Happy Families. | View Full Family (308)
Happy Families (family-cert)
- Effective Members: 0
- none
MyFamily (legacy declarations)
- Effective Members: 4
368DC03C48FCC94105C90B6D86AE0EF76ADB4818 (this relay) B9982649CF52910F34523B08603D11917D28D8F4 EFA4E0BB6C66E176F2B393996517766D6BDC1D0D F33ED39F99A25887170CAF8CACCC3896B79FA5CC
- Alleged Members: 16
-
(they don't list you back)
02B9FF15129A310915C15AB30C673C7DE7A7CB20 2019C724A5DD0888CCED8424B979B11D2024B572 3E1EAC5527F50D9C8E8ACFD323D2629968A06BC1 47B3054618ACBF05FF9F6BE4DCDBE7960D0F6A3C 5CEA56320C904E731AE827866C71B90D50696F6A 626D4F2D6E22F658AA7C2CEA1D4C794C3590DD63 69ADDE95173724077934D6932973E9BB7A40A3BB 7F9013D5D7084BF730CB0983C8176DB9786AB926 870F7E72CA4C88DE891FF7E1B2D8BC46C67593D6 AB14872346F889C5664EE7C3B20493F40A2A8D5C ADE7302E38F14044E460A82E64B5FEE1459BEC37 BC2741B0C37B8EB646A8172B7B0BDA3B8F12B747 BC42307930E647C3A16F88CA69C47A751D501368 D74EA68923AC3449DEA549F10A89E6B33A770A39 E6E1FD78429A99744E5E9CDDC74C6A97448D8BD1 FC0A83C73D9DA146D3608AE71F54E322890D59C5
- Indirect Members: 16
-
(they list you, you don't list them)
02B9FF15129A310915C15AB30C673C7DE7A7CB20 2019C724A5DD0888CCED8424B979B11D2024B572 3E1EAC5527F50D9C8E8ACFD323D2629968A06BC1 47B3054618ACBF05FF9F6BE4DCDBE7960D0F6A3C 5CEA56320C904E731AE827866C71B90D50696F6A 626D4F2D6E22F658AA7C2CEA1D4C794C3590DD63 69ADDE95173724077934D6932973E9BB7A40A3BB 7F9013D5D7084BF730CB0983C8176DB9786AB926 870F7E72CA4C88DE891FF7E1B2D8BC46C67593D6 AB14872346F889C5664EE7C3B20493F40A2A8D5C ADE7302E38F14044E460A82E64B5FEE1459BEC37 BC2741B0C37B8EB646A8172B7B0BDA3B8F12B747 BC42307930E647C3A16F88CA69C47A751D501368 D74EA68923AC3449DEA549F10A89E6B33A770A39 E6E1FD78429A99744E5E9CDDC74C6A97448D8BD1 FC0A83C73D9DA146D3608AE71F54E322890D59C5
- Platform
- Linux — Tor 0.4.9.12 on Linux
- Version
- 0.4.9.12 — Not Recommended
- Version Status
- Obsolete — Update urgently. See torproject.org/download — prsv.ch: 96 of 324 on 0.4.9.14 and 0.4.9.12, 0.86% of consensus weight. Operator versions
DNS Health
Not an exit relay — DNS health testing does not apply.Last fetch was at Sat, 14 Nov 2026 23:15:27 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-14 22: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 | 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) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 5947BB57 | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — |
| E30CF7B3 | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast | 296.0 Mbit/s (M) | 816.0 Kbit/s | 296.0 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 0.0d | 2d | 0.0d | 2.1d | 0.1d | 2.5d | 2026-11-14 21:25:21 | 296.0 Mbit/s (M) |
| dannenberg (DE) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast | 656.0 Mbit/s (M) | 816.0 Kbit/s | 656.0 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s | 6.5% | 98% | 22.7d | 8d | 1.1d | 8.7d | 0.1d | 2.2d | 2026-11-14 21:25:21 | 656.0 Mbit/s (M) |
| dizum (NL) | Yes | Yes | No | — | N | Yes | Yes | Running, Valid, V2Dir | 0 bit/s (R) | 816.0 Kbit/s | 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 6.7% | 98% | 22.8d | 8d | 1.2d | 6.7d | 0.1d | 3.1d | 2026-11-14 21:25:21 | — |
| faravahar (US) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — |
| gabelmoo (DE) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast | 616.0 Mbit/s (M) | 816.0 Kbit/s | 616.0 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s | 6.7% | 98% | 22.8d | 8d | 1.2d | 8.9d | 0.1d | 2.2d | 2026-11-14 21:25:21 | 616.0 Mbit/s (M) |
| longclaw (US) | Yes | Yes | No | — | Y | Yes | N/T | Running, Valid, V2Dir | 0 bit/s (R) | 816.0 Kbit/s | 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 6.6% | 98% | 22.8d | 8d | 1.2d | 9.5d | 0.1d | 2.4d | 2026-11-14 21:25:21 | — |
| maatuska (SE) | Yes | Yes | No | — | N | Yes | Yes | Running, Valid, V2Dir | 0 bit/s (R) | 816.0 Kbit/s | 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 6.5% | 97% | 22.6d | 8d | 1.2d | 1.6d | 0.1d | 2.3d | 2026-11-14 21:25:21 | — |
| moria1 (US) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable | 352.0 Mbit/s (M) | 8.4 Mbit/s | 352.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 11.5% | 98% | 9.3d | 8d | 4283.1d | 10768.2d | 0.1d | 2.0d | 2026-11-14 21:25:21 | 352.0 Mbit/s (M) |
| tor26 (AT) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast | 728.0 Mbit/s (M) | 816.0 Kbit/s | 728.0 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s | 6.6% | 98% | 22.8d | 8d | 1.2d | 8.8d | 0.1d | 2.4d | 2026-11-14 21:25:21 | 728.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.