View Relay "steamedhams"

Fingerprint: DF46E2DDBC65AE072A12A27FA489B38677004D1E | Family: 1 relay | 0xFFFFFFFF Kraig Pidgeon <nobody AT dot com> | AS4764 | Australia | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Fast, Stable, HSDir, Exit (7)
DNS Health
Healthy (15.1s, 53rd percentile) (via exitdnshealth.1aeo.com)
BW Verified
5/7 BW Auths Measured 7 Mbit/s Median
Stability
Not Overloaded | UP 1w 6d 5h ago | UP 90% (1M)
Reachability
IPv4: 9/9 | v6: None configured(Directory Auths)
First Seen
1y 7mo 4d ago
BW Weight
0.00% of Network | 48 Mbit/s Observed By Relay
Version
0.4.9.13 Not Recommended
Issues Detected:
  • Guard: WFU below threshold : 0/9 authorities meet guard-wfu (≥98%; maatuska: ≥96.867%; 5 needed). bastet, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 measured 92.7%–97.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.
  • Tor version not recommended : Running Tor version 0.4.9.13 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.

Connectivity and Location

Addresses
OR Address
144.6.236.131:9002
Exit Address
144.6.236.131
Reachability (Directory Authorities)
IPv4
9/9
IPv6
None configured
Location
Country
Australia Australia
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS4764
AS Name
Aussie Fibre Pty Ltd (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 6 operators)

Flags and Eligibility

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: 8/9 | HSDir: 7/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) 4.9 Mbit/s – 17.6 Mbit/s (5 DA measured)
41.9 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 (1/9 DA) Median: 9.7d (1/9 DA above threshold)
Min/Max: 2.0d / 8333.2d (9/9 DA, Voting / Total Eligible)		 ≥2.7d - 11.8d (varies) (≥5/9 DA)
[Stricter] moria1: ≥6299.4d
Uptime Meets (9/9 DA) 13.2d (R) ≥4.2d - 4.3d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
4.9 Mbit/s – 17.6 Mbit/s (5 DA measured)
41.9 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.7d - 11.8d (varies) (≥5/9 DA)
[Stricter] moria1: ≥6299.4d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Uptime Partial (8/9 DA) 13.2d (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
4.9 Mbit/s – 17.6 Mbit/s (5 DA measured)
41.9 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.7d - 11.8d (varies) (≥5/9 DA)
[Stricter] moria1: ≥6299.4d
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.5% (0/9 DA above threshold)
Min/Max: 92.7% / 97.0% (9/9 DA, Voting / Total Eligible)		 ≥98%; maatuska: ≥96.867% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 16.0d (9/9 DA above threshold)
Min/Max: 9.9d / 16.9d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Partial (5/9 DA) 4.9 Mbit/s – 17.6 Mbit/s (5 DA measured)
41.9 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 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-09 15:45:06).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
48.62 Mbit/s
Advertised Bandwidth
41.94 Mbit/s
Rate Limit
41.94 Mbit/s
Burst Limit
83.89 Mbit/s
Total Data
76 TB (6 months)
1mo: 14 TB | 6mo: 76 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-09 15:45:06

