AS487

AS487 is a legacy autonomous system number registered under ARIN inside the block record AFCONC-BLOCK1-AS, which spans AS379 through AS508 and is held by the registrant organization "Air Force Systems Networking" (ARIN org handle 7ESG). The top-level autnum registration event for this block dates to 1989-08-04, with a last-changed event of 2008-06-06; both are first-party ARIN RDAP facts and are recorded here as the allocation date rather than the newer, unrelated dates carried by the nested contact/registrant entity objects. Administrative, abuse, and technical handling is delegated to DISA-Columbus (Defense Information Systems Agency), while the registrant address resolves to Maxwell Air Force Base, Gunther Annex, Alabama — consistent with a U.S. Air Force/DoD internal-network allocation rather than a commercial ISP. Every routing source checked (RIPEstat, CAIDA AS Rank, bgp.tools) agrees AS487 is currently unannounced: zero IPv4 and IPv6 prefixes, zero visible BGP peers or upstreams, and a CAIDA customer cone that is a singleton containing only itself. No PeeringDB net record exists for this ASN, and no NANOG, security-list, or community discussion specific to AS487 was found. No abuse signal appears in the live Spamhaus ASN-DROP feed as of 2026-07-10, consistent with a dormant, unrouted government ASN.

Operator

Air Force Systems Networking (U.S. Air Force / Department of Defense; ARIN org handle 7ESG), administratively serviced by DISA-Columbus [Confirmed] — https://rdap.arin.net/registry/autnum/487

Country / RIR

US, ARIN [Confirmed] — https://stat.ripe.net/data/abuse-contact-finder/data.json?resource=487

Allocated

1989-08-04 (ARIN RDAP top-level autnum registration event for the covering block AS379–AS508, which includes AS487); last changed 2008-06-06 [Confirmed] — https://rdap.arin.net/registry/autnum/487

Org status

active (per ARIN RDAP status field) [Confirmed] — https://rdap.arin.net/registry/autnum/487

Contacts

disa.columbus.ns.mbx.arin-registrations@mail.mil (abuse/admin/technical POC "Registration", handle REGIS10-ARIN); DISA-Columbus, 300 North James Road, Whitehall, OH 43213, US [Confirmed] — https://rdap.arin.net/registry/entity/REGIS10-ARIN

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-10 — not listed in the live Spamhaus ASN-DROP JSON feed; no bogon flag or abuse annotation on bgp.he.net, consistent with a dormant/unrouted ASN; no NANOG or security-list discussion found

Network & routing

Network type

U.S. military/government internal network infrastructure (Air Force Network), non-commercial; part of a legacy 1989 DoD block [Likely] — https://bgp.he.net/AS487

Size

dormant/unannounced — 0 IPv4 prefixes / 0 IPv4 addresses and 0 IPv6 prefixes; CAIDA customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — https://api.asrank.caida.org/v2/restful/asns/487, https://stat.ripe.net/data/routing-status/data.json?resource=487

Routing/peering

NOT announced — 0/327 RIS peers seeing it on v4, 0/321 on v6; CAIDA degree total 0 (customer 0, peer 0, provider 0); no PeeringDB net record for AS487 [Confirmed] — https://stat.ripe.net/data/routing-status/data.json?resource=487, https://www.peeringdb.com/org/20118

RPKI

not assessable — AS487 announces no prefixes, so there are no ROAs to validate; RIPEstat rpki-validation query was skipped for lack of an announced prefix [Confirmed] — https://stat.ripe.net/data/rpki-validation/data.json?resource=487

Notable usage

no independently verifiable usage beyond the registry record; AS487 shows zero announced prefixes and zero observed peers on public BGP (dormant on public BGP) [Confirmed] — https://bgp.he.net/AS487

Related ASNs

part of the ARIN block record AS379–AS508 (AFCONC-BLOCK1-AS), a single registration covering that whole numeric range under the same registrant [Confirmed] — https://rdap.arin.net/registry/autnum/487

Analyst note

Legacy DoD/Air Force block ASN, unannounced on public BGP with no commercial web presence, PeeringDB entry, or community discussion — expected profile for an internal military allocation. Allocated_date is recorded from the RDAP autnum top-level event, not the newer nested entity events (2008/2009/2025/2026), which are contact-record housekeeping dates, not the allocation date.