Autonomous system detail

AS417

Not announced

Operated by AFCONC-BLOCK1-AS - Air Force Systems Networking.

Summary

// analyst note
Dormant/legacy DoD-held ASN. RDAP autnum handle reads 'AS379' (block-first number) with links to /autnum/417 — a block-registration artifact; resource confirmed as AS417 via RIPEstat/CAIDA. Dates from autnum top-level events[] (registration 1989-08-04, last changed 2008-06-06), not nested entity dates. RIPEstat and CAIDA agree on zero announcements, zero peers, zero cone.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-02; not in Spamhaus ASN-DROP, NANOG archives, or abuse/threat feeds.
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

AS417 is a legacy autonomous system number registered under ARIN to Air Force Systems Networking, a U.S. Department of Defense / United States Air Force network organization. It sits inside the historic AFCONC-BLOCK1-AS block registration that spans AS379AS508, with the registrant entity handle 7ESG located at 501 East Moore Drive, Gunther Annex, Maxwell AFB, Alabama, and abuse/administrative/technical contact handled by DISA-Columbus (300 North James Road, Whitehall, Ohio). The key triage point for AS417 is that it is effectively dormant today: every routing source consulted agrees it announces zero IPv4 and zero IPv6 prefixes. RIPEstat reports the ASN as not announced, with zero RIS peer visibility (0 of 324 v4 peers, 0 of 320 v6 peers), zero announced address space, and zero observed neighbours. CAIDA AS Rank corroborates this with a rank of 79,459, seen=false, cliqueMember=false, a singleton customer cone (the ASN itself, 0 prefixes, 0 addresses), and an AS degree of all zeros — no customer, peer, or provider relationships. RPKI posture is not assessable because AS417 originates no prefixes and therefore has no ROAs to validate. No notable public abuse signal was found as of 2026-07-02 — the ASN does not appear on Spamhaus ASN-DROP, in NANOG mailing-list archives, or in threat/abuse feeds, and general USAF cyber-incident news located in search did not name this specific ASN. This profile is consistent with a legacy DoD-held ASN allocation that is currently unrouted/administrative rather than actively providing transit. One data-quality note: the ARIN RDAP autnum payload's own handle field reads "AS379" (the block's first number) while its self-links reference /registry/autnum/417 — an internal RIR object artifact of the block registration; the queried resource is AS417, matching the RIPEstat and CAIDA resource identifiers.

Operator
Air Force Systems Networking (U.S. Department of Defense / U.S. Air Force; ARIN registrant handle 7ESG, Maxwell AFB, AL; registration administered by DISA-Columbus, Whitehall, OH) [Confirmed] — ARIN RDAP autnum/417
Country / RIR
US, ARIN [Confirmed] — RIPEstat abuse-contact-finder (authoritative_rir: arin)
Allocated
1989-08-04 (ARIN registry date from the autnum top-level events[], eventAction=registration on the AFCONC-BLOCK1-AS block; block-scoped across AS379–AS508, NOT an IEEE date); last changed 2008-06-06 [Confirmed] — ARIN RDAP autnum top-level events
Org status
active (per ARIN RDAP status field for the covering AS379–AS508 block record); U.S. Air Force / DoD network organization [Confirmed] — ARIN RDAP autnum/417
Contacts
abuse/admin/technical disa.columbus.ns.mbx.arin-registrations@mail.mil (DISA-Columbus, Whitehall, OH); registrant Air Force Systems Networking, Maxwell AFB, AL [Confirmed] — ARIN RDAP autnum/417, RIPEstat abuse-contact-finder

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-02 — not in Spamhaus ASN-DROP, NANOG archives, or abuse/threat feeds; general USAF cyber-incident news did not name this ASN; dormant, unrouted ASN under a DoD operator

[Likely] — spamhaus.org/drop/asndrop.txt, seclists.org/nanog

Network & routing

Network type
U.S. military / government (DoD, U.S. Air Force), non-commercial; AS417 is legacy/dormant within the reserved AFCONC-BLOCK1-AS block [Confirmed] — ARIN RDAP autnum/417
Size
dormant — 0 IPv4 prefixes / 0 IPv4 addresses and 0 IPv6 prefixes; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — RIPEstat routing-status / CAIDA AS Rank
Routing/peering
NOT announced — 0 RIS peers seeing it (0/324 v4, 0/320 v6); CAIDA degree total 0 (customer 0, peer 0, provider 0); no upstreams or peers observed in any source [Confirmed]. No published peering policy; no PeeringDB net record returned for AS417
[Likely] — RIPEstat routing-status, bgp.he.net/AS417, peeringdb.com/api/net?asn=417
RPKI
not assessable — AS417 announces no prefixes, so there are no ROAs to validate; RIPEstat rpki-validation skipped (no prefix to check) [Unknown] — RIPEstat
Notable usage
part of the historic AFCONC-BLOCK1-AS block (AS379–AS508) registered to Air Force Systems Networking since 1989-08-04 (block-level date); zero routed prefixes observed, consistent with AS417 being currently unrouted/administrative within this reserved DoD block [Likely] — ARIN RDAP, bgp.he.net/AS417
Related ASNs
AS379–AS508 (the AFCONC-BLOCK1-AS block this ASN belongs to) [Confirmed] — ARIN RDAP autnum/417
Analyst note
Encountered as a dormant legacy ASN within a DoD-held block. RDAP autnum handle reads "AS379" (block-first number) with links to /autnum/417 — an internal RIR block-registration artifact; treated the queried resource as AS417 per RIPEstat/CAIDA resource='417'. Allocation/last-changed dates taken from the autnum top-level events[], not from nested entity dates (7ESG org 2008-06-05, REGIS10-ARIN contact 2009-06-24 are decoys). Clean, inactive ASN.
[ 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.