Measured By
5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Consensus Weight
7.1 Mbit/s (median of 5 measurements)
Measured Min / Max
4.9 Mbit/s / 17.6 Mbit/s
Deviation
12.7 Mbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0004% of network (13th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0011% (3th pctl)
History
Throughput and write/read, last 6 months Throughput and write/read, last 30 days
1M 6M

Uptime and Stability

Uptime Metrics
Current Status
UP 1w 6d 5h ago
Overall Uptime (1M/6M/1Y/5Y)
90.6%/89.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (90.6%/89.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
1y 7mo 4d ago (2025-04-09 13:00:00)
Last Seen
1h 45m 15s ago (2026-11-09 15:00:00)
Last Restarted
1w 6d 5h ago (2026-10-27 11:13:48)
Last Changed Address
2026-06-22 03:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Evaluated 2026-11-09 16:45 UTC. /details snapshot 2026-11-09 15:00:00 UTC (cached 17s ago). /bandwidth snapshot 2026-11-09 12:00:00 UTC (cached 3h 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 6 months Uptime, last 30 days
1M 6M

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-11-09 08:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
0xFFFFFFFF Kraig Pidgeon <nobody AT 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 
DF46E2DDBC65AE072A12A27FA489B38677004D1E (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

Platform
Linux — Tor 0.4.9.13 on Linux
Version
0.4.9.13 — Not Recommended
Version Status
Obsolete — Update urgently. See torproject.org/download

Exit Health & Policy

DNS Health
Status
Healthy (avg. 15.1s, 53rd percentile)
Query Domain
52d8d52742844527ab9ae4affab8f09b.df46e2dd.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Upstream Resolver
Other
Other 95%, Local AS 5% (~89 estimated queries)
Cross-Validation
3/4 instances succeeded (improved by cross-validation)
First Hop
DFRI136 (SE) 3F4BE2F523ECE5A9A4D9D99431DAD7E9EC4ABC0E
Exit Address Used
144.6.236.131
Per-Instance Results
Cross Validation Attempt 1: DNS Fail, 16.9s (cv1_w3)
Cross Validation Attempt 2: Success, 12.8s (cv2_w3)
Cross Validation Attempt 3: Success, 15.9s (cv3_w3)
Cross Validation Attempt 4: Success, 16.6s (cv4_w3)
Tested: 2026-11-09 08:14:52 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
reject: 
  25
  119
  135-139
  445
  563
  1214
  4661-4666
  6346-6429
  6699
  6881-6999
IPv6 Exit Policy Summary
reject: 
  25
  119
  135-139
  445
  563
  1214
  4661-4666
  6346-6429
  6699
  6881-6999
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 144.6.236.131:*
reject 129.94.0.0/16:*
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 *:*

Last fetch was at Mon, 09 Nov 2026 16:45:14 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-11-09 15:45:06).

Per-Authority Details

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 Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 13.6 Mbit/s (M) | 816.0 Kbit/s 13.6 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s 95.2% | 98% 15.1d | 8d 7.4d | 9.7d 13.2d | 5.7d 2026-11-06 00:05:39 13.6 Mbit/s (M)
dannenberg (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 4.9 Mbit/s (M) | 816.0 Kbit/s 4.9 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s 96.9% | 98% 16.8d | 8d 9.9d | 11.8d 13.2d | 4.3d 2026-11-09 00:07:42 4.9 Mbit/s (M)
dizum (NL) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 41.9 Mbit/s (R) | 816.0 Kbit/s 41.9 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 95.9% | 98% 16.0d | 8d 7.9d | 9.4d 13.2d | 4.3d 2026-11-09 00:07:42 41.9 Mbit/s (R)
faravahar (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 41.9 Mbit/s (R) | 816.0 Kbit/s 41.9 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 96.5% | 98% 14.4d | 8d 6.9d | 8.7d 13.2d | 4.3d 2026-11-09 00:07:42 41.9 Mbit/s (R)
gabelmoo (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 5.4 Mbit/s (M) | 816.0 Kbit/s 5.4 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 97.0% | 98% 16.9d | 8d 9.8d | 13.4d 13.2d | 4.3d 2026-11-09 00:07:42 5.4 Mbit/s (M)
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 41.9 Mbit/s (R) | 816.0 Kbit/s 41.9 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 96.9% | 98% 16.9d | 8d 9.8d | 13.7d 13.2d | 4.3d 2026-11-09 00:07:42 41.9 Mbit/s (R)
maatuska (SE) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Exit 41.9 Mbit/s (R) | 816.0 Kbit/s 41.9 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 92.7% | 97% 12.5d | 8d 2.0d | 2.7d 13.2d | 4.3d 2026-11-09 00:07:42 41.9 Mbit/s (R)
moria1 (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, Exit 17.6 Mbit/s (M) | 8.4 Mbit/s 17.6 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s 95.3% | 98% 9.9d | 8d 8333.2d | 6299.4d 13.2d | 4.3d 2026-11-09 00:07:42 17.6 Mbit/s (M)
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 7.1 Mbit/s (M) | 816.0 Kbit/s 7.1 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s 96.9% | 98% 16.9d | 8d 9.7d | 13.3d 13.2d | 4.2d 2026-11-09 00:07:42 7.1 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.