Tor Relays :: 405tor4

View Relay "405tor4"

Fingerprint: `6AF16BD906F43268C7DC410DC46F63EAB4466491` | Family: 8 relays | AS7018 | United States of America | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, V2Dir (3)
BW Verified: 4/7 BW Auths Measured 10 Kbit/s Median
Stability: Not Overloaded | UP 2d 8h 59m ago

Reachability: IPv4: 9/9 (Directory Auths)
First Seen: 3d 10h 45m ago
BW Weight: 0.00% of Network | 10 Mbit/s Observed By Relay
Version: 0.4.9.8 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 1.4 MB/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: Time Known below threshold : Time Known 3.4 days is below 8 days requirement (4.6 more days needed)
Suggestion: Time Known tracks how long authorities have observed your relay. This resets if: 1) Identity key changes, 2) Long downtime makes authorities forget you. Just keep running stably.
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.
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.

Connectivity and Location

Addresses

OR Address: 107-208-159-58.lightspeed.okcbok.sbcglobal.net
107.208.159.58:9003

Reachability (Directory Authorities)

IPv4: 9/9

Location

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

Autonomous System

AS Number: AS7018
AS Name: AT&T Enterprises, LLC (BGP.tools)
AS Rarity: Rare (score: 2/5, 0.09% consensus weight, 40 operators)

Flags and Eligibility

Current Flags (3): Running, Valid, V2Dir

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)	10.9 Mbit/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: 3.4d (0/9 DA above threshold) Min/Max: 3.4d / 3.4d (9/9 DA, Voting / Total Eligible)	≥20.3d - 51.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥335.5d
Stable	Uptime	Below (0/9 DA)	2.4d (R)	≥12.4d - 12.8d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Below (4/9 DA)	4/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 (0/9 DA)	0/9 DA assigned Stable	≥20.3d - 51.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥335.5d
	Prereq: V2Dir	Meets (9/9 DA)	9/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Meets (9/9 DA)	Majority: 100.0% (9/9 DA)	≥98.0% (≥5/9 DA)
	Time Known	Meets (8/9 DA)	Median: 3.4d (0/9 DA above threshold) Min/Max: 2.9d / 3.4d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.8d
Guard	Prereq: Fast	Below (4/9 DA)	4/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 (0/9 DA)	0/9 DA assigned Stable	≥20.3d - 51.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥335.5d
	Prereq: V2Dir	Meets (9/9 DA)	9/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Meets (9/9 DA)	Majority: 100.0% (9/9 DA)	≥98% (≥5/9 DA)
	Time Known	Below (0/9 DA) (need 4.6 more days)	Median: 3.4d (0/9 DA above threshold) Min/Max: 2.9d / 3.4d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Below (0/9 DA)	10.9 Mbit/s (R)	≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-328.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-05-25 10:45:08).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 10.88 Mbit/s
Advertised Bandwidth: 10.88 Mbit/s
Rate Limit: 8.59 Gbit/s
Burst Limit: 8.59 Gbit/s
Total Data: 2.4 GB (1 month)

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-05-25 10:45:08

Measured By: 4/7 Bandwidth Authorities
Not measured by: bastet, dannenberg, longclaw
Median Measurement: 10.9 Kbit/s
Min / Max: 8 bit/s / 10.9 Kbit/s
Deviation: 10.9 Kbit/s [Warning] High variation

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

Uptime and Stability

Uptime Metrics

Current Status: UP 2d 8h 59m ago
Overall Uptime (1M/6M/1Y/5Y): 0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y): Matches Overall Uptime (0.0%/0.0%/0.0%/0.0%)
Hibernating: No

Timestamps

First Seen: 3d 10h 45m ago (2026-05-22 00:00:00)
Last Seen: 1h 45m 56s ago (2026-05-25 09:00:00)
Last Restarted: 2d 8h 59m ago (2026-05-23 01:46:40)
Last Changed Address: 2026-05-22 00:00:00

Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-05-25 03:00 UTC

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: none

