View Relay "tspio"

Fingerprint: 1532A36172C70012B1057FBBFAFE2734EDBF4A3B | Family: 1 relay | 4096R/7176DC71 Jon Gjengset... | AS43927 | Netherlands | Linux

Consensus
In Consensus (9/9 Directory Auths)
DNS Health
Healthy (15.0s, 45th percentile) (via exitdnshealth.1aeo.com)
BW Verified
6/7 BW Auths Measured 960 Kbit/s Median
Stability
Not Overloaded | UP 4d 21h 23m ago | UP 99% (1M)
Reachability
IPv4: 9/9 | v6: None configured(Directory Auths)
BW Weight
0.00% of Network | 6 Mbit/s Observed By Relay
Version
0.4.9.16 Recommended
Issues Detected:
  • 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 – 248.0 Mbit/s). E30CF7B3, dannenberg, gabelmoo, longclaw, moria1 and tor26 measured this relay at 880.0 Kbit/s – 2.7 Mbit/s. dizum, faravahar and maatuska used the relay-reported 4.9 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 : 1/9 authorities meet guard-wfu (≥98%; 5 needed). dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 measured 70.6%–90.0%.
    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.
  • 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.81.247.72:993
Exit Address
77.81.247.72
Reachability (Directory Authorities)
IPv4
9/9
IPv6
None configured
Location
Country
Netherlands Netherlands
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS43927
AS Name
HOSTERION SRL (BGP.tools)
AS Rarity
Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

Current Flags (7): Running, Valid, V2Dir, Fast, Stable, HSDir, Exit
Eligible Flags (7): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 8/9 | Stable: 9/9 | HSDir: 8/9 | Guard: 0/9 | Exit: 9/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 Partial (8/9 DA) 880.0 Kbit/s – 2.7 Mbit/s (6 DA measured)
4.9 Mbit/s (3 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: 10.2d (6/9 DA above threshold)
Min/Max: 3.7d / 8293.1d (9/9 DA, Voting / Total Eligible)
≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12663.9d
Uptime Below (0/9 DA) 4.9d (R) ≥5.0d - 5.1d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (8/9 DA) 8/9 DA assigned Fast
880.0 Kbit/s – 2.7 Mbit/s (6 DA measured)
4.9 Mbit/s (3 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.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12663.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) 4.9d (R) ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA)
[Stricter] moria1: ≥98% WFU and ≥9.6d Time Known
Guard Prereq: Fast Meets (8/9 DA) 8/9 DA assigned Fast
880.0 Kbit/s – 2.7 Mbit/s (6 DA measured)
4.9 Mbit/s (3 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.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12663.9d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (1/9 DA) Median: 76.6% (1/9 DA above threshold)
Min/Max: 70.6% / 100.0% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 19.6d (9/9 DA above threshold)
Min/Max: 6.8d / 28.0d (9/9 DA, Voting / Total Eligible)
≥8 days; E30CF7B3: ≥5 days 11 hours 43 minutes 50 seconds (≥5/9 DA)
Bandwidth Below (0/9 DA) 880.0 Kbit/s – 2.7 Mbit/s (6 DA measured)
4.9 Mbit/s (3 DA relay-reported)
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-248.0 Mbit/s) (≥5/9 DA)
Exit Exit Policy Meets (9/9 DA) Port 80: Yes | Port 443: Yes (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-20 10:15:05).

Capacity (Relay Reported)
Observed Bandwidth
6.38 Mbit/s
Advertised Bandwidth
4.92 Mbit/s
Rate Limit
4.92 Mbit/s
Burst Limit
5.73 Mbit/s
Total Data
1.4 TB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-20 10:15:05

