AS386

AS386 is a legacy autonomous system number administered under ARIN as part of the AFCONC-BLOCK1-AS block (handle AS379, range AS379–AS508) registered to Air Force Systems Networking, a U.S. Department of the Air Force / Department of Defense entity. ARIN's RDAP resolves any ASN in the 379–508 range to this shared block-level record rather than a per-ASN object, so AS386 inherits its identity, dates, and registrant from that block — the same structure already documented for the sibling entries AS379–AS384. The registrant organization is recorded at 501 East Moore Dr., Bldg 884, Rm 1100, Gunter Annex, Maxwell AFB, AL 36114, with abuse/administrative/technical contact routed through DISA-Columbus (300 North James Road, Whitehall, OH). The key triage point is that AS386 is RDAP-active but operationally dormant: RIPEstat, db-ip, and bgp.tools all agree it announces zero IPv4 and zero IPv6 prefixes, is seen by 0 of 323 RIS v4 peers and 0 of 321 v6 peers, and has zero observed neighbours. Historical RIS visibility runs from 131.5.0.0/16 first seen on 2002-01-30 through 215.73.32.0/19 last seen on 2023-07-24, so it was routed more recently than some siblings but is not announced today. CAIDA AS Rank and customer-cone data were unavailable (fetch timeout), so those are honestly recorded as Unknown rather than inherited from a sibling. No notable public abuse signal was found as of 2026-07-02 — nothing in Spamhaus DROP, abuse.ch, AbuseIPDB, or NANOG archives — consistent with a non-routed legacy DoD block that presents no active traffic surface.

Operator

Air Force Systems Networking (U.S. Department of the Air Force / DoD; ARIN registrant org handle 7ESG, Maxwell AFB, AL; abuse/admin/tech routed through DISA-Columbus) [Confirmed] — https://rdap.arin.net/registry/autnum/386

Country / RIR

US, ARIN [Confirmed] — RIPEstat abuse-contact-finder (authoritative_rir: arin), https://stat.ripe.net/AS386

Allocated

1989-08-04 (ARIN RDAP autnum TOP-LEVEL registration event for the AFCONC-BLOCK1-AS block containing AS386 — a first-party RIR fact, NOT an IEEE date; entity/org-level dates 2008-06-05 and 2009-06-24 are decoys and were not used); last changed 2008-06-06

[Confirmed] — https://rdap.arin.net/registry/autnum/386

Org status

active per ARIN RDAP status field, but operationally dormant/unannounced; registrant Air Force Systems Networking, Maxwell AFB, AL [Confirmed] — https://rdap.arin.net/registry/autnum/386

Contacts

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; abuse/admin contact DISA-Columbus, 300 North James Road, Whitehall, OH 43213 [Confirmed] — https://rdap.arin.net/registry/autnum/386

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-02 — not in Spamhaus DROP, abuse.ch, AbuseIPDB, or NANOG archives; non-routed/inactive DoD legacy ASN with no observed announced address space [Likely] — https://www.spamhaus.org/blocklists/do-not-route-or-peer/, https://abuse.ch/, https://www.abuseipdb.com/, https://nanog.org/

Network & routing

Network type

U.S. federal government / military network (Department of the Air Force / DoD), part of the legacy AFCONC-BLOCK1-AS block (AS379–AS508); currently dormant/unrouted, not a commercial ISP or transit network [Likely] — https://rdap.arin.net/registry/autnum/386, https://bgp.tools/as/386

Size

dormant — 0 IPv4 prefixes / 0 IPv4 addresses and 0 IPv6 prefixes; announced=false [Confirmed] — https://stat.ripe.net/data/routing-status/data.json?resource=386, https://db-ip.com/as386-air-force-systems-networking

Routing/peering

NOT announced — 0 RIS peers seeing it (0/323 v4, 0/321 v6); 0 observed neighbours; no upstreams or peers visible in any source [Confirmed]. No PeeringDB net object (peeringdb.com/asn/386 = 404); no public peering policy exists for an unannounced ASN

[Confirmed] — https://stat.ripe.net/data/routing-status/data.json?resource=386, https://www.peeringdb.com/org/20118

RPKI

not assessable — AS386 announces no prefixes, so RIPEstat rpki-validation was skipped ("no --prefix supplied"); there are no ROAs to validate against a non-existent announcement [Unknown]

Notable usage

None identified. No announced prefixes, no PeeringDB presence, no public case studies or usage documentation. Historical BGP visibility 2002-01-30 (131.5.0.0/16) through 2023-07-24 (215.73.32.0/19), currently dormant

[Confirmed] — https://stat.ripe.net/data/routing-status/data.json?resource=386, https://bgp.tools/as/386

Related ASNs

block siblings AS379–AS384 (already DONE) and others within AFCONC-BLOCK1-AS (AS379–AS508) registered to the same org [Confirmed for block membership] — https://rdap.arin.net/registry/autnum/386

Analyst note

Encountered as a dormant legacy ASN within a shared ARIN block record; RDAP for AS386 returns the AS379/AFCONC-BLOCK1-AS block object by design (not a data error). CAIDA rank/cone unavailable this pass (timeout) and left Unknown rather than borrowed from a sibling.