AS380

AS380 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 resource administered by the Defense Information Systems Agency (DISA). It is not an individually-registered ASN: ARIN serves it as part of the contiguous AFCONC-BLOCK1-AS block record (startAutnum 379, endAutnum 508, RDAP handle keyed to AS379), so every registry fact below is a block-level attribute inherited by AS380 rather than an AS380-specific allocation event. The ARIN registrant org (handle 7ESG) lists an address at 501 East Moore Dr., Bldg 884 Rm 1100, Gunter Annex, Maxwell AFB, AL 36114, while the abuse, administrative, and technical contact routes through DISA-Columbus (300 North James Road, Whitehall, OH 43213; disa.columbus.ns.mbx.arin-registrations@mail.mil). The low-number range marks this as one of the earliest ASN allocations, consistent with DoD/Air Force internal networking dating to the origins of ASN assignment. The key triage point for AS380 is that it is effectively dormant today: RIPEstat reports it announces zero IPv4 and zero IPv6 prefixes, is seen by zero RIS peers (0/323 v4, 0/322 v6), has zero upstreams, zero observed neighbours, and a singleton customer cone (the ASN itself, 0 prefixes, 0 addresses). RDAP status remains "active," but BGP visibility shows nothing announced since 205.138.133.0/24 was last seen on 2006-08-13 (first seen announcing 132.33.0.0/16 on 2001-09-26). No PeeringDB network object exists for AS380 specifically. RPKI posture is not assessable — there are no active originations and therefore no ROAs. No notable public abuse signal was found as of 2026-07-02 — not in Spamhaus DROP/ASN-DROP nor in general web / NANOG-archive searches — consistent with a clean, dormant military ASN whose restricted public visibility reflects operational-security policy rather than reputation. It mirrors the profile of its immediate sibling AS379 (same block, same registrant, same DISA contact).

Operator

Air Force Systems Networking (U.S. DoD / U.S. Air Force; ARIN OrgId 7ESG; administered by DISA) [Confirmed] — ARIN RDAP (https://rdap.arin.net/registry/autnum/380)

Country / RIR

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

Allocated

1989-08-04 (ARIN registry date from the autnum TOP-LEVEL registration event for the AS379–AS508 block containing AS380, NOT an IEEE date — IEEE publishes no ASN registration dates; the nested entity/org events of 2008-06-05 and 2009-06-24 are decoys); last changed 2008-06-06

[Confirmed] — ARIN RDAP autnum top-level events (https://rdap.arin.net/registry/autnum/380)

Org status

active per ARIN RDAP; U.S. Air Force network resource administered by DISA (Gunter Annex, Maxwell AFB, AL; DISA-Columbus, OH) [Confirmed] — ARIN RDAP (https://rdap.arin.net/registry/autnum/380)

Contacts

abuse/admin/tech via DISA-Columbus — disa.columbus.ns.mbx.arin-registrations@mail.mil, +1-844-347-2457 ext.2; registrant HQ 501 East Moore Dr., Bldg 884 Rm 1100, Gunter Annex, Maxwell AFB, AL 36114 [Confirmed] — ARIN RDAP (https://rdap.arin.net/registry/autnum/380)

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-02 — not in Spamhaus DROP/ASN-DROP, nor in general web / NANOG-archive searches (search recall degraded by an unrelated high-volume "AS380" Alaska Airlines flight-number namespace collision, so absence is "no signal found despite noise," not an exhaustive negative); dormant/unrouted network limits abuse surface

Network & routing

Network type

U.S. government / military network (DoD, U.S. Air Force / AFNET); not a commercial ISP, hosting, or content network; AS380 is legacy/inactive [Confirmed] — ARIN RDAP; bgp.tools/as/380

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 (https://stat.ripe.net/AS380)

Routing/peering

NOT announced — 0 RIS peers seeing it (0/323 v4, 0/322 v6); RIPEstat observed_neighbours 0; no public peering policy published; no AS380-specific PeeringDB network object [Confirmed] — RIPEstat (https://stat.ripe.net/AS380), peeringdb.com/org/20118

RPKI

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

Notable usage

part of a contiguous historical ASN block (AS379 through AS508) allocated to Air Force Systems Networking for DoD/Air Force internal networking since the earliest ASN allocations; no specific public-facing services documented [Likely] — bgp.tools/as/380, whois.ipip.net/AS380

Historical routing

first seen announcing 132.33.0.0/16 on 2001-09-26; last seen announcing 205.138.133.0/24 on 2006-08-13; not announced since [Confirmed] — RIPEstat routing-status (https://stat.ripe.net/AS380)

Block/RDAP anomaly note

RDAP for AS380 returns the block-level record (handle AS379, startAutnum 379 / endAutnum 508); ARIN exposes no AS380-specific sub-record, so all registry dates/org data are the block's top-level facts applied to AS380 as a member [Confirmed] — ARIN RDAP (https://rdap.arin.net/registry/autnum/380)

Analyst note

Encountered as a dormant legacy military ASN registered to Air Force Systems Networking via DISA; RDAP status is "active" but no prefixes have been visible in BGP since 2006. The absence of community/peering presence reflects deliberate DoD operational security, not a defunct or ill-reputed operator. Same block/profile as sibling AS379. Clean, inactive ASN.