Measured By
6/7 Bandwidth Authorities
Not measured by: faravahar
Consensus Weight
960.0 Kbit/s (median of 6 measurements)
Measured Min / Max
880.0 Kbit/s / 2.7 Mbit/s
Deviation
1.8 Mbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0001% of network (6th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0002% (2th pctl)
History
Throughput and write/read, last 30 days

Uptime Metrics
Current Status
UP 4d 21h 23m ago
Overall Uptime (1M/6M/1Y/5Y)
99.8%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (99.8%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
3w 2d 11h ago (2026-10-27 23:00:00)
Last Seen
1h 15m 38s ago (2026-11-20 09:00:00)
Last Restarted
4d 21h 23m ago (2026-11-15 12:51:39)
Last Changed Address
2026-10-27 23:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Evaluated 2026-11-20 10:15 UTC. /details snapshot 2026-11-20 09:00:00 UTC (cached 14s ago). /bandwidth snapshot 2026-11-20 02:00:00 UTC (cached 7h ago).

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
No rate-limit report in available data
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
History
Uptime, last 30 days

Operator Identity

Source: AROI Validation API — 2026-11-19 23:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
4096R/7176DC71 Jon Gjengset <jon@tsp.io> - 1KMjEjoQerKAMJ1ca95pXzCRzZsEhSpjAt
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1
1532A36172C70012B1057FBBFAFE2734EDBF4A3B (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Platform
Linux — Tor 0.4.9.16 on Linux
Version
0.4.9.16 — Recommended
Version Status
Recommended

DNS Health
Status
Healthy (avg. 15.0s, 45th percentile)
Query Domain
b776f634c7fb4d348f20cdfe880e9cb3.1532a361.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Upstream Resolver
Not enough data
Other 59%, Google 41% (~21 estimated queries)
Cross-Validation
2/4 instances succeeded (improved by cross-validation)
First Hop
NTH61R1 (NL) 4EF90C045937B75E9C659E0B4BD289226ACE0941
Exit Address Used
77.81.247.72
Per-Instance Results
Cross Validation Attempt 1: Success, 14.8s (cv1_w1)
Cross Validation Attempt 2: DNS Fail, 18.7s (cv2_w1)
Cross Validation Attempt 3: Success, 15.1s (cv3_w1)
Cross Validation Attempt 4: DNS Fail, 18.4s (cv4_w1)
Tested: 2026-11-19 20:05:46 UTC
IPv4 Exit Policy Summary
accept: 
  22-23
  43
  53
  79-81
  110
  143
  194
  220
  443
  531
  873
  981
  989-995
  1194
  2086-2087
  3128
  3690
  4321
  5222-5223
  5228
  6660-6669
  6679
  6697
  8008
  8080
  8888
  9418
  11371
  19294
IPv6 Exit Policy Summary
None
Full Exit Policy
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.81.247.72:*
accept *:22-23
accept *:43
accept *:53
accept *:79-81
accept *:110
accept *:143
accept *:194
accept *:220
accept *:443
accept *:531
accept *:873
accept *:981
accept *:989-995
accept *:1194
accept *:2086-2087
accept *:3128
accept *:3690
accept *:4321
accept *:5222-5223
accept *:5228
accept *:6660-6669
accept *:6679
accept *:6697
accept *:8008
accept *:8080
accept *:8888
accept *:9418
accept *:11371
accept *:19294
reject *:*

Last fetch was at Fri, 20 Nov 2026 10:15:38 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-11-20 10: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) Desc Published Cons Wt (Authority)
E30CF7B3 Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 2.7 Mbit/s (M) | 816.0 Kbit/s 2.7 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 6.8d | 5d 6.8d | 3.9d 4.9d | 5.1d 2026-11-20 00:51:49 2.7 Mbit/s (M)
dannenberg (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 1.1 Mbit/s (M) | 816.0 Kbit/s 1.1 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 83.5% | 98% 28.0d | 8d 23.4d | 8.2d 4.9d | 5.1d 2026-11-20 00:51:49 1.1 Mbit/s (M)
dizum (NL) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 4.9 Mbit/s (R) | 816.0 Kbit/s 4.9 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 73.7% | 98% 18.8d | 8d 6.9d | 6.8d 4.9d | 5.1d 2026-11-20 00:51:49 4.9 Mbit/s (R)
faravahar (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 4.9 Mbit/s (R) | 816.0 Kbit/s 4.9 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 81.9% | 98% 25.6d | 8d 18.6d | 7.0d 4.9d | 5.1d 2026-11-20 00:51:49 4.9 Mbit/s (R)
gabelmoo (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 880.0 Kbit/s (M) | 816.0 Kbit/s 880.0 Kbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 76.3% | 98% 19.6d | 8d 10.1d | 8.3d 4.9d | 5.1d 2026-11-20 00:51:49 880.0 Kbit/s (M)
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 960.0 Kbit/s (M) | 816.0 Kbit/s 960.0 Kbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 76.6% | 98% 19.8d | 8d 10.2d | 9.1d 4.9d | 5.1d 2026-11-20 00:51:49 960.0 Kbit/s (M)
maatuska (SE) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 4.9 Mbit/s (R) | 816.0 Kbit/s 4.9 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 70.6% | 98% 16.4d | 8d 3.7d | 2.3d 4.9d | 5.1d 2026-11-20 00:51:49 4.9 Mbit/s (R)
moria1 (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Stable, Exit 2.5 Mbit/s (M) | 8.4 Mbit/s 2.5 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s 90.0% | 98% 9.8d | 8d 8293.1d | 12663.9d 4.9d | 5.0d 2026-11-20 00:51:49 2.5 Mbit/s (M)
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 880.0 Kbit/s (M) | 816.0 Kbit/s 880.0 Kbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 76.5% | 98% 19.9d | 8d 10.2d | 8.3d 4.9d | 5.1d 2026-11-20 00:51:49 880.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 (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.