Autonomous system detail

AS169

Not announced

Operated by HANSCOM-NET-AS - Air Force Systems Networking.

Summary

// analyst note
Dormant USAF/DoD legacy ASN. Registry active under Air Force Systems Networking, administered by DISA-Columbus. Zero routed prefixes, zero peers, no public abuse signal. Only routing signal a transient 144.105.79.0/24 on 2024-05-07 seen by no RIS peers. CAIDA AS-rank/customer-cone not computable (timed out; unannounced AS).
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-06-17; not on Spamhaus DROP/SBL, CleanTalk, or AbuseIPDB indexed excerpts; Scamalytics 0/100 on the wider AFSN ISP label; dormant with no routed IP surface.
IPv4 prefixes
0
~0 addresses
IPv6 prefixes
0
Peer networks
0
0 up · 0 down
IANA block
1-1876
Assigned by ARIN
[ 01 ] — Context

About this ASN.

Updated  ·  Confidence: High

AS169 is a legacy United States Department of Defense Autonomous System Number registered with ARIN to Air Force Systems Networking (AFSN), the U.S. Air Force organization that administers Air Force data communications infrastructure under the Air Force Life Cycle Management Center (AFLCMC). The AS name, HANSCOM-NET-AS, ties it to Hanscom Air Force Base in Bedford, Massachusetts — a major Air Force installation for cyber, network, and electronic-systems programs. The registrant org record (ARIN OrgId 7ESG) lists an address at 501 East Moore Drive, Building 884, Room 1100, Gunther Annex, Maxwell AFB, AL, while the administrative, technical, and abuse point of contact is DISA-Columbus (Defense Information Systems Agency) in Whitehall, OH. The key triage point is that AS169 is effectively dormant: it announces zero IPv4 and zero IPv6 prefixes, is seen by none of the ~327 IPv4 / ~323 IPv6 RIS route collectors, and has no observed BGP neighbours as of June 2026. The only routing signal anywhere in the data is a single transient appearance of 144.105.79.0/24 on 2024-05-07 that no RIS peer saw at query time — consistent with a brief internal route leak or test announcement that did not persist. The org registration remains active (last updated 2025-03-13) even though the ASN record itself has not been refreshed since 2009. AFSN operates several other ASNs (e.g., 65, 123, 175, 221, 301) that may carry current traffic. No notable public abuse signal was found as of 2026-06-17; with no routed address space there is effectively no active IP surface.

Operator
Air Force Systems Networking (ARIN OrgId 7ESG; U.S. Air Force / AFLCMC, Maxwell AFB, AL) [Confirmed] — ARIN RDAP / whois.arin.net/rest/org/7ESG
Country / RIR
US, ARIN [Confirmed] — RIPEstat abuse-contact-finder (authoritative_rir: arin)
Allocated
ARIN ASN RegDate 1988-04-08 (registry database value, NOT an IEEE date — IEEE publishes none); ASN record last changed 2009-05-01 [Confirmed for the shown dates] — rdap.arin.net/registry/autnum/169
Org status
active ARIN registration. Org 7ESG last changed 2025-03-13; admin/tech/abuse contact DISA-Columbus (disa.columbus.ns.mbx.arin-registrations@mail.mil, +1-844-347-2457), 300 North James Road, Whitehall, OH; ASN record last changed 2009-05-01 [Confirmed] — rdap.arin.net/registry/autnum/169
Website
no dedicated public website for AS169/HANSCOM-NET-AS; parent organization operates under af.mil / aflcmc.af.mil [Confirmed] — peeringdb.com/org/20118, ipinfo.io/AS169

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-06-17; not on Spamhaus DROP/SBL, CleanTalk, or AbuseIPDB indexed excerpts; Scamalytics scores the wider "Air Force Systems Networking" ISP label 0/100 (covers AFSN block, not AS169 alone); no NANOG/Reddit incident threads found; dormant with no routed surface

[Likely] — bgp.tools/as/169, scamalytics.com/ip/isp/air-force-systems-networking

Network & routing

Network type
US federal government / military internal network infrastructure; legacy ASN named for Hanscom AFB networking [Confirmed] — whois.ipip.net/AS169, bgp.tools/as/169
Size
zero routed space — 0 IPv4 prefixes / 0 addresses, 0 IPv6 prefixes; dormant, not in the global routing table [Confirmed] — bgp.he.net/AS169, bgp.tools/as/169
Routing/peering
not currently routing; 0 BGP peers, 0 upstreams, 0 observed neighbours; visible to 0/327 IPv4 and 0/323 IPv6 RIS peers; only signal a transient 144.105.79.0/24 on 2024-05-07 [Confirmed] — RIPEstat routing-status, bgp.he.net/AS169
RPKI
not assessable — RIPEstat rpki-validation skipped (no announced prefix); HE shows 0 valid / 0 invalid origins, consistent with zero announcements [Confirmed] — bgp.he.net/AS169
Notable usage
originally the network ASN for Hanscom Air Force Base (Bedford, MA), a major USAF cyber/network/electronic-systems installation; AFSN operates other ASNs (65, 123, 175, 221, 301) that may carry current traffic [Likely] — whois.ipip.net/AS169, peeringdb.com/org/20118
PeeringDB
AFSN has org record org/20118 (last updated 2018-06-02) listing ASNs 65, 123, 175, 221, 301 — AS169 is NOT listed there and has no network-level PeeringDB entry; no peering policy published anywhere [Confirmed] — peeringdb.com/org/20118
Related ASNs
AS65, AS123, AS175, AS221, AS301 (other Air Force Systems Networking ASNs per PeeringDB org/20118) [Confirmed for the PeeringDB listing]
Analyst note
Encountered as a dormant USAF/DoD legacy ASN. Registry active under AFSN, administered by DISA-Columbus; no routed prefixes, no peers, no public abuse signal. CAIDA AS-rank / customer-cone could not be computed (CAIDA query timed out and an unannounced AS would not appear regardless).
[ 02 ] — Announced prefixes

What this network routes.

0 prefixes total · RIPEstat data · cached, not real-time
// IPv4 prefixes0
No IPv4 prefixes announced.
// IPv6 prefixes0
No IPv6 prefixes announced.
[ 03 ] — Notable peers & upstreams

Who it talks to.

0 observed neighbours
Neighbour data unavailable from public BGP collectors.