View Relay "YourRelayNickname"

Fingerprint: `073858E0D0BE070645C30F88DB3BECC597D98522` | Family: 1 relay | your-email@example.com | AS31898 | United States of America | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid (2)
BW Verified: 0/7 BW Auths Measured 480 bit/s Median
Stability: Not Overloaded | UP 3h 4m 28s ago

Reachability: IPv4: 9/9 (Directory Auths)
First Seen: 2h 45m 58s ago
BW Weight: 0.00% of Network | 483 Kbit/s Observed By Relay
Version: 0.4.9.13 Recommended

Issues Detected:

Guard: requires Fast flag : Guard flag requires having the Fast flag first
Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
Guard: requires Stable flag : Guard flag requires having the Stable flag first
Suggestion: Get Stable flag by maintaining consistent uptime. Stable requires uptime and MTBF at or above network median (typically 2-3 weeks of stable running).
Guard: bandwidth below threshold : Observed bandwidth 483 Kbit/s is below 2 MB/s minimum (AuthDirGuardBWGuarantee)
Suggestion: Guard requires ≥2 MB/s bandwidth OR being in top 25% of network. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx or ARM.
Guard: WFU below threshold : Weighted Fractional Uptime 0.6% is below 98% requirement
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.
Not eligible for Stable flag : Uptime or MTBF below network median for most authorities
Suggestion: Stable flag requires uptime/MTBF at or above network median. Keep your relay running continuously for 2-3 weeks. Avoid restarts. Use reliable hardware and network connection.
HSDir: requires Fast flag : HSDir flag requires having the Fast flag first
Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
HSDir: requires Stable flag : HSDir flag requires having the Stable flag first
Suggestion: Get Stable flag by maintaining consistent uptime. Stable requires uptime and MTBF at or above network median (typically 2-3 weeks of stable running). Avoid restarts.
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
HSDir: WFU below threshold : WFU 0.6% below 98% required for HSDir
Suggestion: HSDir requires ≥98% WFU, Stable flag, and Time Known ≥25 hours (or ~10 days for moria1). Improve uptime consistency.
Low bandwidth authority measurements : Only 0/7 bandwidth authorities measured this relay. Minimum 3 measurements needed for accurate consensus weight.
Suggestion: Low measurement count can indicate connectivity issues. Check: 1) Relay is reachable from multiple geographic locations, 2) ORPort accepts connections from bandwidth scanners, 3) RelayBandwidthRate in torrc matches actual capacity. New relays may take 1-2 days to be measured by all authorities.

Connectivity and Location

Addresses

OR Address: 168.107.54.232:8443

Reachability (Directory Authorities)

IPv4: 9/9

Location

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

Autonomous System

AS Number: AS31898
AS Name: Oracle Corporation (BGP.tools)
AS Rarity: Rare (score: 2/5, 0.23% consensus weight, 86 operators)

Flags and Eligibility

