View Relay "9g4net7"

Fingerprint: `F0970FACC30D72673C54FC7A88DAE0E30B019196` | Family: 2 relays | tor@9g4.net | AS8560 | United States of America | Linux

Health Status

Consensus: In Consensus (10/10 Directory Auths)
Flags: Running, Valid, V2Dir, Fast, Stable, Guard (6)
BW Verified: 5/8 BW Auths Measured 45 Mbit/s Median
Stability: Not Overloaded | UP 2h 52m 57s ago | UP 100% (1M)

Reachability: IPv4: 10/10 | v6: 9/9(Directory Auths)
First Seen: 6mo 5d 1h ago
BW Weight: 0.00% of Network | 64 Mbit/s Observed By Relay
Version: 0.4.9.6 Not Recommended

Issues Detected:

HSDir: uptime below 96 hours : Only 0/10 authorities voted HSDir, though this relay has Fast, Stable and V2Dir
Suggestion: HSDir needs 96 hours of uptime as each authority sees it (MinUptimeHidServDirectoryV2): the time since your relay restarted, or since that authority last failed to reach it if that is shorter. Keep the relay running and reachable.
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.6 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.

Notes:

Guard: Time Known near threshold: Time Known is just above the Guard bar at 5947BB57 (2275 seconds, need ≥37 minutes 34 seconds) and E30CF7B3 (2.1 days, need ≥2 days 13 minutes 8 seconds). This is weighted time, so the day count is shorter than calendar uptime, and it falls while the relay is unreachable. Stay reachable so it can move clear of the bar.
Suggestion: Weighted time-known falls while the relay is unreachable and resets if the identity key changes. Authorities cap it at 8 days (AuthDirVoteGuardGuaranteeTimeKnown), about a few weeks of continuous uptime. Stay up with the same key.

Connectivity and Location

Addresses

OR Address: ip74-208-155-31.pbiaas.com
74.208.155.31:443
[2607:f1c0:f09f:2e00::1]:443

Reachability (Directory Authorities)

IPv4: 10/10
IPv6: 9/9 (1 don't test)

Location

Country: United States of America
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS8560
AS Name: IONOS SE (BGP.tools)
AS Rarity: Emerging (score: 1/5, 3.30% consensus weight, 153 operators)

Flags and Eligibility

Current Flags (6): Running, Valid, V2Dir, Fast, Stable, Guard

Eligibility Flag Vote Details

Flag	Metric	Status	Relay Value	Threshold Required
Running	IPv4 Reachability	Meets (10/10 DA)	10/10 authorities reached relay	≥6/10 DA ORPort reachable
Running	IPv6 Reachability	Meets (9/9 DA)	9/9 tested authorities reached relay	≥5/9 tested (majority) (≥5/9 DA)
Valid	Descriptor	Meets (10/10 DA)	10/10 authorities assigned Valid	Not blacklisted + valid descriptor (≥6/10 DA)
V2Dir	DirPort Available	Meets (10/10 DA)	Tunnelled: Yes (no DirPort) (R)	Tunnelled directory via ORPort or DirPort (≥6/10 DA)
Fast	Speed	Meets (10/10 DA)	24.8 Mbit/s – 168.0 Mbit/s (5 DA measured) 64.9 Mbit/s (5 DA relay-reported)	≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥6/10 DA) [Stricter] moria1: ≥8.4 Mbit/s
Stable	MTBF	Partial (9/10 DA)	Median: 44.7d (7/10 DA above threshold) Min/Max: 0.0d / 184.9d (10/10 DA, Voting / Total Eligible)	≥0.0d - 8.7d (varies) (≥6/10 DA) [Stricter] moria1: ≥10768.2d
Stable	Uptime	Below (0/10 DA)	0.1d (R)	≥2.0d - 2.4d (varies) (≥6/10 DA) [Stricter] 5947BB57: ≥5.9d
HSDir	Prereq: Fast	Meets (10/10 DA)	10/10 DA assigned Fast 24.8 Mbit/s – 168.0 Mbit/s (5 DA measured) 64.9 Mbit/s (5 DA relay-reported)	≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥6/10 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Meets (9/10 DA)	9/10 DA assigned Stable	≥0.0d - 8.7d (varies) (≥6/10 DA) [Stricter] moria1: ≥10768.2d
	Prereq: V2Dir	Meets (10/10 DA)	10/10 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥6/10 DA)
	Uptime	Below (0/10 DA)	0.1d (R)	≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥6/10 DA) [Stricter] moria1: ≥98% WFU and ≥9.7d Time Known
