View Relay "tweakin"

Fingerprint: D21972155E26E2DEF4977D110CA9244ECBF6C34E | Family: 2 relays | Jeff Burrows Jeff@privacywarrior.org | AS44925 | Iceland | Linux

Consensus
In Consensus (9/9 Directory Auths)
DNS Health
Healthy (13.4s, 29th percentile) (via exitdnshealth.1aeo.com)
BW Verified
5/7 BW Auths Measured 52 Mbit/s Median
Stability
Not Overloaded | UP 6d 2h 49m ago | UP 100% (1M)
Reachability
IPv4: 9/9 | v6: None configured(Directory Auths)
BW Weight
0.00% of Network | 56 Mbit/s Observed By Relay
Version
0.4.9.15 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 because DirCache 0 is set in torrc.
    Suggestion: Remove DirCache 0 from torrc (DirCache is enabled by default in Tor ≥0.3.3). Restart Tor and verify the descriptor includes tunnelled-dir-server. You can check with: grep tunnelled-dir-server /var/lib/tor/cached-descriptors

Addresses
OR Address
89.147.110.82:9001
Exit Address
89.147.110.82
Reachability (Directory Authorities)
IPv4
9/9
IPv6
None configured
Location
Country
Iceland Iceland
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS44925
AS Name
1984 ehf (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.09% consensus weight, 13 operators)

Current Flags (5): Running, Valid, Fast, Stable, Exit
Eligible Flags (6): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 9/9 | HSDir: 0/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 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) 40.8 Mbit/s – 63.2 Mbit/s (5 DA measured)
45.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 Partial (8/9 DA) Median: 106.7d (8/9 DA above threshold)
Min/Max: 7.5d / 550.5d (9/9 DA, Voting / Total Eligible)
≥2.4d - 9.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7607.5d
Uptime Meets (9/9 DA) 6.1d (R) ≥5.2d - 5.3d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
40.8 Mbit/s – 63.2 Mbit/s (5 DA measured)
45.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 (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) 6.1d (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
40.8 Mbit/s – 63.2 Mbit/s (5 DA measured)
45.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 (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: 100.0% (9/9 DA above threshold)
Min/Med/Max: 99.6% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)
≥98%; dizum: ≥97.84099999999999% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 85.5d (9/9 DA above threshold)
Min/Max: 10.0d / 550.1d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 40.8 Mbit/s – 63.2 Mbit/s (5 DA measured)
45.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-04 12:45:10).