Current Flags (2): Running, Valid

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	Below (0/9 DA)	483.3 Kbit/s (R)	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s
Stable	MTBF	Below (0/9 DA)	Median: 0.2d (1/9 DA above threshold) Min/Max: 0.1d / 567.9d (9/9 DA, Voting / Total Eligible)	≥4.9d - 10.8d (varies) (≥5/9 DA) [Stricter] moria1: ≥9086.1d
Stable	Uptime	Below (0/9 DA)	0.1d (R)	≥3.1d - 3.1d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Below (0/9 DA)	0/9 DA assigned Fast	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Below (1/9 DA)	1/9 DA assigned Stable	≥4.9d - 10.8d (varies) (≥5/9 DA) [Stricter] moria1: ≥9086.1d
	Prereq: V2Dir	Below (0/9 DA)	0/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Below (0/9 DA)	Median: 0.5% (0/9 DA above threshold) Min/Max: 0.3% / 3.5% (9/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Meets (8/9 DA)	Median: 36.7d (9/9 DA above threshold) Min/Max: 9.8d / 40.1d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.9d
Guard	Prereq: Fast	Below (0/9 DA)	0/9 DA assigned Fast	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Below (1/9 DA)	1/9 DA assigned Stable	≥4.9d - 10.8d (varies) (≥5/9 DA) [Stricter] moria1: ≥9086.1d
	Prereq: V2Dir	Below (0/9 DA)	0/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Below (0/9 DA)	Median: 0.5% (0/9 DA above threshold) Min/Max: 0.3% / 3.5% (9/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 36.7d (9/9 DA above threshold) Min/Max: 9.8d / 40.1d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Below (0/9 DA)	483.3 Kbit/s (R)	≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-320.0 Mbit/s (≥5/9 DA)
Exit	Exit Policy	Below (0/9 DA)	Port 80: No \| Port 443: No (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-10-11 17:15:11).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 483.33 Kbit/s
Advertised Bandwidth: 483.33 Kbit/s
Rate Limit: 8.19 Mbit/s
Burst Limit: 12.29 Mbit/s
Total Data: N/A

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-10-11 17:15:11

Measured By: 0/7 Bandwidth Authorities
Not measured by: bastet, dannenberg, faravahar, gabelmoo, longclaw, moria1, tor26
Median Measurement: 480 bit/s
Min / Max: 480 bit/s / 480 bit/s

Network Participation: Consensus Weight: 0.0000% of network (3th pctl) | Guard: N/A | Middle: 0.0000% (3th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics

Current Status: UP 3h 4m 28s ago
Overall Uptime (1M/6M/1Y/5Y): 0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y): N/A
Hibernating: No

Timestamps

First Seen: 2h 45m 58s ago (2026-10-11 15:00:00)
Last Seen: 1h 45m 58s ago (2026-10-11 16:00:00)
Last Restarted: 3h 4m 28s ago (2026-10-11 14:41:30)
Last Changed Address: 2026-10-11 15:00:00

Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

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

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: your-email@example.com

Family Configuration

Family Support: None — No family membership configured

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Member: 1

073858E0D0BE070645C30F88DB3BECC597D98522 (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 — Recommended
Version Status: Recommended

Exit Health & Policy

DNS Health

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

IPv4 Exit Policy Summary

reject: 
  1-65535

Full Exit Policy

reject *:*

Last fetch was at Sun, 11 Oct 2026 17:45:55 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-10-11 17:15:11).

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 (Relay\|T)	Guard BW (Relay\|Threshold)	Guard WFU (M\|T)	Guard TK (M\|T)	Stable MTBF (M\|T)	Stable Uptime (Relay\|T)	HSDir WFU (M\|T)	HSDir TK (M\|T)	Desc Published	Cons Wt (Authority)
bastet (US)	Yes	Yes	No	—	Y	Yes	Running, Valid	483.3 Kbit/s \| 816.0 Kbit/s	483.3 Kbit/s \| 192.0 Mbit/s OR 16.0 Mbit/s	0.6% \| 98%	36.7d \| 8d	0.2d \| 10.8d	0.1d \| 3.2d	0.6% \| 98.0%	36.7d \| 1.0d	2026-10-11 14:41:37	480 bit/s
dannenberg (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid	483.3 Kbit/s \| 816.0 Kbit/s	483.3 Kbit/s \| 288.0 Mbit/s OR 16.0 Mbit/s	3.5% \| 98%	27.8d \| 8d	0.9d \| 4.9d	0.1d \| 3.2d	3.5% \| 98.0%	27.8d \| 1.0d	2026-10-11 14:41:37	480 bit/s
dizum (NL)	Yes	Yes	No	—	N	Yes	Running, Valid	483.3 Kbit/s \| 816.0 Kbit/s	483.3 Kbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	2.0% \| 98%	30.5d \| 8d	0.6d \| 10.8d	0.1d \| 3.1d	2.0% \| 98.0%	30.5d \| 1.0d	2026-10-11 14:41:37	480 bit/s
faravahar (US)	Yes	Yes	No	—	Y	Yes	Running, Valid	483.3 Kbit/s \| 816.0 Kbit/s	483.3 Kbit/s \| 320.0 Mbit/s OR 16.0 Mbit/s	0.3% \| 98%	40.0d \| 8d	0.1d \| 11.7d	0.1d \| 3.1d	0.3% \| 98.0%	40.0d \| 1.0d	2026-10-11 14:41:37	480 bit/s
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid	483.3 Kbit/s \| 816.0 Kbit/s	483.3 Kbit/s \| 272.0 Mbit/s OR 16.0 Mbit/s	0.3% \| 98%	40.1d \| 8d	0.1d \| 10.8d	0.1d \| 3.2d	0.3% \| 98.0%	40.1d \| 1.0d	2026-10-11 14:41:37	480 bit/s
longclaw (US)	Yes	Yes	No	—	Y	Yes	Running, Valid	483.3 Kbit/s \| 816.0 Kbit/s	483.3 Kbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	0.4% \| 98%	38.2d \| 8d	0.2d \| 11.1d	0.1d \| 3.1d	0.4% \| 98.0%	38.2d \| 1.0d	2026-10-11 14:41:37	480 bit/s
maatuska (SE)	Yes	Yes	No	—	N	Yes	Running, Valid	483.3 Kbit/s \| 816.0 Kbit/s	483.3 Kbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	0.4% \| 98%	39.4d \| 8d	0.1d \| 10.6d	0.1d \| 3.1d	0.4% \| 98.0%	39.4d \| 1.0d	2026-10-11 14:41:37	480 bit/s
moria1 (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, Stable	483.3 Kbit/s \| 8.4 Mbit/s	483.3 Kbit/s \| 208.0 Mbit/s OR 16.0 Mbit/s	1.1% \| 98%	9.8d \| 8d	567.9d \| 9086.1d	0.1d \| 3.2d	1.1% \| 98.0%	9.8d \| 9.9d	2026-10-11 14:41:37	480 bit/s
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Running, Valid	483.3 Kbit/s \| 816.0 Kbit/s	483.3 Kbit/s \| 280.0 Mbit/s OR 16.0 Mbit/s	0.5% \| 98%	35.8d \| 8d	0.2d \| 11.0d	0.1d \| 3.1d	0.5% \| 98.0%	35.8d \| 1.0d	2026-10-11 14:41:37	480 bit/s

— = not tested/available • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known

Bandwidth Values Explained:
Relay Reported = Your relay's self-reported bandwidth from its descriptor (observed_bandwidth). Used for flag eligibility (Guard, Fast).
Authority Measured = Bandwidth measured by authority's sbws scanner. Used for consensus weight (path selection probability).
Why different? Authorities verify your reported bandwidth independently. 6 of 9 authorities run bandwidth scanners; 3 use relay-reported values directly.

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.