AS424
Operated by AFCONC-BLOCK1-AS - Air Force Systems Networking.
Summary
- // analyst note
- Dormant/legacy military ASN. ARIN RDAP returns the shared AS379 block record (startAutnum 379, endAutnum 508), not an AS424-specific sub-record — a legacy-block artifact; RIPEstat and CAIDA both return holder AFCONC-BLOCK1-AS for resource 424. Nested entity events (2009-06-24, 2008-06-05) are contact/org events; the autnum top-level registration event (1989-08-04) is the allocated_date. All routing sources agree on zero announcements, zero peers, zero cone.
- // security note
- NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-02; not in Spamhaus ASN-DROP, CleanTalk, AbuseIPDB, or NANOG archives.
About this ASN.
AS424 is a legacy autonomous system number registered under ARIN to the U.S. Air Force. It is not an individually registered ASN: ARIN records it as one member of a flat block-registration autnum record spanning AS379 through AS508 (handle AS379, name AFCONC-BLOCK1-AS, "Air Force Consolidated Block 1"), and the registrant entity is "Air Force Systems Networking" (org handle 7ESG) at Gunther Annex, Maxwell AFB, Alabama. The administrative, technical, and abuse contact is DISA-Columbus (Defense Information Systems Agency, handle REGIS10-ARIN) in Whitehall, Ohio. The key triage point for AS424 is that it is dormant. Every routing source consulted — RIPEstat routing-status, CAIDA AS Rank, Hurricane Electric (bgp.he.net), bgp.tools, and IPinfo — agrees it announces zero IPv4 and zero IPv6 prefixes today, is seen by 0 of 324 RIS peers (v4) and 0 of 320 (v6), and has zero observed BGP neighbours. Its CAIDA AS rank of 79,459 sits near the bottom of the global ranking and its customer cone is a singleton (the ASN itself, 0 prefixes, 0 addresses). The only historical routing on record is 129.53.0.0/16, first seen 2000-08-18 and last seen 2002-08-14 — nothing since. RPKI posture cannot be assessed because there are no active originations and therefore no ROAs. No PeeringDB record exists for AS424 (direct API query returned 404), consistent with a DoD internal allocation whose external connectivity, where present, is gated through DISN/DISA primary ASNs rather than AS424 itself. No notable public abuse signal was found as of 2026-07-02 — not in Spamhaus ASN-DROP, CleanTalk, AbuseIPDB, or NANOG archives — consistent with a clean, non-routed ASN held by a military operator.
- Operator
- Air Force Systems Networking (U.S. Air Force; ARIN org handle 7ESG, Gunther Annex, Maxwell AFB, AL 36114); AS424 is a member of ARIN's flat block record AFCONC-BLOCK1-AS (AS379–508) [Confirmed] — ARIN RDAP, ipinfo.io/AS424
- Country / RIR
- US, ARIN [Confirmed] — RIPEstat abuse-contact-finder (authoritative_rir: arin), CAIDA country.iso US
- Allocated
- 1989-08-04 (ARIN registry date — autnum top-level "registration" event for the AS379–508 block record that contains AS424; NOT an IEEE date, IEEE publishes no ASN registration dates); last changed 2008-06-06 [Confirmed] — ARIN RDAP autnum top-level events. Note: ARIN returns a single flat record for the whole 379–508 range rather than a per-ASN record, so this registration date applies at the block level; recorded as the RIR registry date per the rule that RIR RDAP registration dates are first-party facts and are not nulled.
- Org status
- active (per ARIN RDAP status field for the containing block record); no indication of deallocation [Confirmed] — ARIN RDAP
- Contacts
- DISA-Columbus (handle REGIS10-ARIN), disa.columbus.ns.mbx.arin-registrations@mail.mil, +1-844-347-2457 ext2, 300 North James Road, Whitehall, OH 43213, US; registrant address 501 East Moore Dr. Bldg 884 Rm 1100 Gunther Annex, Maxwell AFB, AL 36114[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 ASN-DROP, CleanTalk, AbuseIPDB, or NANOG archives; a non-routed ASN generates no live traffic to be flagged. Treat as a sourced, dated null, not a confirmed clean scan
Network & routing
- Network type
- U.S. military / government network numbering resource (Air Force); not a commercial ISP, content, or enterprise network. AS424 is legacy/inactive [Confirmed] — ARIN RDAP
- 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 / CAIDA AS Rank / bgp.he.net / bgp.tools (2026-07)
- Routing/peering
- NOT announced — 0 RIS peers seeing it (0/324 v4, 0/320 v6); CAIDA degree total 0 (customer 0, peer 0, provider 0); no upstreams or peers visible in any source [Confirmed]. Historical origination: 129.53.0.0/16 first_seen 2000-08-18, last_seen 2002-08-14 — not announced since 2002[Confirmed] — RIPEstat routing-status
- Peering policy
- none active (AS424 announces nothing); no PeeringDB record exists (direct API query returned HTTP 404) and no public peering-policy page was found [Confirmed] — peeringdb.com/api/net?asn=424 (404), bgp.he.net/AS424
- RPKI
- not assessable — AS424 announces no prefixes, so there are no ROAs to validate; RIPEstat rpki-validation was skipped for lack of an announced prefix [Confirmed] — RIPEstat
- Notable usage
- none identified — no active BGP announcements, no originated prefixes, and no third-party coverage of AS424 specifically. General context: the parent block (AFCONC-BLOCK1-AS, AS379–508) is Air Force infrastructure administered by DISA-Columbus [Confirmed] — bgp.he.net/AS424, ARIN RDAP
- Related ASNs
- AS379–AS508 share the AFCONC-BLOCK1-AS block record; sibling AS383 (754th Electronic Systems Group, same block) was the #1 unstable origin in a May 2012 BGP Update Report (cause not publicly documented) [Likely] — RIPE routing-wg archive
- Analyst note
- Encountered as a dormant legacy military ASN. ARIN's RDAP returns the shared AS379 block-level record (startAutnum 379, endAutnum 508) rather than an AS424-specific sub-record — a known ARIN legacy-block artifact; RIPEstat as-overview and CAIDA both independently return holder "AFCONC-BLOCK1-AS" for resource 424, confirming the block record is authoritative for AS424. The nested entity events (2009-06-24 REGIS10-ARIN, 2008-06-05 7ESG) are contact/org events, NOT the allocation date; the autnum top-level registration event (1989-08-04) is the allocated_date.