Guard	Prereq: Fast	Meets (10/10 DA)	10/10 DA assigned Fast 24.8 Mbit/s – 168.0 Mbit/s (5 DA measured) 64.9 Mbit/s (5 DA relay-reported)	≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥6/10 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Meets (9/10 DA)	9/10 DA assigned Stable	≥0.0d - 8.7d (varies) (≥6/10 DA) [Stricter] moria1: ≥10768.2d
	Prereq: V2Dir	Meets (10/10 DA)	10/10 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥6/10 DA)
	WFU	Meets (10/10 DA)	Median: 100.0% (10/10 DA above threshold) Min/Med/Max: 98.8% / 100.0% / 100.0% (10/10 DA, Voting / Total Eligible)	≥98%; maatuska: ≥97.051% (≥6/10 DA)
	Time Known	Meets (10/10 DA)	Median: 42.8d (10/10 DA above threshold) Min/Max: 0.0d / 184.6d (10/10 DA, Voting / Total Eligible)	≥8 days; 5947BB57: ≥37 minutes 34 seconds; E30CF7B3: ≥2 days 13 minutes 8 seconds (≥6/10 DA)
	Bandwidth	Meets (10/10 DA)	24.8 Mbit/s – 168.0 Mbit/s (5 DA measured) 64.9 Mbit/s (5 DA relay-reported)	≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-256.0 Mbit/s) (≥6/10 DA)
Exit	Exit Policy	Below (0/10 DA)	Port 80: No \| Port 443: No (R)	Allows ≥1 /8 on ports 80 AND 443 (≥6/10 DA)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-11-14 22:45:06).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 64.91 Mbit/s
Advertised Bandwidth: 64.91 Mbit/s
Rate Limit: 8.59 Gbit/s
Burst Limit: 8.59 Gbit/s
Total Data: 38 TB (1 year)
1mo: 14 TB | 6mo: 39 TB | 1y: 38 TB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-14 22:45:06

Measured By: 5/8 Bandwidth Authorities
Not measured by: 5947BB57, faravahar, longclaw
Consensus Weight: 45.6 Mbit/s (median of 5 measurements)
Measured Min / Max: 24.8 Mbit/s / 168.0 Mbit/s
Deviation: 143.2 Mbit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0024% of network (30th pctl) | Guard: 0.0071% (13th pctl) | Middle: N/A | Exit: N/A

History

Throughput and write/read, last 6 months

Uptime and Stability

Uptime Metrics

Current Status: UP 2h 52m 57s ago
Overall Uptime (1M/6M/1Y/5Y): 100.0%/100.0%/100.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y): —/99.8%/—/—
Hibernating: No

Timestamps

First Seen: 6mo 5d 1h ago (2026-05-13 22:00:00)
Last Seen: 1h 15m 27s ago (2026-11-14 22:00:00)
Last Restarted: 2h 52m 57s ago (2026-11-14 20:22:30)
Last Changed Address: 2026-05-13 22:00:00

Overload Status: Not Overloaded — No overload conditions reported.

