View Relay "TakTor03"

Fingerprint: 1D65771E68383F294D4F1131B19DF64989EEDF8A | Family: 1 relay | ContactInfo... | AS36352 | United States of America | Linux

Consensus
In Consensus (9/9 Directory Auths)
DNS Health
Healthy (17.9s, 83rd percentile) (via exitdnshealth.1aeo.com)
BW Verified
6/7 BW Auths Measured 8 Mbit/s Median
Stability
Not Overloaded | UP 2d 11h 37m ago | UP 98% (1M)
Reachability
IPv4: 9/9 | v6: None configured(Directory Auths)
BW Weight
0.00% of Network | 21 Mbit/s Observed By Relay
Version
0.4.9.17 Recommended
Issues Detected:
  • Guard: bandwidth below threshold : 2/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). dannenberg, gabelmoo, longclaw and tor26 measured this relay at 8.8 Mbit/s. dizum, faravahar and maatuska used the relay-reported 14.8 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 76.4%–92.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
tor03.mtak.nl
198.46.166.157:443
Exit Address
198.46.166.157
Reachability (Directory Authorities)
IPv4
9/9
IPv6
None configured
Location
Country
United States of America United States of America
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS36352
AS Name
HostPapa (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.29% consensus weight, 62 operators)

Current Flags (7): Running, Valid, V2Dir, Fast, Stable, HSDir, Exit
Eligible Flags (7): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 6/9 | HSDir: 5/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 Meets (9/9 DA) 8.8 Mbit/s – 20.0 Mbit/s (6 DA measured)
14.8 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 Below (2/9 DA) Median: 5.0d (1/9 DA above threshold)
Min/Max: 2.7d / 14323.8d (9/9 DA, Voting / Total Eligible)
≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12669.7d
Uptime Below (0/9 DA) 2.5d (R) ≥5.0d - 5.1d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
8.8 Mbit/s – 20.0 Mbit/s (6 DA measured)
14.8 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 (6/9 DA) 6/9 DA assigned Stable ≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12669.7d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Uptime Partial (5/9 DA) 2.5d (R) ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA)
[Stricter] moria1: ≥98% WFU and ≥9.7d Time Known
Guard Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
8.8 Mbit/s – 20.0 Mbit/s (6 DA measured)
14.8 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 (6/9 DA) 6/9 DA assigned Stable ≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12669.7d
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: 82.6% (1/9 DA above threshold)
Min/Max: 76.4% / 98.6% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 16.0d (9/9 DA above threshold)
Min/Max: 5.7d / 18.1d (9/9 DA, Voting / Total Eligible)
≥8 days; E30CF7B3: ≥5 days 10 hours 41 minutes 56 seconds (≥5/9 DA)
Bandwidth Below (2/9 DA) 8.8 Mbit/s – 20.0 Mbit/s (6 DA measured)
14.8 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 08:45:05).

Capacity (Relay Reported)
Observed Bandwidth
21.52 Mbit/s
Advertised Bandwidth
14.81 Mbit/s
Rate Limit
14.81 Mbit/s
Burst Limit
59.24 Mbit/s
Total Data
2.8 TB (6 months)
1mo: 2.8 TB | 6mo: 2.8 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-20 08:45:05

