Autonomous system detail

AS462

Not announced

Operated by AFCONC-BLOCK1-AS - Air Force Systems Networking.

Summary

// analyst note
Dormant legacy DoD/Air Force block ASN. ARIN RDAP for the number 462 resolves to the containing block record (AS379-508, handle AS379), not a distinct singleton; the block's top-level registration date (1989-08-04) is recorded as AS462's allocated_date per RIR convention. RIPEstat and CAIDA independently agree on zero announcements, zero peers, zero cone.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-05; not in Spamhaus, abuse.ch/urlhaus, NANOG archives, or BGP hijack/route-leak trackers.
IPv4 prefixes
0
~0 addresses
IPv6 prefixes
0
Peer networks
0
0 up · 0 down
IANA block
1-1876
Assigned by ARIN
[ 01 ] — Context

About this ASN.

Updated  ·  Confidence: Moderate

AS462 is a legacy autonomous system number that sits inside a large ARIN-registered block, AS379AS508, named AFCONC-BLOCK1-AS and assigned to "Air Force Systems Networking," an organization tied to the United States Air Force. ARIN's RDAP autnum lookup for the number 462 resolves to this encompassing block record (handle AS379) rather than a distinct singleton record — standard behavior for a legacy range allocated as a contiguous unit. The block's registrant organization (handle 7ESG) carries an address at Maxwell Air Force Base, Alabama, while the administrative/abuse contact is routed through DISA-Columbus in Whitehall, Ohio, reflecting the Defense Information Systems Agency's role in managing DoD numbering resources on the Air Force's behalf. Every routing source checked — RIPEstat and CAIDA AS Rank — agrees AS462 is currently unannounced: zero IPv4 and zero IPv6 prefixes, zero of 325 RIS peers seeing it in IPv4 and zero of 321 in IPv6, zero observed neighbours, and a CAIDA customer cone of a single ASN (itself) with zero prefixes and zero addresses. CAIDA's AS rank (79,459) sits near the bottom of the global ranking, consistent with total routing inactivity. No dedicated operator or peering website was found for AS462 specifically; the closest official parent-organization material is general Air Force Network Integration Center background at acc.af.mil, which is not AS462-specific. No PeeringDB profile lists AS462 (a related Air Force Systems Networking PeeringDB org exists but enumerates different ASNs). No notable public abuse signal, BGP hijack, or route-leak incident was found for AS462 as of 2026-07-05 — expected for a block with no active announcements to generate abuse telemetry against.

Operator
Air Force Systems Networking (United States Air Force / DoD); ARIN org handle 7ESG, address 501 East Moore Dr, Bldg 884, Rm 1100, Gunther Annex, Maxwell AFB, AL 36114, US [Confirmed] — https://rdap.arin.net/registry/autnum/462
Country / RIR
US, ARIN [Confirmed] — https://rdap.arin.net/registry/autnum/462
Allocated
1989-08-04 (ARIN RDAP top-level registration event for the containing block AS379–508, handle AS379, "AFCONC-BLOCK1-AS," which encompasses AS462; this is the registry's first-party registration date for the block and is recorded as AS462's allocated_date per RIR convention for legacy block registrations); last changed 2008-06-06 [Confirmed] — https://rdap.arin.net/registry/autnum/462. Entity-level dates (contact REGIS10-ARIN registered 2009-06-24; registrant org 7ESG registered 2008-06-05) are excluded as decoys — they are contact/org record dates, not the autnum's own top-level event.
Org status
active registration at ARIN (org handle 7ESG, status "active"); ASN itself shows no current routing activity [Confirmed] — https://rdap.arin.net/registry/autnum/462
Contacts
disa.columbus.ns.mbx.arin-registrations@mail.mil (abuse/administrative, via DISA-Columbus) [Confirmed] — https://stat.ripe.net/data/abuse-contact-finder/data.json?resource=462

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-05 — checked general web search, Spamhaus, abuse.ch/urlhaus, NANOG archive search (dominated by unrelated Alaska Airlines flight AS462 results), CAIDA AS Rank, and BGP hijack/route-leak trackers (BGPStream/MANRS/Atlantic Council); no hits. Absence is expected given zero announced routes to generate traffic-based abuse telemetry

[Likely] — https://ipinfo.io/AS462, https://urlhaus.abuse.ch/asn/3462/

Network & routing

Network type
U.S. military/government network (Air Force enterprise networking infrastructure), not a commercial ISP or content network [Confirmed] — https://ipinfo.io/AS462
Size
dormant — 0 IPv4 prefixes / 0 IPv4 addresses and 0 IPv6 prefixes announced; CAIDA customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — https://stat.ripe.net/AS462, https://asrank.caida.org/asns/462
Routing/peering
NOT announced — 0 of 325 RIS peers seeing it in IPv4, 0 of 321 in IPv6, 0 observed neighbours; CAIDA degree total 0 (customer 0, peer 0, provider 0), cliqueMember false, seen false [Confirmed] — https://stat.ripe.net/AS462, https://asrank.caida.org/asns/462. No public peering policy found (no PeeringDB record, no IRR peering-policy object for AS462 specifically) [Likely]
RPKI
not assessable — RIPEstat's rpki-validation was skipped because no prefix was supplied (a prefix is required for ROA validation), and AS462 has no announced prefixes to validate against [Unknown]
Notable usage
none identified — no public prefixes are currently announced, and IPinfo shows zero hosted domains; appears to be one of many ASNs bulk-assigned to Air Force Systems Networking, likely reserved/administrative rather than actively used for a distinct visible service [Likely] — https://ipinfo.io/AS462
Related ASNs
part of the AS379–AS508 block ("AFCONC-BLOCK1-AS") held by the same registrant organization [Confirmed] — https://rdap.arin.net/registry/autnum/462
Analyst note
Legacy DoD/Air Force block ASN, dormant with no active announcements. RDAP resolves to the containing block record (AS379–508) rather than a distinct AS462 singleton, which is standard for legacy bulk-allocated ranges; the block's top-level registration date is recorded here as AS462's allocated_date per instructions, since it is a first-party ARIN RDAP fact and not an entity/contact date.
[ 02 ] — Announced prefixes

What this network routes.

0 prefixes total · RIPEstat data · cached, not real-time
// IPv4 prefixes0
No IPv4 prefixes announced.
// IPv6 prefixes0
No IPv6 prefixes announced.
[ 03 ] — Notable peers & upstreams

Who it talks to.

0 observed neighbours
Neighbour data unavailable from public BGP collectors.