Evaluated 2026-11-14 23:15 UTC. /details snapshot 2026-11-14 22:00:00 UTC (cached 28s ago). /bandwidth snapshot 2026-11-14 20:00:00 UTC (cached 1h 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

Operator and Family

Operator Identity

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

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: tor@9g4.net

Family Configuration

Family Support: MyFamily Only (2) — Legacy only. Consider migrating to Happy Families. | View Full Family (2)

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Members: 2

0A7083F7BF1ACD9ECC486BD28C616A1AE0907B5A
F0970FACC30D72673C54FC7A88DAE0E30B019196 (this relay)

Alleged Members: 6

(they don't list you back)

0024E93D8366B4169981EA5A07A9B7AC319E08C2
5086BC85611EA3312DDC28B591749A2402E05C1E
6CFBB403418932B5208E39A80B3F12952C454C61 (not in the network)
BBC050C12E6A00D36384A23CEA901068F626B615
C81C1B31EE34E0E035581018EE8DA04BA34A9F4F (not in the network)
ED39066F3CF8B93EDC7B00DEAA39EDA02558523B (not in the network)

Indirect Members: 0

none

Software and Version

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

Exit Health & Policy

DNS Health

Not an exit relay — DNS health testing does not apply.

IPv4 Exit Policy Summary

reject: 
  1-65535

IPv6 Exit Policy Summary

None

Full Exit Policy

reject *:*

Last fetch was at Sat, 14 Nov 2026 23:15:27 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-11-14 22: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	v6	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)
5947BB57	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast	64.9 Mbit/s (R) \| 816.0 Kbit/s	64.9 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	100.0% \| 98%	0.0d \| 0d	0.0d \| 0.0d	0.1d \| 5.9d	2026-11-12 18:13:36	64.9 Mbit/s (R)
E30CF7B3	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, Guard	168.0 Mbit/s (M) \| 816.0 Kbit/s	168.0 Mbit/s (M) \| 184.0 Mbit/s OR 16.8 Mbit/s	100.0% \| 98%	2.1d \| 2d	2.1d \| 2.1d	0.1d \| 2.5d	2026-11-14 20:22:33	168.0 Mbit/s (M)
dannenberg (DE)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, Guard	45.6 Mbit/s (M) \| 816.0 Kbit/s	45.6 Mbit/s (M) \| 256.0 Mbit/s OR 16.8 Mbit/s	100.0% \| 98%	58.4d \| 8d	50.9d \| 8.7d	0.1d \| 2.2d	2026-11-14 20:22:33	45.6 Mbit/s (M)
dizum (NL)	Yes	Yes	No	—	N	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, Guard	64.9 Mbit/s (R) \| 816.0 Kbit/s	64.9 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	99.8% \| 98%	44.9d \| 8d	38.4d \| 6.7d	0.1d \| 3.1d	2026-11-14 20:22:33	64.9 Mbit/s (R)
faravahar (US)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, Guard	64.9 Mbit/s (R) \| 816.0 Kbit/s	64.9 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	100.0% \| 98%	40.8d \| 8d	33.6d \| 6.8d	0.1d \| 2.3d	2026-11-14 20:22:33	64.9 Mbit/s (R)
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, Guard	34.4 Mbit/s (M) \| 816.0 Kbit/s	34.4 Mbit/s (M) \| 240.0 Mbit/s OR 16.8 Mbit/s	100.0% \| 98%	116.8d \| 8d	116.8d \| 8.9d	0.1d \| 2.2d	2026-11-14 20:22:33	34.4 Mbit/s (M)
longclaw (US)	Yes	Yes	No	—	Y	Yes	N/T	Running, Valid, V2Dir, Fast, Stable, Guard	64.9 Mbit/s (R) \| 816.0 Kbit/s	64.9 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	100.0% \| 98%	172.3d \| 8d	172.3d \| 9.5d	0.1d \| 2.4d	2026-11-14 20:22:33	64.9 Mbit/s (R)
maatuska (SE)	Yes	Yes	No	—	N	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, Guard	64.9 Mbit/s (R) \| 816.0 Kbit/s	64.9 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	98.8% \| 97%	24.5d \| 8d	1.6d \| 1.6d	0.1d \| 2.3d	2026-11-14 20:22:33	64.9 Mbit/s (R)
moria1 (US)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, Guard	168.0 Mbit/s (M) \| 8.4 Mbit/s	168.0 Mbit/s (M) \| 192.0 Mbit/s OR 16.8 Mbit/s	100.0% \| 98%	9.9d \| 8d	184.9d \| 10768.2d	0.1d \| 2.0d	2026-11-14 20:22:33	168.0 Mbit/s (M)
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, Guard	24.8 Mbit/s (M) \| 816.0 Kbit/s	24.8 Mbit/s (M) \| 240.0 Mbit/s OR 16.8 Mbit/s	100.0% \| 98%	184.6d \| 8d	184.6d \| 8.8d	0.1d \| 2.4d	2026-11-14 20:22:33	24.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.

View Relay "9g4net7"

Fingerprint: F0970FACC30D72673C54FC7A88DAE0E30B019196 | Family: 2 relays | tor@9g4.net | AS8560 | United States of America | Linux

Addresses

Reachability (Directory Authorities)

Location

Autonomous System

Eligibility Flag Vote Details

Capacity (Relay Reported)

Measurement (Directory Authority Verified)

History

Uptime Metrics

Timestamps

General Overload (from /details)

File Descriptor Exhaustion (from /bandwidth)

Rate Limits (from /bandwidth)

History

Operator Identity

Family Configuration

Full Exit Policy

Fingerprint: `F0970FACC30D72673C54FC7A88DAE0E30B019196` | Family: 2 relays | tor@9g4.net | AS8560 | United States of America | Linux