View Relay "shanoshema"
Family: 1 relay | [email protected] | AS8866 | Bulgaria | Linux
- Consensus
- In Consensus (9/9 Directory Auths)
- BW Verified
- 5/6 BW Auths Measured 9 Kbit/s Median
- Stability
- Not Overloaded | UP 1d 18h 45m ago | UP 78% (1M)
- Reachability
- IPv4: 9/9 (Directory Auths)
- First Seen
- 1y 12mo 4d ago
- BW Weight
- 0.00% of Network | 12 Mbit/s Observed By Relay
- Version
- 0.4.8.21 Recommended
Issues Detected:
-
Guard: bandwidth below threshold
: Observed bandwidth 1.6 MB/s is below 2 MB/s minimum (AuthDirGuardBWGuarantee)
Suggestion: Guard requires ≥2 MB/s bandwidth OR being in top 25% of network. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx or ARM. -
Guard: WFU below threshold
: Weighted Fractional Uptime 77.3% 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: 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). -
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: WFU below threshold
: WFU 77.3% 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. -
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
-
77-85-153-22.ip.btc-net.bg
77.85.153.22:9001 - Exit Address
- 77.85.153.22
Reachability (Directory Authorities)
- IPv4
- 9/9
Location
- Country
-
Bulgaria
- Interactive Map
- View on Interactive Map
Eligible Flags (4):
Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 1/9 | HSDir: 0/9 | Guard: 0/9 (need ≥5/9 for flag)
Eligibility Flag Vote Details
| Flag | Metric | Status | Relay Value | Threshold Required |
|---|---|---|---|---|
| Fast | Speed | Meets (≥100 KB/s) | 12.5 Mbit/s (R) | ≥800.0 Kbit/s (guarantee) OR top 7/8 [Stricter] moria1: ≥8.4 Mbit/s |
| Stable | MTBF | Below | Median: 2.4d (1/9 DA above threshold) Min/Max: 2.3d / 15869.1d (9/9 DA, Voting / Total Eligible) |
≥22.3d - 53.9d (varies) [Stricter] moria1: ≥403.9d |
| Uptime | Below | 1.8d (R) | ≥10.0d - 10.8d (varies) | |
| HSDir | Prereq: Stable | Below | 1/9 authorities assigned Stable flag | ≥5/9 authorities |
| Prereq: Fast | Meets | 9/9 authorities assigned Fast flag | ≥5/9 authorities | |
| WFU | Below | Median: 77.3% (0/9 DA above threshold) Min/Max: 77.2% / 84.2% (9/9 DA, Voting / Total Eligible) |
≥98.0% | |
| Time Known | Meets | Median: 13.9d (9/9 DA above threshold) Min/Max: 9.5d / 14.2d (9/9 DA, Voting / Total Eligible) |
≥1.0d (most) [Stricter] moria1: ≥9.8d |
|
| Guard | Prereq: Fast | Meets | 9/9 authorities assigned Fast flag | ≥5/9 authorities |
| Prereq: Stable | Below | 1/9 authorities assigned Stable flag | ≥5/9 authorities | |
| Prereq: V2Dir | Meets | 9/9 authorities assigned V2Dir flag | ≥5/9 authorities | |
| WFU | Below | Median: 77.3% (0/9 DA above threshold) Min/Max: 77.2% / 84.2% (9/9 DA, Voting / Total Eligible) |
≥98% (all authorities) | |
| Time Known | Meets | Median: 13.9d (9/9 DA above threshold) Min/Max: 9.5d / 14.2d (9/9 DA, Voting / Total Eligible) |
≥8 days (all authorities) | |
| Bandwidth | Below | 12.5 Mbit/s (R) | ≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s |
(DA) = Dir. Auth. Measured |
(R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-01-29 11:45:07).
Last fetch was at Thu, 29 Jan 2026 12:45:34 GMT.
- shanoshema
-
C95A2CB440F382606D092A68BB7C3C36F1B73BBA - none
- [email protected]
-
reject: 25 119 135-139 445 563 1214 4661-4666 6346-6429 6699 6881-6999
-
none
-
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 77.85.153.22:* reject *:25 reject *:119 reject *:135-139 reject *:445 reject *:563 reject *:1214 reject *:4661-4666 reject *:6346-6429 reject *:6699 reject *:6881-6999 accept *:*
-
C95A2CB440F382606D092A68BB7C3C36F1B73BBA
-
none
-
none
- 12.51 Mbit/s | 12.51 Mbit/s| 8.59 Gbit/s| 8.59 Gbit/s Measured
- 0.00% | N/A | N/A | 0.00%
- 77-85-153-22.ip.btc-net.bg | 77.85.153.22:9001
- none
- none
-
Bulgaria
- View on Interactive Map
- AS8866 | Vivacom Bulgaria EAD (BGP.tools)
-
Exit
Fast
Running
V2Dir
Valid
- —/—/—/5.9%
- 78.8%/19.2%/9.5%/11.4%
- UP 1d 18h 45m ago
- 1y 12mo 4d ago (2024-01-30 15:00:00) | 1h 47m 6s ago (2026-01-29 11:00:00)
- 1d 18h 46m ago (2026-01-27 18:00:19)
- 2026-01-04 22:00:00
- No
- Linux | Tor 0.4.8.21 on Linux
- 0.4.8.21 | Yes | recommended
Data from Tor CollecTor (authority votes, fetched 2026-01-29 11:45:07).
- Consensus Status (need ≥5/9): In Consensus — 9/9 authorities voted.
- Flag Eligibility (need ≥5/9 for flag): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 1/9 | HSDir: 0/9 | Guard: 0/9
- Reachability: IPv4: 9/9
- Consensus Weight (Dir. Auth.): Median: 9.6 Kbit/s | Min: 3680 bit/s | Max: 12.5 Kbit/s [Warning] High deviation
- Identified Issues:
-
Guard: bandwidth below threshold: Observed bandwidth 1.6 MB/s is below 2 MB/s minimum (AuthDirGuardBWGuarantee)
- Suggestion: Guard requires ≥2 MB/s bandwidth OR being in top 25% of network. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx or ARM.
-
Guard: WFU below threshold: Weighted Fractional Uptime 77.3% 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: 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).
-
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: WFU below threshold: WFU 77.3% 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.
-
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.
-
Guard: bandwidth below threshold: Observed bandwidth 1.6 MB/s is below 2 MB/s minimum (AuthDirGuardBWGuarantee)
Green = meets threshold, Red = below threshold, Yellow = partial.
| Metric | Dir Auth Measured | Dir Auth Threshold | Status |
|---|---|---|---|
| In Consensus (Dir. Auth.) | 9/9 authorities | ≥5/9 (majority) | IN CONSENSUS |
| Running (IPv4 Reachable) | 9/9 authorities reached this relay | ≥5/9 (majority) | RUNNING |
| Valid | 9/9 (Running + Valid Descriptor) | ≥5/9 (majority) | VALID |
| Consensus Weight (Dir. Auth.) | 9.6 Kbit/s (median) | N/A (no threshold, used for path selection) | — |
| Guard WFU (Dir. Auth., guard-wfu) | 77.3% | ≥98% (all authorities) | BELOW - cannot get Guard |
| Guard TK (Dir. Auth., tk) | 13.9 days | ≥8 days (all authorities) | MEETS |
| Guard BW (Relay Reported) | 12.5 Mbit/s | ≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s | BELOW - need ≥2 MB/s |
| Stable Uptime (Relay Reported) | 1.8d | ≥10.0d - 10.8d (typical) | BELOW - 0/9 |
| Stable MTBF (Dir. Auth., mtbf) | 2 days |
≥22.3d - 53.9d (typical)
[Stricter] moria1: ≥403.9d |
BELOW - 1/9 |
| Fast Speed (Relay Reported) | 12.5 Mbit/s |
≥800.0 Kbit/s (guarantee) OR ≥816.0 Kbit/s (typical)
[Stricter] moria1: ≥8.4 Mbit/s |
MEETS - ≥100 KB/s guarantee |
| HSDir WFU (Dir. Auth., wfu) | 77.3% | ≥98.0% (from all auths) | BELOW - 0/9 |
| HSDir TK (Dir. Auth., tk) | 13.9 days |
≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.8d |
BELOW - 0/9 |
Each cell shows: your measured value | authority threshold. Green = meets, red = below. Flags: green = all authorities agree, yellow = partial.
| Authority | Running | Valid | BW Scan (Authority) | v4 | Flags | Fast (Relay|T) | Guard BW (Relay|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 | Y | Yes | Running, Valid, V2Dir, Fast, Exit | 12.5 Mbit/s | 816.0 Kbit/s | 12.5 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s | 77.3% | 98% | 13.9d | 8d | 2.3d | 50.5d | 1.8d | 11.4d | 77.3% | 98.0% | 13.9d | 1.0d | 2026-01-29 06:01:28 | 9.6 Kbit/s |
| dannenberg (DE) | Yes | Yes | N | Yes | Running, Valid, V2Dir, Fast, Exit | 12.5 Mbit/s | 816.0 Kbit/s | 12.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s | 77.3% | 98% | 14.2d | 8d | 2.4d | 22.3d | 1.8d | 10.8d | 77.3% | 98.0% | 14.2d | 1.0d | 2026-01-29 06:01:28 | 12.5 Kbit/s |
| dizum (NL) | Yes | Yes | N | Yes | Running, Valid, V2Dir, Fast, Exit | 12.5 Mbit/s | 816.0 Kbit/s | 12.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s | 77.4% | 98% | 13.6d | 8d | 2.4d | 34.8d | 1.8d | 10.9d | 77.4% | 98.0% | 13.6d | 1.0d | 2026-01-29 06:01:28 | 12.5 Kbit/s |
| faravahar (US) | Yes | Yes | N | Yes | Running, Valid, V2Dir, Fast, Exit | 12.5 Mbit/s | 816.0 Kbit/s | 12.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s | 77.2% | 98% | 14.1d | 8d | 2.4d | 47.4d | 1.8d | 10.0d | 77.2% | 98.0% | 14.1d | 1.0d | 2026-01-29 06:01:28 | 12.5 Kbit/s |
| gabelmoo (DE) | Yes | Yes | Y | Yes | Running, Valid, V2Dir, Fast, Exit | 12.5 Mbit/s | 816.0 Kbit/s | 12.5 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s | 77.6% | 98% | 13.6d | 8d | 2.4d | 53.9d | 1.8d | 10.9d | 77.6% | 98.0% | 13.6d | 1.0d | 2026-01-29 06:01:28 | 3680 bit/s |
| longclaw (US) | Yes | Yes | Y | Yes | Running, Valid, V2Dir, Fast, Exit | 12.5 Mbit/s | 816.0 Kbit/s | 12.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s | 77.3% | 98% | 14.1d | 8d | 2.4d | 55.1d | 1.8d | 10.2d | 77.3% | 98.0% | 14.1d | 1.0d | 2026-01-29 06:01:28 | 12.5 Kbit/s |
| maatuska (SE) | Yes | Yes | Y | Yes | Running, Valid, V2Dir, Fast, Exit | 12.5 Mbit/s | 816.0 Kbit/s | 12.5 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s | 84.2% | 98% | 13.0d | 8d | 2.4d | 55.2d | 1.8d | 10.1d | 84.2% | 98.0% | 13.0d | 1.0d | 2026-01-29 06:01:28 | 4480 bit/s |
| moria1 (US) | Yes | Yes | Y | Yes | Running, Valid, V2Dir, Fast, Stable, Exit | 12.5 Mbit/s | 8.4 Mbit/s | 12.5 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s | 78.9% | 98% | 9.5d | 8d | 15869.1d | 403.9d | 1.8d | 10.6d | 78.9% | 98.0% | 9.5d | 9.8d | 2026-01-29 06:01:28 | 9.6 Kbit/s |
| tor26 (AT) | Yes | Yes | Y | Yes | Running, Valid, V2Dir, Fast, Exit | 12.5 Mbit/s | 816.0 Kbit/s | 12.5 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s | 77.2% | 98% | 14.1d | 8d | 2.4d | 55.8d | 1.8d | 11.9d | 77.2% | 98.0% | 14.1d | 1.0d | 2026-01-29 06:01:28 | 3920 bit/s |
— = not tested/available • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known
Bandwidth Values Explained:
Relay Reported = Your relay's self-reported bandwidth from its descriptor (observed_bandwidth). Used for flag eligibility (Guard, Fast).
Authority Measured = Bandwidth measured by authority's sbws scanner. Used for consensus weight (path selection probability).
Why different? Authorities verify your reported bandwidth independently. 6 of 9 authorities run bandwidth scanners; 3 use relay-reported values directly.
Relay Reported = Your relay's self-reported bandwidth from its descriptor (observed_bandwidth). Used for flag eligibility (Guard, Fast).
Authority Measured = Bandwidth measured by authority's sbws scanner. Used for consensus weight (path selection probability).
Why different? Authorities verify your reported bandwidth independently. 6 of 9 authorities run bandwidth scanners; 3 use relay-reported values directly.
Stable Uptime (Two Data Sources):
Relay Uptime = From Onionoo API (last_restarted field). This is your relay's self-reported uptime from its 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). This is your relay's self-reported uptime from its 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.