Capacity (Relay Reported)
Observed Bandwidth
56.06 Mbit/s
Advertised Bandwidth
45.88 Mbit/s
Rate Limit
45.88 Mbit/s
Burst Limit
91.75 Mbit/s
Total Data
258 TB (5 years)
1mo: 14 TB | 6mo: 65 TB | 1y: 111 TB | 5y: 258 TB
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
52.0 Mbit/s (median of 5 measurements)
Measured Min / Max
40.8 Mbit/s / 63.2 Mbit/s
Network Participation: Consensus Weight: 0.0028% of network (35th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0092% (11th pctl)
History

Uptime Metrics
Current Status
UP 6d 2h 49m ago
Overall Uptime (1M/6M/1Y/5Y)
100.0%/100.0%/100.0%/90.6%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (100.0%/100.0%/100.0%/90.6%)
Hibernating
No
Timestamps
First Seen
2y 10mo 2d ago (2024-01-07 00:00:00)
Last Seen
2h 45m 39s ago (2026-11-04 11:00:00)
Last Restarted
6d 2h 49m ago (2026-10-29 10:56:25)
Last Changed Address
2026-04-06 23:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Evaluated 2026-11-04 13:45 UTC. /details snapshot 2026-11-04 11:00:00 UTC (cached 42s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 6h 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

Operator Identity

Source: AROI Validation API — 2026-11-04 04:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
Jeff Burrows Jeff@privacywarrior.org
Family Configuration
Family Support
Happy Families (2) — Has family-cert in server descriptor (guide) | View Full Family (2)
Happy Families (family-cert)
Effective Members: 2
9DFF7F006FA33615DADD4EA775E1CEF73E7D7630
D21972155E26E2DEF4977D110CA9244ECBF6C34E (this relay)
MyFamily (legacy declarations) — none

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

DNS Health
Status
Healthy (avg. 13.4s, 29th percentile)
Query Domain
645fdcc791c34c0a99095346173fd61d.d2197215.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Upstream Resolver
Google (public resolver)
Google 100% (~31 estimated queries)
Cross-Validation
4/4 instances succeeded
First Hop
gnosti (GB) 462C4C97170DE94F251A46F4C741032864AD1BFB
Exit Address Used
89.147.110.82
Per-Instance Results
Cross Validation Attempt 1: Success, 15.7s (cv1_w3)
Cross Validation Attempt 2: Success, 17.3s (cv2_w3)
Cross Validation Attempt 3: Success, 9.1s (cv3_w3)
Cross Validation Attempt 4: Success, 11.5s (cv4_w3)
Tested: 2026-11-03 20:15:24 UTC
IPv4 Exit Policy Summary
accept: 
  20-21
  43
  53
  80
  110
  143
  220
  443
  873
  989-993
  995
  1194
  1293
  3690
  4321
  5222-5223
  5228
  9418
  11371
  64738
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 89.147.110.82:*
accept *:20-21
accept *:43
accept *:53
accept *:80
accept *:110
accept *:143
accept *:220
accept *:443
accept *:873
accept *:989-990
accept *:991
accept *:992
accept *:993
accept *:995
accept *:1194
accept *:1293
accept *:3690
accept *:4321
accept *:5222-5223
accept *:5228
accept *:9418
accept *:11371
accept *:64738
reject *:*

Last fetch was at Wed, 04 Nov 2026 13:45:39 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 Yes — Y Yes Running, Valid, Fast, Stable, Exit 56.0 Mbit/s (M) | 816.0 Kbit/s 56.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 99.9% | 98% 33.2d | 8d 26.3d | 8.4d 6.1d | 5.2d 2026-11-03 16:58:11 56.0 Mbit/s (M)
dannenberg (DE) Yes Yes Yes — Y Yes Running, Valid, Fast, Stable, Exit 44.8 Mbit/s (M) | 816.0 Kbit/s 44.8 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 124.7d | 8d 124.7d | 9.3d 6.1d | 5.3d 2026-11-04 10:58:26 44.8 Mbit/s (M)
dizum (NL) Yes Yes Yes — N Yes Running, Valid, Fast, Stable, Exit 45.9 Mbit/s (R) | 816.0 Kbit/s 45.9 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.7% | 98% 85.5d | 8d 58.2d | 6.7d 6.1d | 5.3d 2026-11-04 10:58:26 45.9 Mbit/s (R)
faravahar (US) Yes Yes Yes — Y Yes Running, Valid, Fast, Stable, Exit 45.9 Mbit/s (R) | 816.0 Kbit/s 45.9 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 80.3d | 8d 49.3d | 6.5d 6.1d | 5.3d 2026-11-04 10:58:26 45.9 Mbit/s (R)
gabelmoo (DE) Yes Yes Yes — Y Yes Running, Valid, Fast, Stable, Exit 40.8 Mbit/s (M) | 816.0 Kbit/s 40.8 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 106.7d | 8d 106.7d | 10.8d 6.1d | 5.3d 2026-11-04 10:58:26 40.8 Mbit/s (M)
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, Fast, Stable, Exit 45.9 Mbit/s (R) | 816.0 Kbit/s 45.9 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 533.9d | 8d 533.9d | 10.9d 6.1d | 5.3d 2026-11-03 16:58:11 45.9 Mbit/s (R)
maatuska (SE) Yes Yes Yes — N Yes Running, Valid, Fast, Stable, Exit 45.9 Mbit/s (R) | 816.0 Kbit/s 45.9 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.6% | 98% 48.3d | 8d 7.5d | 2.4d 6.1d | 5.3d 2026-11-04 10:58:26 45.9 Mbit/s (R)
moria1 (US) Yes Yes Yes — Y Yes Running, Valid, Fast, Stable, Exit 63.2 Mbit/s (M) | 8.4 Mbit/s 63.2 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 10.0d | 8d 550.5d | 7607.5d 6.1d | 5.3d 2026-11-04 10:58:26 63.2 Mbit/s (M)
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, Fast, Stable, Exit 52.0 Mbit/s (M) | 816.0 Kbit/s 52.0 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 550.1d | 8d 550.1d | 10.6d 6.1d | 5.3d 2026-11-04 10:58:26 52.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 (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.