AS404

AS404 is a legacy 16-bit autonomous system number that ARIN returns as part of the block-style record AFCONC-BLOCK1-AS, which spans startAutnum 379 through endAutnum 508 and is registered to "Air Force Systems Networking" — the U.S. Air Force (Department of Defense). The registrant contact on the record is at 501 East Moore Dr., Bldg 884 Rm 1100, Gunter Annex, Maxwell AFB, Alabama, and the current ARIN administrative, technical, and abuse point of contact is the Defense Information Systems Agency (DISA) field office in Columbus, Ohio (disa.columbus.ns.mbx.arin-registrations@mail.mil). AS404 is not an independently branded network: it is one number inside a large historical military block, and no distinct per-ASN RDAP record exists beyond the block-level entry. Operationally the ASN is dormant. RIPEstat reports it as unannounced — zero IPv4 and zero IPv6 prefixes, zero observed neighbours, and 0 of 323 (v4) / 0 of 321 (v6) RIS peers seeing it — so there are no visible upstreams, peers, or downstreams, and no RPKI validation state can be assessed (an RPKI check requires a specific announced prefix, of which there are none). No PeeringDB network record exists for AS404 (a direct API query for asn=404 returned 404 Not Found), and no operator-authored website, peering policy, or usage statement was located on any Air Force or DISA page. Security posture is neutral as of 2026-07-02: no AS404-specific abuse signal appeared in Spamhaus, AbuseIPDB, or NANOG archives; only an org-level Scamalytics aggregate for "Air Force Systems Networking" (low fraud risk, spanning several USAF ASNs) is on record, which is not attributable to AS404 alone. CAIDA AS Rank and customer-cone data could not be retrieved because the lookup timed out.

Operator

Air Force Systems Networking — U.S. Air Force / Department of Defense; ARIN block record AFCONC-BLOCK1-AS (startAutnum 379, endAutnum 508); registrant at Gunter Annex, Maxwell AFB, AL [Confirmed] — ARIN RDAP https://rdap.arin.net/registry/autnum/404

Country / RIR

US, ARIN [Confirmed] — RIPEstat abuse-contact-finder (authoritative_rir: arin); ARIN RDAP

Allocated

1989-08-04 (ARIN autnum top-level "registration" event, eventDate 1989-08-04T00:00:00-04:00 — a first-party RIR fact, NOT an IEEE date; applies to the whole AFCONC-BLOCK1-AS block of which AS404 is a member); last changed 2008-06-06 [Confirmed] — ARIN RDAP autnum top-level events

Org status

active ARIN registration (RDAP status: active) but operationally inactive/unannounced; a legacy 16-bit ASN inside a large historical Air Force block [Confirmed] — ARIN RDAP, https://ipinfo.io/AS404

Contacts

abuse/admin/tech = DISA-Columbus, disa.columbus.ns.mbx.arin-registrations@mail.mil, +1-844-347-2457 ext.2, 300 North James Road, Whitehall, OH 43213 [Confirmed] — ARIN RDAP; RIPEstat abuse-contact-finder

Website

no dedicated AS404 operator site; administering agency is DISA (https://www.disa.mil/); Air Force domain of record af.mil [Likely] — https://ipinfo.io/AS404, https://www.disa.mil/

Security/abuse context (NEUTRAL, DATED)

no notable AS404-specific abuse signal found as of 2026-07-02 — no hits in Spamhaus, AbuseIPDB, or NANOG archives; org-level Scamalytics aggregate for "Air Force Systems Networking" rates low fraud risk but is not AS404-specific

Network & routing

Network type

U.S. federal government / military (DoD — Air Force) block; not a commercial ISP, hosting, or enterprise network. Third-party classifiers use a generic "ISP/Business/Hosting" bucket that is not a first-party self-description [Likely] — https://ipinfo.io/AS404, ARIN RDAP

Size / routing

dormant — 0 announced IPv4 prefixes and 0 announced IPv6 prefixes; 0 observed neighbours; 0/323 v4 and 0/321 v6 RIS peers seeing it (window 2026-06-18 to 2026-07-02) [Confirmed] — RIPEstat routing-status / announced-prefixes (https://stat.ripe.net/AS404)

Peering

no PeeringDB network record (direct API query asn=404 → HTTP 404); no upstreams or peers visible; no published peering policy on any DoD/Air Force/DISA page [Confirmed for absence] — https://www.peeringdb.com/api/net?asn=404

RPKI

not assessable — AS404 announces no prefixes, so there are no ROAs and no prefix to validate [Unknown] — RIPEstat rpki-validation skipped (requires a prefix)

AS rank / customer cone

Unknown — CAIDA ASRank lookup timed out in the canonical fetch and was not re-fetched [Unknown] — CAIDA error "operation aborted due to timeout"

Notable usage

Unknown — no first-party operator statement about deployment or purpose; third-party sources report it currently unannounced/inactive [Likely] — https://ipinfo.io/AS404

Analyst note

The autnum record's own "handle" reads AS379 with startAutnum/endAutnum = 379–508 — this is an ARIN block-style AS registration (one record covering the whole range), not a data anomaly; RIPEstat's as-overview for resource 404 independently confirms the same holder name, so the 1989-08-04 registration date and Air Force attribution are correctly matched to AS404. Nested entity dates (REGIS10-ARIN 2009-06-24; 7ESG org 2008-06-05) are decoys and were excluded from allocated_date. A5's "754th Electronic Systems Group / AS386–AS410" framing is not supported by the RDAP block bounds (379–508) and is not carried forward as fact.