Measured By
6/7 Bandwidth Authorities
Not measured by: faravahar
Consensus Weight
8.8 Mbit/s (median of 6 measurements)
Measured Min / Max
8.8 Mbit/s / 20.0 Mbit/s
Deviation
11.2 Mbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0006% of network (14th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0019% (3th pctl)
History
Throughput and write/read, last 6 months Throughput and write/read, last 30 days
1M 6M

Uptime Metrics
Current Status
UP 2d 11h 37m ago
Overall Uptime (1M/6M/1Y/5Y)
98.9%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (98.9%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
3w 6d 11h ago (2026-10-23 22:00:00)
Last Seen
1h 45m 32s ago (2026-11-20 08:00:00)
Last Restarted
2d 11h 37m ago (2026-11-17 22:07:34)
Last Changed Address
2026-10-23 22:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Evaluated 2026-11-20 09:45 UTC. /details snapshot 2026-11-20 08:00:00 UTC (cached 37s ago). /bandwidth snapshot 2026-11-20 02:00:00 UTC (cached 6h 30m 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
ContactInfo email:tak.tor.operator[]gmail.com url:https://tak.io/ keybase:mtak dnslocation:local dnsqname:y dnssec:y ciissversion:2
Family Configuration
Family Support
Happy Families (3) — Has family-cert in server descriptor (guide)
Happy Families (family-cert)
Effective Members: 3
1D65771E68383F294D4F1131B19DF64989EEDF8A (this relay)
69042D0DC33BD810BD08ADADBC7E95A3CABAEF64
8696DC7AC0470F6ED5C7AC48030002D7D3716FC9
MyFamily (legacy declarations) — none

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

DNS Health
Status
Healthy (avg. 17.9s, 83rd percentile)
Query Domain
0854049162d24febbb1121b103e2d25c.1d65771e.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Upstream Resolver
Local /24 (exit's own network)
Local /24 100% (~49 estimated queries)
Cross-Validation
4/4 instances succeeded
First Hop
tr35 (DE) 39130398A173638285D216A95B3D64AE0B3FF750
Exit Address Used
198.46.166.157
Per-Instance Results
Cross Validation Attempt 1: Success, 20.8s (cv1_w1)
Cross Validation Attempt 2: Success, 11.8s (cv2_w1)
Cross Validation Attempt 3: Success, 20.6s (cv3_w1)
Cross Validation Attempt 4: Success, 18.5s (cv4_w1)
Tested: 2026-11-19 20:05:34 UTC
IPv4 Exit Policy Summary
accept: 
  53
  80
  443
  993
  995
  1194
  11371
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 198.46.166.157:*
accept *:53
accept *:80
accept *:443
accept *:993
accept *:995
accept *:1194
accept *:11371
reject *:*

Last fetch was at Fri, 20 Nov 2026 09:45:32 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-11-20 08:45: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, Exit 16.8 Mbit/s (M) | 816.0 Kbit/s 16.8 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s 98.6% | 98% 5.7d | 5d 2.7d | 3.9d 2.5d | 5.1d 2026-11-20 04:07:43 16.8 Mbit/s (M)
dannenberg (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 8.8 Mbit/s (M) | 816.0 Kbit/s 8.8 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 85.6% | 98% 17.2d | 8d 4.8d | 8.2d 2.5d | 5.1d 2026-11-20 04:07:43 8.8 Mbit/s (M)
dizum (NL) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 14.8 Mbit/s (R) | 816.0 Kbit/s 14.8 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 83.2% | 98% 16.0d | 8d 5.0d | 6.8d 2.5d | 5.1d 2026-11-20 04:07:43 14.8 Mbit/s (R)
faravahar (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 14.8 Mbit/s (R) | 816.0 Kbit/s 14.8 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 79.7% | 98% 16.0d | 8d 4.8d | 7.0d 2.5d | 5.1d 2026-11-20 04:07:43 14.8 Mbit/s (R)
gabelmoo (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 8.8 Mbit/s (M) | 816.0 Kbit/s 8.8 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 82.1% | 98% 18.1d | 8d 5.8d | 8.3d 2.5d | 5.1d 2026-11-20 04:07:43 8.8 Mbit/s (M)
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 8.8 Mbit/s (M) | 816.0 Kbit/s 8.8 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 81.9% | 98% 18.0d | 8d 5.9d | 9.1d 2.5d | 5.1d 2026-11-20 04:07:43 8.8 Mbit/s (M)
maatuska (SE) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 14.8 Mbit/s (R) | 816.0 Kbit/s 14.8 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 76.4% | 98% 14.8d | 8d 2.9d | 2.3d 2.5d | 5.1d 2026-11-20 04:07:43 14.8 Mbit/s (R)
moria1 (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, Exit 20.0 Mbit/s (M) | 8.4 Mbit/s 20.0 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s 92.0% | 98% 9.9d | 8d 14323.8d | 12669.7d 2.5d | 5.0d 2026-11-20 04:07:43 20.0 Mbit/s (M)
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 8.8 Mbit/s (M) | 816.0 Kbit/s 8.8 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 82.6% | 98% 17.8d | 8d 5.9d | 8.2d 2.5d | 5.1d 2026-11-20 04:07:43 8.8 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 (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.