AS389
Operated by AFCONC-BLOCK1-AS - Air Force Systems Networking.
Summary
- // analyst note
- Within-block number of a dormant/legacy military ASN block. ARIN keys resource 389 to the block record AS379 (AFCONC-BLOCK1-AS, startAutnum 379 to endAutnum 508); no discrete AS389 RDAP entity exists. RDAP status is 'active' but RIPEstat shows zero announcements and zero RIS peer visibility. CAIDA metrics (as_rank, customer_cone) could not be re-fetched (timeout) and are left null rather than assumed. All registry/routing facts match the already-DONE AS379 entry; treat as a within-block duplicate-of-DONE.
- // security note
- NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-02; not in Spamhaus DROP/SBL, AbuseIPDB, NANOG archives, or community ASN blocklists.
About this ASN.
AS389 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). The important structural fact for this entry is that ARIN does not issue a discrete RDAP record for AS389: querying autnum/389 returns the contiguous block record handle AS379, ASName AFCONC-BLOCK1-AS, spanning startAutnum 379 through endAutnum 508, and AS389 falls inside that legacy block. The registrant org (ARIN handle 7ESG) lists an address at 501 East Moore Dr., Bldg 884 Rm 1100, Gunter Annex, Maxwell AFB, AL 36114, while abuse, administrative, and technical contact routes through DISA-Columbus (300 North James Road, Whitehall, OH 43213; disa.columbus.ns.mbx.arin-registrations@mail.mil). Third-party aggregators (ipinfo.io) attribute AS389 itself, at the ASN-specific level, to Air Force Systems Networking, and community sourcing associates the block with the 754th Electronic Systems Group. The key triage point for AS389 is that it is effectively dormant: RIPEstat reports as-overview announced=false, an empty announced-prefixes array, zero RIS peer visibility (0/323 v4, 0/321 v6), zero observed neighbours, and a singleton customer cone. RDAP status remains "active." CAIDA data could not be re-fetched (query timed out), so AS-rank / customer-cone metrics for resource 389 are recorded as Unknown rather than assumed. RPKI posture is not assessable — with zero announced prefixes there are no ROAs to validate. No notable public abuse signal was found as of 2026-07-02 — not in Spamhaus DROP/SBL, AbuseIPDB, NANOG archives, or community ASN blocklists — consistent with a clean, dormant military allocation whose restricted public visibility reflects operational-security policy rather than reputation.
- Operator
- Air Force Systems Networking (U.S. DoD / U.S. Air Force; ARIN OrgId 7ESG; administered by DISA; associated with the 754th Electronic Systems Group) [Confirmed] — ARIN RDAP (https://rdap.arin.net/registry/autnum/389); ipinfo.io/AS389
- 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 of the parent block record AS379/AFCONC-BLOCK1-AS, 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/389)
- Org status
- active per ARIN RDAP; U.S. Air Force network resource administered by DISA (Gunter Annex, Maxwell AFB, AL; DISA-Columbus, OH); block-level record last changed 2008-06-06, registrant org 7ESG last updated 2025-03-13 [Confirmed] — ARIN RDAP (https://rdap.arin.net/registry/autnum/389)
- 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/389)
Security/abuse context (NEUTRAL, DATED)
no notable public abuse signal found as of 2026-07-02 — not in Spamhaus DROP/SBL, AbuseIPDB, NANOG archives, or community ASN blocklists (C0nw0nk/ASN-BlackList, brianhama/bad-asn-list, FireHOL); 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; AS389 is legacy/inactive [Confirmed] — ARIN RDAP; ipinfo.io/AS389
- Size
- dormant — 0 IPv4 prefixes / 0 IPv4 addresses and 0 IPv6 prefixes; customer cone not independently confirmed (CAIDA fetch timed out) [Confirmed for prefixes/announcements; Unknown for cone] — RIPEstat routing-status (https://stat.ripe.net/389)
- Routing/peering
- NOT announced — as-overview announced=false; announced-prefixes empty; 0 RIS peers seeing it (0/323 v4, 0/321 v6); RIPEstat observed_neighbours 0; no public peering policy published; no PeeringDB network record for AS389 (the block org page peeringdb.com/org/20118 lists no populated peering fields)[Confirmed] — RIPEstat (https://stat.ripe.net/389), peeringdb.com/org/20118
- RPKI
- not assessable — AS389 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; ipinfo.io reports no observed announcements or domains for AS389[Likely] — ipinfo.io/AS389; ARIN RDAP
- Within-block duplicate note
- ARIN keys resource 389 to the same AFCONC-BLOCK1-AS block record already fully enriched and finalized as AS379 (/asn/379/, status DONE). AS389 is not a separately allocable RDAP entity; all routing/registry facts match the parent block[Confirmed] — ARIN RDAP (https://rdap.arin.net/registry/autnum/389); /asn/379/
- Analyst note
- Encountered as a within-block number of a dormant legacy military ASN block registered to Air Force Systems Networking via DISA; RDAP status is "active" but nothing is announced. Registry data resolves to the block record AS379, not a discrete AS389 record. The absence of community/peering presence reflects deliberate DoD operational security, not a defunct or ill-reputed operator. Clean, inactive ASN. Flagging for the checker: if the pipeline treats within-block numbers as duplicates-of-DONE, AS389 may be closed rather than published as a distinct page.