AS402
Operated by AFCONC-BLOCK1-AS - Air Force Systems Networking.
Summary
- // analyst note
- ARIN records AS402 as part of a BLOCK autnum (handle AS379, startAutnum 379, endAutnum 508, name AFCONC-BLOCK1-AS), not a per-ASN record. allocated_date 1989-08-04 and last-changed 2008-06-06 are the autnum TOP-LEVEL events. Entity-nested dates (REGIS10-ARIN 2009-06-24, org 7ESG 2008-06-05) excluded. CAIDA AS-rank/customer-cone unavailable (source timeout).
- // security note
- NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-02; not in Spamhaus DROP/ASN-DROP, NANOG archives, or general abuse searches.
About this ASN.
AS402 is a legacy autonomous system number registered under ARIN to Air Force Systems Networking, a U.S. Department of Defense / United States Air Force organization (ARIN registrant org handle 7ESG, address Maxwell AFB, Alabama; administrative and abuse contact handled by DISA-Columbus in Whitehall, Ohio). It was allocated in the pre-CIDR era, on 1989-08-04, and its ARIN record is modeled as a block registration — a single autnum object with handle AS379, spanning startAutnum 379 through endAutnum 508 under the name AFCONC-BLOCK1-AS — rather than an individual per-ASN record. AS402 falls within that covering block. The key triage point is that AS402 is operationally dormant: RIPEstat's as-overview reports announced=false, announced-prefixes returns an empty array, and routing-status shows zero IPv4 and zero IPv6 prefixes with zero of roughly 323/321 RIS peers observing any announcement and zero observed neighbours. Historical routing shows the ASN was visible in BGP only between 2002-02-05 (first_seen 129.198.0.0/16) and 2008-10-10 (last_seen 198.220.159.0/24), which aligns closely with the autnum's last-changed date of 2008-06-06 and suggests the AS went quiet shortly thereafter. RPKI posture is not assessable because no prefix is currently announced. No notable public abuse, spam-listing, or BGP-hijack signal was found for AS402 specifically as of 2026-07-02 — searches against Spamhaus, NANOG archives, and general abuse terms surfaced only unrelated nearby ASNs — which is consistent with a DoD/Air Force administrative block rather than a commercial transit, hosting, or access network.
- Operator
- Air Force Systems Networking (U.S. Air Force / DoD; ARIN registrant org handle 7ESG, Maxwell AFB, AL 36114; admin/abuse via DISA-Columbus, Whitehall, OH 43213) [Confirmed] — ARIN RDAP autnum/402
- 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; this covers the AS379–508 block containing AS402 — RIR registry dates are first-party facts, NOT IEEE dates); last changed 2008-06-06 [Confirmed] — ARIN RDAP autnum top-level events
- Org status
- registry status "active" at ARIN (on the covering AS379–508 block record), but operationally dormant / not announcing routes on the public Internet [Confirmed] — ARIN RDAP, RIPEstat as-overview
- Website
- none dedicated — AS402 is a legacy USAF block with no operator-specific site; no AS402-specific page found [Likely] — ARIN RDAP
- Contacts
- abuse/admin/technical — disa.columbus.ns.mbx.arin-registrations@mail.mil (DISA-Columbus, handle REGIS10-ARIN), phone +1-844-347-2457 ext2 [Confirmed] — ARIN RDAP, RIPEstat abuse-contact-finder
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 general abuse searches (only unrelated nearby ASNs surfaced); dormant DoD/Air Force administrative block
Network & routing
- Network type
- U.S. federal/military legacy ASN block (not a commercial ISP, hosting provider, or content network); AS402 is legacy/inactive [Confirmed] — ARIN RDAP autnum/402
- Size
- dormant — 0 IPv4 prefixes / 0 IPv4 addresses and 0 IPv6 prefixes; not visible in the global routing table [Confirmed] — RIPEstat routing-status / announced-prefixes (2026-07)
- Routing/peering
- NOT announced — announced=false; 0 RIS peers seeing it (0/323 v4, 0/321 v6); 0 observed neighbours; no upstreams or peers visible in any source [Confirmed] — RIPEstat as-overview / routing-status. No PeeringDB network object exists for AS402, so no peering policy is published[Confirmed] — peeringdb.com/org/20118
- RPKI
- not assessable — AS402 announces no prefixes, so there are no ROAs to validate; RIPEstat rpki-validation was skipped (no announced prefix) [Confirmed] — RIPEstat
- Notable usage
- none current; historically visible in BGP only 2002-02-05 (129.198.0.0/16) to 2008-10-10 (198.220.159.0/24), consistent with a U.S. military network that went dormant after 2008 [Confirmed] — RIPEstat routing-status
- Related ASNs
- part of the AFCONC-BLOCK1-AS block (AS379–AS508); PeeringDB lists other Air Force Systems Networking ASNs (e.g. AS65, AS123, AS175, AS221, AS301), but NOT AS402 [Confirmed for block; Likely for the broader list per PeeringDB] — peeringdb.com/org/20118
- Analyst note
- AS402's ARIN record is a BLOCK registration (handle AS379, startAutnum 379, endAutnum 508), not an individual per-ASN record. The 1989-08-04 registration and 2008-06-06 last-changed are the autnum top-level events for that block and are the correct dates to record for AS402. Entity-nested dates (REGIS10-ARIN registration 2009-06-24; org 7ESG registration 2008-06-05) are contact/org record dates and were excluded. CAIDA AS-rank/customer-cone data was unavailable (source timed out).