View Relay "camily"
Fingerprint: CA7EC826F69F7DCA2EFECDD7A94A07D7C7FC9A93 |
Family: 1 relay
|
camil_is_the_best@proton.me |
AS5089
|
United Kingdom of Great Britain and Northern Ireland
|
Linux
- Consensus
- In Consensus (9/9 Directory Auths)
- BW Verified
- 0/7 BW Auths Measured
- Stability
- Not Overloaded | DOWN 4h 15m 38s ago
- Reachability
- IPv4: 9/9 (Directory Auths)
- BW Weight
- 0 Kbit/s Observed By Relay
- Version
- 0.4.9.14 Recommended
Issues Detected:
-
Not getting the Fast flag
: Only 0/9 authorities vote Fast (5 needed). dizum, longclaw and maatuska used the relay-reported unknown, below the Fast threshold (816.0 Kbit/s). bastet, dannenberg, gabelmoo, moria1 and tor26 counted this relay as 0 (no measurement, relay-reported bandwidth ignored). faravahar judged it by bandwidth not shown in the votes.
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
: 0/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 – 280.0 Mbit/s). dizum, longclaw and maatuska used the relay-reported unknown. bastet, dannenberg, gabelmoo, moria1 and tor26 counted this relay as 0 (no measurement, relay-reported bandwidth ignored).
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 11.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. -
Guard: Time Known below threshold
: Time Known 0.1 days is below 8 days requirement (7.9 more days needed)
Suggestion: Time Known tracks how long authorities have observed your relay. This resets if: 1) Identity key changes, 2) Long downtime makes authorities forget you. Just keep running stably. -
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 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. -
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 11.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. -
HSDir: Time Known below threshold
: Time Known 3.0 hours below 25 hours (dir-spec default)
Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably. -
Low bandwidth authority measurements
: Only 0/7 bandwidth authorities measured this relay. Minimum 3 measurements needed for accurate consensus weight.
Suggestion: Low measurement count can indicate connectivity issues. Check: 1) Relay is reachable from multiple geographic locations, 2) ORPort accepts connections from bandwidth scanners, 3) RelayBandwidthRate in torrc matches actual capacity. New relays may take 1-2 days to be measured by all authorities.
Addresses
- OR Address
-
seve-27-b2-v4wan-173127-cust72.vm13.cable.virginm.net
82.9.240.73:9001
Reachability (Directory Authorities)
- IPv4
- 9/9
Location
- Country
-
United Kingdom of Great Britain and Northern Ireland
- Interactive Map
- View in RouteFluxMap
Eligible Flags (3):
Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 0/9 | Stable: 1/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 0/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 | Below (0/9 DA) | 0 bit/s (3 DA relay-reported) 0 bit/s (5 DA unmeasured, counted as 0) faravahar: 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 (1/9 DA) | Median: 0.0d (1/9 DA above threshold) Min/Max: 0.0d / 20737.9d (9/9 DA, Voting / Total Eligible) |
≥5.0d - 10.8d (varies) (≥5/9 DA) [Stricter] moria1: ≥8990.2d |
| Uptime | Below (0/9 DA) | 0.2d (R) | ≥3.3d - 3.4d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Below (0/9 DA) | 0/9 DA assigned Fast 0 bit/s (3 DA relay-reported) 0 bit/s (5 DA unmeasured, counted as 0) faravahar: 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.0d - 10.8d (varies) (≥5/9 DA) [Stricter] moria1: ≥8990.2d |
|
| 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: 13.3% (0/9 DA above threshold) Min/Max: 11.2% / 22.0% (9/9 DA, Voting / Total Eligible) |
≥98.0% (≥5/9 DA) | |
| Time Known | Below (0/9 DA) | Median: 0.1d (0/9 DA above threshold) Min/Max: 0.1d / 0.1d (9/9 DA, Voting / Total Eligible) |
≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.8d |
|
| Guard | Prereq: Fast | Below (0/9 DA) | 0/9 DA assigned Fast 0 bit/s (3 DA relay-reported) 0 bit/s (5 DA unmeasured, counted as 0) faravahar: 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.0d - 10.8d (varies) (≥5/9 DA) [Stricter] moria1: ≥8990.2d |
|
| 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: 13.3% (0/9 DA above threshold) Min/Max: 11.2% / 22.0% (9/9 DA, Voting / Total Eligible) |
≥98% (≥5/9 DA) | |
| Time Known | Below (0/9 DA) (need 7.9 more days) | Median: 0.1d (0/9 DA above threshold) Min/Max: 0.1d / 0.1d (9/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Below (0/9 DA) | 0 bit/s (3 DA relay-reported) 0 bit/s (5 DA unmeasured, counted as 0) faravahar: not published |
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-280.0 Mbit/s) (≥5/9 DA) | |
| Exit | Exit Policy | Below (0/9 DA) | Port 80: No | Port 443: No (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-12 02:15:05).
Capacity (Relay Reported)
- Observed Bandwidth
- 0.00 Kbit/s
- Advertised Bandwidth
- Unknown
- Rate Limit
- 16.78 Mbit/s
- Burst Limit
- 25.17 Mbit/s
- Total Data
- N/A
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-10-12 02:15:05
- Measured By
-
0/7
Bandwidth Authorities
Not measured by: bastet, dannenberg, faravahar, gabelmoo, longclaw, moria1, tor26 - Consensus Weight
- 0 bit/s (Unmeasured)
- Measured Min / Max
- N/A / N/A
Network Participation:
Consensus Weight:
N/A
|
Guard:
N/A |
Middle:
N/A |
Exit:
N/A
Uptime Metrics
- Current Status
- DOWN 4h 15m 38s 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
- 4h 15m 38s ago (2026-10-11 22:00:00)
- Last Seen
- 4h 15m 38s ago (2026-10-11 22:00:00)
- Last Restarted
- 4h 28m 20s ago (2026-10-11 21:47:18)
- Last Changed Address
- 2026-10-11 22:00:00
Overload Status:
Not Overloaded — No overload conditions reported.
Operator Identity
Source: AROI Validation API — 2026-10-11 18:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- camil_is_the_best@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
CA7EC826F69F7DCA2EFECDD7A94A07D7C7FC9A93 (this relay)
- Alleged Members: 0
- none
- Indirect Members: 0
- none
DNS Health
Not an exit relay — DNS health testing does not apply.Last fetch was at Mon, 12 Oct 2026 02:15:37 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-10-12 02:15:05).
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) | HSDir WFU (M|T) | HSDir TK (M|T) | Desc Published | Cons Wt (Authority) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| bastet (US) | Yes | Yes | No | — | Y | Yes | Valid | 0 bit/s (U) | 816.0 Kbit/s | 0 bit/s (U) | 192.0 Mbit/s OR 16.8 Mbit/s | 11.2% | 98% | 0.1d | 8d | 0.0d | 10.7d | 0.2d | 3.4d | 11.2% | 98.0% | 0.1d | 1.0d | 2026-10-11 21:48:23 | — |
| dannenberg (DE) | Yes | Yes | No | — | Y | Yes | Valid | 0 bit/s (U) | 816.0 Kbit/s | 0 bit/s (U) | 280.0 Mbit/s OR 16.8 Mbit/s | 11.7% | 98% | 0.1d | 8d | 0.0d | 5.0d | 0.2d | 3.4d | 11.7% | 98.0% | 0.1d | 1.0d | 2026-10-11 21:48:23 | — |
| dizum (NL) | Yes | Yes | No | — | N | Yes | Valid | 0 bit/s (R) | 816.0 Kbit/s | 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 18.9% | 98% | 0.1d | 8d | 0.0d | 10.8d | 0.2d | 3.4d | 18.9% | 98.0% | 0.1d | 1.0d | 2026-10-11 21:48:23 | — |
| faravahar (US) | Yes | Yes | No | — | Y | Yes | Valid | not published | 816.0 Kbit/s | not published | 280.0 Mbit/s OR 16.8 Mbit/s | 17.4% | 98% | 0.1d | 8d | 0.0d | 11.6d | 0.2d | 3.3d | 17.4% | 98.0% | 0.1d | 1.0d | 2026-10-11 21:48:23 | — |
| gabelmoo (DE) | Yes | Yes | No | — | Y | Yes | Valid | 0 bit/s (U) | 816.0 Kbit/s | 0 bit/s (U) | 264.0 Mbit/s OR 16.8 Mbit/s | 13.3% | 98% | 0.1d | 8d | 0.0d | 10.7d | 0.2d | 3.4d | 13.3% | 98.0% | 0.1d | 1.0d | 2026-10-11 21:48:23 | — |
| longclaw (US) | Yes | Yes | No | — | Y | Yes | Valid | 0 bit/s (R) | 816.0 Kbit/s | 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 12.7% | 98% | 0.1d | 8d | 0.0d | 11.1d | 0.2d | 3.3d | 12.7% | 98.0% | 0.1d | 1.0d | 2026-10-11 21:48:23 | — |
| maatuska (SE) | Yes | Yes | No | — | N | Yes | Valid | 0 bit/s (R) | 816.0 Kbit/s | 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 22.0% | 98% | 0.1d | 8d | 0.0d | 10.5d | 0.2d | 3.3d | 22.0% | 98.0% | 0.1d | 1.0d | 2026-10-11 21:48:23 | — |
| moria1 (US) | Yes | Yes | No | — | Y | Yes | Valid, Stable | 0 bit/s (U) | 8.4 Mbit/s | 0 bit/s (U) | 208.0 Mbit/s OR 16.8 Mbit/s | 16.9% | 98% | 0.1d | 8d | 20737.9d | 8990.2d | 0.2d | 3.4d | 16.9% | 98.0% | 0.1d | 9.8d | 2026-10-11 21:48:23 | — |
| tor26 (AT) | Yes | Yes | No | — | Y | Yes | Valid | 0 bit/s (U) | 816.0 Kbit/s | 0 bit/s (U) | 272.0 Mbit/s OR 16.8 Mbit/s | 13.2% | 98% | 0.1d | 8d | 0.0d | 11.2d | 0.2d | 3.4d | 13.2% | 98.0% | 0.1d | 1.0d | 2026-10-11 21:48:23 | — |
— = 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.