AS393

AS393 is a legacy autonomous system number administered by ARIN and registered to Air Force Systems Networking, a U.S. Department of Defense / U.S. Air Force networking organization. It is not an individually delegated ASN with its own dedicated RDAP record: ARIN returns a single contiguous block object (handle AS379, name AFCONC-BLOCK1-AS, startAutnum 379, endAutnum 508) for any member query, and AS393 falls inside that AS379–AS508 range. The block was registered on 1989-08-04 per the autnum's top-level registration event and last changed 2008-06-06. The registrant org (ARIN handle 7ESG) is listed at 501 East Moore Dr., Bldg 884 Rm 1100, Gunter Annex, Maxwell AFB, AL 36114, while the abuse/administrative/technical point of contact has been consolidated under DISA Columbus (REGIS10-ARIN, Whitehall, OH; disa.columbus.ns.mbx.arin-registrations@mail.mil). The key triage point is that AS393 is dormant: RIPEstat reports it is not announced, with zero IPv4 and zero IPv6 prefixes and zero of the 323/321 RIS peers observing it, no upstreams, and no observed neighbours. CAIDA AS Rank data was unavailable (source timed out), and RPKI validation is not applicable because the ASN originates no prefixes. No notable public abuse signal was found as of 2026-07-02 — no Spamhaus DROP/ASN-DROP listing, no documented BGP hijack or route leak, and no NANOG or Reddit discussion specific to AS393 — consistent with a clean, dormant government/military allocation rather than an actively operated commercial network.

Operator

Air Force Systems Networking (U.S. Air Force / DoD; ARIN org handle 7ESG, Maxwell AFB / Gunter Annex, AL) [Confirmed] — ARIN RDAP autnum registrant, https://rdap.arin.net/registry/autnum/393

Country / RIR

US, ARIN [Confirmed] — RIPEstat abuse-contact-finder (authoritative_rir: arin), https://stat.ripe.net/data/abuse-contact-finder/data.json?resource=393

Allocated

1989-08-04 (ARIN registry date, from the autnum TOP-LEVEL registration event — a first-party RIR fact, NOT an IEEE date; IEEE publishes no ASN registration dates); last changed 2008-06-06 [Confirmed] — ARIN RDAP autnum top-level events, https://rdap.arin.net/registry/autnum/393

Org status

active per ARIN RDAP status[] on the AS379–508 block; registrant org (7ESG, Air Force Systems Networking) remains at Maxwell AFB while registration management is consolidated under DISA Columbus [Confirmed] — https://rdap.arin.net/registry/autnum/393

Contacts

disa.columbus.ns.mbx.arin-registrations@mail.mil; +1-844-347-2457 ext2 (REGIS10-ARIN, DISA Columbus, Whitehall, OH); registrant Maxwell AFB / Gunter Annex, AL [Confirmed] — https://rdap.arin.net/registry/autnum/393

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-02 — no Spamhaus DROP/ASN-DROP listing, no documented BGP hijack/route leak, and no NANOG or Reddit thread specific to AS393; dormant/unrouted status means essentially no attack surface

Network & routing

Network type

legacy government/military block allocation, not an individually delegated operator ASN; dormant (no active routing) [Confirmed] — ARIN RDAP + RIPEstat routing-status, https://stat.ripe.net/data/routing-status/data.json?resource=393

Size

dormant — 0 IPv4 prefixes / 0 IPv4 addresses and 0 IPv6 prefixes; no address space visible in the global routing table [Confirmed] — RIPEstat announced-prefixes / routing-status (2026-07), https://stat.ripe.net/data/announced-prefixes/data.json?resource=393

Routing/peering

NOT announced — 0 RIS peers seeing it (0/323 v4, 0/321 v6); observed_neighbours 0; no upstreams or peers visible; RIPEstat as-overview announced=false [Confirmed] — https://stat.ripe.net/data/routing-status/data.json?resource=393

RPKI

not assessable — AS393 announces no prefixes, so there are no ROAs to validate; RIPEstat rpki-validation was skipped (no prefix supplied), which is moot given zero announcements [Confirmed] — RIPEstat rpki-validation

Peering policy

none active / not publicly documented — no PeeringDB net record for AS393 or AFCONC-BLOCK1-AS; a public peering policy is not expected for DoD infrastructure [Confirmed for absence] — https://www.peeringdb.com/

Notable usage

Unknown / not independently verifiable from operator-official sources — third-party aggregators describe it only as Air Force Systems Networking infrastructure; no first-party service description or network map on an official .mil site [Unknown] — https://whois.ipip.net/AS393

Related ASNs

other members of the AFCONC-BLOCK1 cluster (Air Force Systems Networking), e.g. AS379, AS385, AS386, AS391, AS399, AS400, AS416, AS440, AS448, AS486, AS727 [Likely per third-party DB] — https://asrank.caida.org/asns?asn=399

Registry scope

RDAP returns a BLOCK record (handle AS379, name AFCONC-BLOCK1-AS, startAutnum 379, endAutnum 508); AS393 is a member of the contiguous AS379–AS508 range and inherits the block's registration/last-changed dates [Confirmed] — ARIN RDAP, https://rdap.arin.net/registry/autnum/393

Analyst note

Encountered as a dormant legacy ASN inside a contiguous DoD block; there is no per-393 RDAP record (startAutnum 379 / endAutnum 508 proves it), no announced prefixes, and no public operator website. Clean, inactive government/military ASN.