View Relay "Assange026fi"
Fingerprint: 6D4D5193A0E290C027FE6B66731133F70946A155 |
Operator: assange0-family.github.io v2
(24 relays)
✓ Validated
|
Family: 23 relays
|
email:BMTY90VKYRQPUJZOTH[]Safe-mail.n... |
AS51765
|
Finland
|
Linux
- Consensus
- In Consensus (9/9 Directory Auths)
- BW Verified
- 5/7 BW Auths Measured 96 Mbit/s Median
- Stability
- Overloaded | UP 3w 10h 33m ago | UP 99% (1M)
- Reachability
- IPv4: 9/9 | v6: None configured(Directory Auths)
- BW Weight
- 0.01% of Network | 81 Mbit/s Observed By Relay
- Version
- 0.4.9.14 Not Recommended
Issues Detected:
-
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 -
Tor version not recommended
: Running Tor version 0.4.9.14 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. -
Write Bandwidth Limit Hit
: Write rate-limit counter is 2,986 (configured rate 83.89 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 10,402 (configured rate 83.89 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=83.89 Mbit/s, Burst=13 MB. Counters: Write=2,986, Read=10,402. 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
- 185.103.110.14:9001
Reachability (Directory Authorities)
- IPv4
- 9/9
- IPv6
- None configured
Location
- Country
-
Finland
- Interactive Map
- View in RouteFluxMap
Eligible Flags (5):
Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 9/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 | Meets (9/9 DA) | 72.8 Mbit/s – 112.0 Mbit/s (5 DA measured) 80.0 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 | Partial (8/9 DA) | Median: 21.2d (8/9 DA above threshold) Min/Max: 5.8d / 3667.5d (9/9 DA, Voting / Total Eligible) |
≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d |
| Uptime | Meets (9/9 DA) | 21.4d (R) | ≥5.2d - 5.3d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Meets (9/9 DA) | 9/9 DA assigned Fast 72.8 Mbit/s – 112.0 Mbit/s (5 DA measured) 80.0 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 (9/9 DA) | 9/9 DA assigned Stable | ≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d |
|
| Prereq: V2Dir | Below (0/9 DA) | 0/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| Uptime | Meets (9/9 DA) | 21.4d (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.8d Time Known |
|
| Guard | Prereq: Fast | Meets (9/9 DA) | 9/9 DA assigned Fast 72.8 Mbit/s – 112.0 Mbit/s (5 DA measured) 80.0 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 (9/9 DA) | 9/9 DA assigned Stable | ≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d |
|
| Prereq: V2Dir | Below (0/9 DA) | 0/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Meets (9/9 DA) | Median: 99.9% (9/9 DA above threshold) Min/Max: 98.6% / 100.0% (9/9 DA, Voting / Total Eligible) |
≥98%; dizum: ≥97.84099999999999% (≥5/9 DA) | |
| Time Known | Meets (9/9 DA) | Median: 20.2d (9/9 DA above threshold) Min/Max: 9.8d / 63.5d (9/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Meets (9/9 DA) | 72.8 Mbit/s – 112.0 Mbit/s (5 DA measured) 80.0 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 12:45:10).
Capacity (Relay Reported)
- Observed Bandwidth
- 81.55 Mbit/s
- Advertised Bandwidth
- 81.55 Mbit/s
- Rate Limit
- 83.89 Mbit/s
- Burst Limit
- 100.66 Mbit/s
- Total Data
-
1.0 PB
(5 years)
1mo: 37 TB | 6mo: 87 TB | 1y: 195 TB | 5y: 1.0 PB
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-04 12:45:10
- Measured By
-
5/7
Bandwidth Authorities
Not measured by: faravahar, longclaw - Consensus Weight
- 96.0 Mbit/s (median of 5 measurements)
- Measured Min / Max
- 72.8 Mbit/s / 112.0 Mbit/s
Network Participation:
Consensus Weight:
0.0061% of network
(55th pctl)
|
Guard:
N/A |
Middle:
0.0175% (76th pctl) |
Exit:
N/A
History
Uptime Metrics
- Current Status
- UP 3w 10h 33m ago
- Overall Uptime (1M/6M/1Y/5Y)
- 99.9%/88.7%/94.0%/96.7%
- Flag Uptime (1M/6M/1Y/5Y)
- Matches Overall Uptime (99.9%/88.7%/94.0%/96.7%)
- Hibernating
- No
Timestamps
- First Seen
- 6y 9mo 3d ago (2020-02-06 10:00:00)
- Last Seen
- 2h 15m 38s ago (2026-11-04 11:00:00)
- Last Restarted
- 3w 10h 33m ago (2026-10-14 02:41:43)
- Last Changed Address
- 2026-04-06 23:00:00
[Warning] OVERLOADED
— Rate limits hit W:2,986 R:10,402 (limit: 83.89 Mbit/s)
Evaluated 2026-11-04 13:15 UTC. /details snapshot 2026-11-04 11:00:00 UTC (cached 19s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 5h 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
- 83.89 Mbit/s
- Burst Limit
- 13 MB
- Write counter
- 2,986
- Read counter
- 10,402
- Reported
- 2026-11-04 01: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 04:00 UTC
- AROI Domain (?)
- assange0-family.github.io
- Operator Validation
- Validated (24/24 relays)
- This Relay
- Validated (uri-rsa)
- Contact
- email:BMTY90VKYRQPUJZOTH[]Safe-mail.net url:https://assange0-family.github.io proof:uri-rsa ciissversion:2
Family Configuration
- Family Support
- Happy Families (24) — Has family-cert in server descriptor (guide) | View Full Family (23)
Happy Families (family-cert)
- Effective Members: 24
14E72D4DA10B66353E583F26EE04AC0D563EA7EF 1A5977013CF9DC0CC1D6C2643E3EABE6B82E2401 1BA2F9436C0018A4B52625D071B72F648522B748 1EB6BC4C65138A4FD1145823A89CA86CA6062E85 215616527FB97ED5BE0BF8D2166BDB44EEB6A840 21AC6EF15C86641CE623B8A08D64144BCAC14AEC 33AFED52DF25D8B1C85ED74B6A7783BB6DF067E5 4D5DC30956821797E5201C346ADBF29BBA4CA5A5 5412D862C7625F145E16D3D831F6D33A9FAF5EE9 5BC4625B1B8106FB3CC9CE1164E191CB675DF30C 659B6C695782B6206FF2D1166708DE9BA2E0F35C 6D4D5193A0E290C027FE6B66731133F70946A155 (this relay) 72F5D579CD039FF1FE1E08DAE2770648C3FA463E 77C7500CC573643E4B3E7F602D0137F8C89CE0B8 8AFFA6E447559943FE364EC1960D5AA5C5F06E9E 96275921105DC2D41B79AD75804A301738B51E47 9665A1A6EB9B98C57E446A483E75E05F0539B41B 96C7F178B1531825E82122DEFBFEF16E233A9328 ADB98B27D7A3FB5732068FD23602A1BCB3BE9F38 B91A1EB30E66D52026EFCD1E96BFC0E966C83E6D BB5630967607D8A8B6CA854AF954FE8372D1662A C6E3910CBADCA6D2D7E932AB31A038EDD6A6FB79 DD7BD3E5BD0BA48A8C70B0CDF017FA5988B87E27 DF86098968BBCD963E38E03FC3FC1837EF667C13
MyFamily (legacy declarations)
- Effective Members: 0
- none
- Alleged Member: 1
-
(they don't list you back)
8AFFA6E447559943FE364EC1960D5AA5C5F06E9E
- Indirect Members: 0
- none
- Platform
- Linux — Tor 0.4.9.14 on Linux
- Version
- 0.4.9.14 — Not Recommended
- Version Status
- Obsolete — Update urgently. See torproject.org/download
DNS Health
Not an exit relay — DNS health testing does not apply.Last fetch was at Wed, 04 Nov 2026 13:15:37 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-04 12:45:10).
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, Fast, Stable | 78.4 Mbit/s (M) | 816.0 Kbit/s | 78.4 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 99.7% | 98% | 20.2d | 8d | 13.5d | 8.4d | 21.4d | 5.2d | 2026-11-04 02:44:01 | 78.4 Mbit/s (M) |
| dannenberg (DE) | Yes | Yes | No | — | Y | Yes | Running, Valid, Fast, Stable | 112.0 Mbit/s (M) | 816.0 Kbit/s | 112.0 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s | 99.9% | 98% | 26.3d | 8d | 21.7d | 9.3d | 21.4d | 5.3d | 2026-11-04 02:44:01 | 112.0 Mbit/s (M) |
| dizum (NL) | Yes | Yes | No | — | N | Yes | Running, Valid, Fast, Stable | 80.0 Mbit/s (R) | 816.0 Kbit/s | 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 98.6% | 98% | 18.3d | 8d | 10.8d | 6.7d | 21.4d | 5.3d | 2026-11-04 02:44:01 | 80.0 Mbit/s (R) |
| faravahar (US) | Yes | Yes | No | — | Y | Yes | Running, Valid, Fast, Stable | 80.0 Mbit/s (R) | 816.0 Kbit/s | 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 99.8% | 98% | 19.9d | 8d | 11.2d | 6.5d | 21.4d | 5.3d | 2026-11-04 02:44:01 | 80.0 Mbit/s (R) |
| gabelmoo (DE) | Yes | Yes | No | — | Y | Yes | Running, Valid, Fast, Stable | 72.8 Mbit/s (M) | 816.0 Kbit/s | 72.8 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 26.0d | 8d | 21.2d | 10.8d | 21.4d | 5.3d | 2026-11-04 02:44:01 | 72.8 Mbit/s (M) |
| longclaw (US) | Yes | Yes | No | — | Y | Yes | Running, Valid, Fast, Stable | 80.0 Mbit/s (R) | 816.0 Kbit/s | 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 25.9d | 8d | 21.4d | 10.9d | 21.4d | 5.3d | 2026-11-04 02:44:01 | 80.0 Mbit/s (R) |
| maatuska (SE) | Yes | Yes | No | — | N | Yes | Running, Valid, Fast, Stable | 80.0 Mbit/s (R) | 816.0 Kbit/s | 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 99.6% | 98% | 18.8d | 8d | 5.8d | 2.4d | 21.4d | 5.3d | 2026-11-04 02:44:01 | 80.0 Mbit/s (R) |
| moria1 (US) | Yes | Yes | No | — | Y | Yes | Running, Valid, Fast, Stable | 104.0 Mbit/s (M) | 8.4 Mbit/s | 104.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 99.9% | 98% | 9.8d | 8d | 3667.5d | 7607.5d | 21.4d | 5.3d | 2026-11-04 02:44:01 | 104.0 Mbit/s (M) |
| tor26 (AT) | Yes | Yes | No | — | Y | Yes | Running, Valid, Fast, Stable | 96.0 Mbit/s (M) | 816.0 Kbit/s | 96.0 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 63.5d | 8d | 63.4d | 10.6d | 21.4d | 5.3d | 2026-11-04 02:44:01 | 96.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.