AS382

AS382 is a legacy autonomous system number registered under ARIN and administered on behalf of the U.S. Department of Defense. It has no distinct RDAP or WHOIS record of its own: the ARIN autnum object resolves to a single contiguous block registration, handle AS379, name AFCONC-BLOCK1-AS, spanning startAutnum 379 through endAutnum 508 (130 ASNs) under the organization "Air Force Systems Networking" (org handle 7ESG, Maxwell AFB, AL). This block-registration pattern is typical of pre-CIDR-era military allocations, where individual ASNs share one registry entry rather than carrying independent org details. The key triage point for AS382 is that it is effectively dormant today: every routing source consulted agrees it announces zero IPv4 and zero IPv6 prefixes and has no visible BGP peers. RIPEstat routing-status shows 0 of 323 v4 RIS peers and 0 of 322 v6 peers seeing it as of 2026-07-02, with zero observed neighbours. Its last known announcement was a single prefix, 214.4.83.0/24, first seen 2012-02-01 and last seen 2017-04-10; it has not been observed in the DFZ since. CAIDA AS-rank, customer cone, and RPKI posture could not be assessed — the CAIDA fetch timed out, and with no active originations there are no ROAs to validate. Registration events for the block were read from the RDAP autnum object's top-level events[] array: registration 1989-08-04, last changed 2008-06-06 (the nested entity/org dates of 2008-06-05/2009-06-24 are contact-record artifacts and were excluded). Administrative and abuse contact runs through DISA-Columbus (Whitehall, OH), abuse address disa.columbus.ns.mbx.arin-registrations@mail.mil. No notable public abuse signal was found as of 2026-07-02 — not in Spamhaus DROP/ASN-DROP, NANOG archives, or other threat-intel feeds — consistent with a clean, dormant military allocation rather than commercial hosting or transit infrastructure. There is no PeeringDB record (peeringdb.com/asn/382 returns 404) and no operator-published peering policy, website, or case studies, as expected for an internal DoD block.

Operator

Air Force Systems Networking (U.S. Air Force / DoD; ARIN org handle 7ESG; registrant address Maxwell AFB, AL; administered by DISA-Columbus, OH) [Confirmed] — ARIN RDAP autnum/382, whois.arin.net/rest/asn/AS379

Country / RIR

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

Allocated

1989-08-04 (ARIN registry date for the AS379–AS508 block that covers AS382, from the RDAP autnum top-level "registration" event — a first-party RIR fact, NOT an IEEE date); last changed 2008-06-06 [Confirmed] — ARIN RDAP autnum top-level events

Block context

AS382 falls within AFCONC-BLOCK1-AS, a contiguous legacy block AS379–AS508 (130 ASNs) registered as one ARIN entry under handle AS379; individual ASNs do not carry separate RDAP/WHOIS records [Confirmed] — ARIN RDAP autnum/382 (startAutnum 379, endAutnum 508)

Org status

ARIN record status "active" (last changed 2008-06-06); third-party aggregator ipinfo.io separately reports AS382 as unrouted/0 prefixes ("Inactive" in operational terms) — registry status active, operationally dormant [Confirmed] — ARIN RDAP autnum/382, ipinfo.io/AS382

Website

none — no dedicated operator/about/IR page for this ASN or block; ipinfo.io loosely associates the org with af.mil, but that is aggregator inference, not a first-party operator page [Likely] — ipinfo.io/AS382

Contacts

disa.columbus.ns.mbx.arin-registrations@mail.mil (abuse/admin/tech via DISA-Columbus); registrant Maxwell AFB, AL 36114 [Confirmed] — RIPEstat abuse-contact-finder, ARIN RDAP autnum/382

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-02 — not in Spamhaus DROP/ASN-DROP, NANOG archives, or other threat-intel feeds; consistent with a dormant military allocation

Network & routing

Network type

U.S. government/military network (DoD legacy address space, DISA-administered); not a commercial ISP, transit, or content network [Confirmed] — ARIN RDAP autnum/382

Size

dormant — 0 IPv4 prefixes / 0 IPv6 prefixes; no address estimate returned by RIPEstat [Confirmed] — RIPEstat announced-prefixes / routing-status (2026-07-02)

Routing/peering

NOT announced — 0/323 v4 RIS peers, 0/322 v6 RIS peers; 0 observed neighbours; no upstreams or peers visible. Last known announcement 214.4.83.0/24, seen 2012-02-01 to 2017-04-10 [Confirmed] — RIPEstat routing-status / announced-prefixes

Peering policy

none published — no PeeringDB record (peeringdb.com/asn/382 → HTTP 404); no self-published policy, consistent with a non-commercial DoD block [Confirmed] — peeringdb.com/asn/382

RPKI

not assessable — AS382 announces no prefixes, so there are no ROAs to validate; RIPEstat rpki-validation skipped (no prefix to supply) [Unknown] — RIPEstat rpki-validation

AS rank / customer cone / upstreams

Unknown — CAIDA fetch aborted due to timeout; not currently routed [Unknown] — CAIDA (timeout)

Notable usage

Unknown / none found — no public case studies, customer-facing service, or usage documentation; consistent with internal DoD/Air Force use [Likely] — no first-party source

Analyst note

Encountered as a dormant legacy DoD ASN with no independent registry record — it shares the AFCONC-BLOCK1-AS block entry (handle AS379). Clean, inactive, unrouted since 2017. Allocated_date is the block registration date recorded per the RIR-dates-are-facts rule, not nulled.