Family Configuration

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

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Members: 8

1B94FAF4FD83732028CDC64C0F28B3DBAC08912C
2974569A8392B242991078864D5D3047EA8F67BB
2D5C6D8A00AF1BFFB028CFA954915779EB6E833C
6AF16BD906F43268C7DC410DC46F63EAB4466491 (this relay)
BB98244A761F36C80F7974A88E93A55B110AFB5F
D36013BB77EFEB8EFFACD7054CDFB9F71FD9611C
D6F0FDD0672158B8384234481D839DCBD15E7F7C
E8A87E37DD79EAD6757146B4974113A2F06E1714

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

Platform: Linux — Tor 0.4.9.8 on Linux
Version: 0.4.9.8 — 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 Mon, 25 May 2026 10:45:55 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-05-25 10:45:08).

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, V2Dir	10.9 Mbit/s \| 816.0 Kbit/s	10.9 Mbit/s \| 224.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	3.4d \| 8d	3.4d \| 50.7d	2.4d \| 12.4d	100.0% \| 98.0%	3.4d \| 1.0d	2026-05-25 07:48:11	10.9 Kbit/s
dannenberg (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast	10.9 Mbit/s \| 816.0 Kbit/s	10.9 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	3.4d \| 8d	3.4d \| 44.6d	2.4d \| 12.8d	100.0% \| 98.0%	3.4d \| 1.0d	2026-05-25 07:48:11	10.9 Kbit/s
dizum (NL)	Yes	Yes	No	—	N	Yes	Running, Valid, V2Dir, Fast	10.9 Mbit/s \| 816.0 Kbit/s	10.9 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	3.4d \| 8d	3.4d \| 20.3d	2.4d \| 12.8d	100.0% \| 98.0%	3.4d \| 1.0d	2026-05-25 07:48:11	10.9 Kbit/s
faravahar (US)	Yes	Yes	No	—	N	Yes	Running, Valid, V2Dir, Fast	10.9 Mbit/s \| 816.0 Kbit/s	10.9 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	3.4d \| 8d	3.4d \| 51.2d	2.4d \| 12.9d	100.0% \| 98.0%	3.4d \| 1.0d	2026-05-25 07:48:11	10.9 Kbit/s
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir	10.9 Mbit/s \| 816.0 Kbit/s	10.9 Mbit/s \| 312.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	3.4d \| 8d	3.4d \| 52.0d	2.4d \| 12.9d	100.0% \| 98.0%	3.4d \| 1.0d	2026-05-25 07:48:11	8 bit/s
longclaw (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir	10.9 Mbit/s \| 816.0 Kbit/s	10.9 Mbit/s \| 248.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	3.4d \| 8d	3.4d \| 58.6d	2.4d \| 12.8d	100.0% \| 98.0%	3.4d \| 1.0d	2026-05-25 07:48:11	10.9 Kbit/s
maatuska (SE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast	10.9 Mbit/s \| 816.0 Kbit/s	10.9 Mbit/s \| 328.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	3.4d \| 8d	3.4d \| 22.9d	2.4d \| 12.7d	100.0% \| 98.0%	3.4d \| 1.0d	2026-05-25 07:48:11	3600 bit/s
moria1 (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir	10.9 Mbit/s \| 8.4 Mbit/s	10.9 Mbit/s \| 240.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	2.9d \| 8d	3.4d \| 335.5d	2.4d \| 13.1d	100.0% \| 98.0%	2.9d \| 9.8d	2026-05-25 07:48:11	8 bit/s
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir	10.9 Mbit/s \| 816.0 Kbit/s	10.9 Mbit/s \| 312.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	3.4d \| 8d	3.4d \| 53.6d	2.4d \| 13.1d	100.0% \| 98.0%	3.4d \| 1.0d	2026-05-25 07:48:11	8 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.