View Relay "Weaponized2"
Fingerprint: E6272D9DC1D39FDB4C1DAC2F206127448A640752 |
Family: 1 relay
|
danvondra (at) protonmail (dot) com |
AS10796
|
United States of America
|
Linux
- Consensus
- In Consensus (9/9 Directory Auths)
- BW Verified
- 5/7 BW Auths Measured 64 Kbit/s Median
- Stability
- Overloaded | UP 6d 7h 49m ago | UP 94% (1M)
- Reachability
- IPv4: 9/9 | v6: None configured(Directory Auths)
- BW Weight
- 0.00% of Network | 4 Mbit/s Observed By Relay
- Version
- 0.4.9.15 Recommended
Issues Detected:
-
Not getting the Fast flag
: Only 4/9 authorities vote Fast (5 needed). bastet, dannenberg, gabelmoo, moria1 and tor26 measured this relay at 40.0 Kbit/s – 648.0 Kbit/s, below the Fast threshold (816.0 Kbit/s; moria1: 8.4 Mbit/s). Its consensus weight, the median of the 5 bandwidth-scanner measurements, is 64.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: 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 – 272.0 Mbit/s). bastet, dannenberg, gabelmoo, moria1 and tor26 measured this relay at 40.0 Kbit/s – 648.0 Kbit/s. dizum, faravahar, longclaw and maatuska used the relay-reported 4.1 Mbit/s.
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
: 0/9 authorities meet guard-wfu (≥98%; dizum: ≥97.774%; 5 needed). bastet, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 measured 93.4%–96.1%.
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. -
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. -
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. -
Write Bandwidth Limit Hit
: Write rate-limit counter is 38 (configured rate 4.10 Mbit/s). Read and write counters increment at most once per minute per direction. They are not a count of blocked connections, the duration of throttling, or necessarily the number of events in the last 24 hours.
Suggestion: Inspect BandwidthRate and BandwidthBurst (the values reported with this hit), any relay-specific caps such as RelayBandwidthRate and RelayBandwidthBurst, the intended bandwidth budget, and actual uplink headroom. A rate-limit report is not evidence of ISP throttling. After checking that evidence and the capacity you meant to offer, review whether those limits should change. MetricsPort: tor_relay_load_global_rate_limit_reached_total{side="read"} and {side="write"}. Increases indicate additional global token-bucket limit events. -
Read Bandwidth Limit Hit
: Read rate-limit counter is 89 (configured rate 4.10 Mbit/s). Read and write counters increment at most once per minute per direction. They are not a count of blocked connections, the duration of throttling, or necessarily the number of events in the last 24 hours.
Suggestion: Inspect BandwidthRate and BandwidthBurst (the values reported with this hit), any relay-specific caps such as RelayBandwidthRate and RelayBandwidthBurst, the intended bandwidth budget, and actual uplink headroom. A rate-limit report is not evidence of ISP throttling. After checking that evidence and the capacity you meant to offer, review whether those limits should change. MetricsPort: tor_relay_load_global_rate_limit_reached_total{side="read"} and {side="write"}. Increases indicate additional global token-bucket limit events.
Notes:
- Rate Limit Configuration: Configured limits: Rate=4.10 Mbit/s, Burst=512 KB. Counters: Write=38, Read=89. These values are BandwidthRate and BandwidthBurst from the extra-info descriptor. RelayBandwidthRate and RelayBandwidthBurst are additional torrc caps, not the names of these values. Burst is a quantity of bytes.
Suggestion: Inspect BandwidthRate and BandwidthBurst (the values reported with this hit), any relay-specific caps such as RelayBandwidthRate and RelayBandwidthBurst, the intended bandwidth budget, and actual uplink headroom. A rate-limit report is not evidence of ISP throttling. After checking that evidence and the capacity you meant to offer, review whether those limits should change. MetricsPort: tor_relay_load_global_rate_limit_reached_total{side="read"} and {side="write"}. Increases indicate additional global token-bucket limit events.
Addresses
- OR Address
- 24.31.164.114:10001
Reachability (Directory Authorities)
- IPv4
- 9/9
- IPv6
- None configured
Location
- Country
-
United States of America
- Interactive Map
- View in RouteFluxMap
Eligible Flags (4):
Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 4/9 | Stable: 8/9 | HSDir: 3/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 | Meets (9/9 DA) | Tunnelled: Yes (no DirPort) (R) | Tunnelled directory via ORPort or DirPort (≥5/9 DA) |
| Fast | Speed | Below (4/9 DA) | 40.0 Kbit/s – 648.0 Kbit/s (5 DA measured) 4.1 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 (2/9 DA) | Median: 8.9d (1/9 DA above threshold) Min/Max: 2.1d / 8982.7d (9/9 DA, Voting / Total Eligible) |
≥2.3d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.9d |
| Uptime | Meets (9/9 DA) | 6.3d (R) | ≥5.2d - 5.3d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Below (4/9 DA) | 4/9 DA assigned Fast 40.0 Kbit/s – 648.0 Kbit/s (5 DA measured) 4.1 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 | Meets (8/9 DA) | 8/9 DA assigned Stable | ≥2.3d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.9d |
|
| Prereq: V2Dir | Meets (9/9 DA) | 9/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| Uptime | Meets (9/9 DA) | 6.3d (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.8d Time Known |
|
| Guard | Prereq: Fast | Below (4/9 DA) | 4/9 DA assigned Fast 40.0 Kbit/s – 648.0 Kbit/s (5 DA measured) 4.1 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 | Meets (8/9 DA) | 8/9 DA assigned Stable | ≥2.3d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.9d |
|
| Prereq: V2Dir | Meets (9/9 DA) | 9/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Below (0/9 DA) | Median: 96.0% (0/9 DA above threshold) Min/Max: 93.4% / 96.1% (9/9 DA, Voting / Total Eligible) |
≥98%; dizum: ≥97.774% (≥5/9 DA) | |
| Time Known | Meets (9/9 DA) | Median: 15.8d (9/9 DA above threshold) Min/Max: 9.8d / 16.2d (9/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Below (0/9 DA) | 40.0 Kbit/s – 648.0 Kbit/s (5 DA measured) 4.1 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 | 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-11-04 11:15:19).
Capacity (Relay Reported)
- Observed Bandwidth
- 4.08 Mbit/s
- Advertised Bandwidth
- 4.08 Mbit/s
- Rate Limit
- 4.10 Mbit/s
- Burst Limit
- 4.10 Mbit/s
- Total Data
-
1.7 TB
(5 years)
1mo: 11 GB | 6mo: 951 GB | 1y: 1.1 TB | 5y: 1.7 TB
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-04 11:15:19
- Measured By
-
5/7
Bandwidth Authorities
Not measured by: faravahar, longclaw - Consensus Weight
- 64.0 Kbit/s (median of 5 measurements)
- Measured Min / Max
- 40.0 Kbit/s / 648.0 Kbit/s
- Deviation
- 608.0 Kbit/s [Warning] High variation
Network Participation:
Consensus Weight:
0.0000% of network
(2th pctl)
|
Guard:
N/A |
Middle:
0.0000% (2th pctl) |
Exit:
N/A
History
Uptime Metrics
- Current Status
- UP 6d 7h 49m ago
- Overall Uptime (1M/6M/1Y/5Y)
- 94.6%/92.3%/91.5%/92.1%
- Flag Uptime (1M/6M/1Y/5Y)
- Matches Overall Uptime (94.6%/92.3%/91.5%/92.1%)
- Hibernating
- No
Timestamps
- First Seen
- 1y 9mo 3w ago (2025-01-15 03:00:00)
- Last Seen
- 1h 15m 40s ago (2026-11-04 11:00:00)
- Last Restarted
- 6d 7h 49m ago (2026-10-29 04:25:49)
- Last Changed Address
- 2026-08-21 17:00:00
[Warning] OVERLOADED
— Rate limits hit W:38 R:89 (limit: 4.10 Mbit/s)
Evaluated 2026-11-04 12:15 UTC. /details snapshot 2026-11-04 11:00:00 UTC (cached 25s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 4h 30m ago).
Reported timestamps use hour precision, so the displayed minute is not an exact incident time.
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
- Reported
- Rate Limit
- 4.10 Mbit/s
- Burst Limit
- 512 KB
- Write counter
- 38
- Read counter
- 89
- Reported
- 2026-11-04 00:00 UTC (12 hours ago)
Read and write counters increment at most once per minute per direction. They are not a count of blocked connections, the duration of throttling, or necessarily the number of events in the last 24 hours. Rate is BandwidthRate and follows this site’s bits/bytes setting. Burst is BandwidthBurst, already a byte quantity. RelayBandwidthRate and RelayBandwidthBurst are extra torrc caps, not the names of these values. A hit stays eligible for 24 hours.
What to check
-
Configured bandwidth limits
Inspect BandwidthRate and BandwidthBurst (the values reported with this hit), any relay-specific caps such as RelayBandwidthRate and RelayBandwidthBurst, the intended bandwidth budget, and actual uplink headroom. A rate-limit report is not evidence of ISP throttling. After checking that evidence and the capacity you meant to offer, review whether those limits should change.MetricsPort:
tor_relay_load_global_rate_limit_reached_total{side="read"} and {side="write"}— Increases indicate additional global token-bucket limit events.
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 03:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- danvondra (at) protonmail (dot) com
Family Configuration
- Family Support
- None — No family membership configured
Happy Families (family-cert)
- Effective Members: 0
- none
MyFamily (legacy declarations)
- Effective Member: 1
E6272D9DC1D39FDB4C1DAC2F206127448A640752 (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 Wed, 04 Nov 2026 12:15:39 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-04 11:15:19).
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 | No | — | Y | Yes | Running, Valid, V2Dir, Stable | 648.0 Kbit/s (M) | 816.0 Kbit/s | 648.0 Kbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 96.0% | 98% | 16.0d | 8d | 7.8d | 8.4d | 6.3d | 5.2d | 2026-11-04 00:28:48 | 648.0 Kbit/s (M) |
| dannenberg (DE) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir, Stable | 64.0 Kbit/s (M) | 816.0 Kbit/s | 64.0 Kbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s | 96.1% | 98% | 15.9d | 8d | 9.0d | 9.3d | 6.3d | 5.3d | 2026-11-04 00:28:48 | 64.0 Kbit/s (M) |
| dizum (NL) | Yes | Yes | No | — | N | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir | 4.1 Mbit/s (R) | 816.0 Kbit/s | 4.1 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 93.4% | 98% | 13.9d | 8d | 7.2d | 6.7d | 6.3d | 5.3d | 2026-11-04 00:28:48 | 4.1 Mbit/s (R) |
| faravahar (US) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir | 4.1 Mbit/s (R) | 816.0 Kbit/s | 4.1 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 95.2% | 98% | 12.9d | 8d | 5.1d | 6.5d | 6.3d | 5.3d | 2026-11-04 00:28:48 | 4.1 Mbit/s (R) |
| gabelmoo (DE) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir, Stable | 64.0 Kbit/s (M) | 816.0 Kbit/s | 64.0 Kbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s | 96.1% | 98% | 16.2d | 8d | 9.1d | 10.7d | 6.3d | 5.3d | 2026-11-04 00:28:48 | 64.0 Kbit/s (M) |
| longclaw (US) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir | 4.1 Mbit/s (R) | 816.0 Kbit/s | 4.1 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 96.1% | 98% | 15.8d | 8d | 8.9d | 10.9d | 6.3d | 5.3d | 2026-11-04 00:28:48 | 4.1 Mbit/s (R) |
| maatuska (SE) | Yes | Yes | No | — | N | Yes | Running, Valid, V2Dir, Fast | 4.1 Mbit/s (R) | 816.0 Kbit/s | 4.1 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 94.5% | 98% | 13.9d | 8d | 2.1d | 2.3d | 6.3d | 5.3d | 2026-11-04 00:28:48 | 4.1 Mbit/s (R) |
| moria1 (US) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir, Stable | 120.0 Kbit/s (M) | 8.4 Mbit/s | 120.0 Kbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 94.0% | 98% | 9.8d | 8d | 8982.7d | 7607.9d | 6.3d | 5.3d | 2026-11-04 00:28:48 | 120.0 Kbit/s (M) |
| tor26 (AT) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir, Stable | 40.0 Kbit/s (M) | 816.0 Kbit/s | 40.0 Kbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s | 96.1% | 98% | 15.9d | 8d | 9.0d | 10.6d | 6.3d | 5.3d | 2026-11-04 00:28:48 | 40.0 Kbit/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.