Autonomous system detail

AS415

Not announced

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

Summary

// analyst note
Dormant/legacy DoD ASN. ARIN RDAP resolves to the block-level autnum record (handle AS379, startAutnum 379, endAutnum 508), not an AS415-scoped object — expected for this range, confirmed identically for AS414; allocated_date is the block registration event recorded per first-party RIR convention. RIPEstat, CAIDA, and bgp.he.net agree on zero current announcements, zero peers, zero cone. Single historical announcement (132.23.0.0/16) in late 2001.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-02; not in Spamhaus ASN-DROP, general abuse feeds, or NANOG archives.
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: High

AS415 is a legacy autonomous system number registered under ARIN to Air Force Systems Networking, a United States Air Force / Department of Defense entity, and it sits inside the AFCONC-BLOCK1-AS range (AS379AS508) carved out of ARIN's early 1–1876 "Assigned by ARIN" allocation. The ASN is effectively dormant. Every routing source consulted — RIPEstat as-overview and routing-status, CAIDA AS Rank, and bgp.he.net/bgp.tools — agrees it currently announces zero IPv4 and zero IPv6 prefixes, has zero observed BGP peers, and has no upstreams, customers, or IXP memberships. RIPEstat's historical routing record shows exactly one announcement ever on file: prefix 132.23.0.0/16, first seen 2001-09-26 and last seen 2001-10-23, a roughly four-week window in late 2001, with nothing since. CAIDA ranks it 79,459 with a singleton customer cone (itself only, 0 prefixes, 0 addresses) and zero AS-degree relationships. Registration and abuse operations are handled by DISA Columbus (abuse contact disa.columbus.ns.mbx.arin-registrations@mail.mil), consistent with sibling DoD-block ASNs like AS414. The ARIN RDAP query for AS415 resolves to the block-level autnum object (handle AS379, startAutnum 379, endAutnum 508) rather than a discrete per-ASN record — expected behavior for this legacy DoD range, confirmed identically for AS414 — so the top-level registration event of 1989-08-04 is recorded as AS415's allocated_date per the first-party RIR-registry convention. No notable public abuse signal was found as of 2026-07-02 (not in Spamhaus ASN-DROP, general abuse feeds, or NANOG archives), consistent with an inactive, unrouted military ASN.

Operator
Air Force Systems Networking (U.S. Air Force / Department of Defense; ARIN org handle 7ESG) [Confirmed] — ARIN RDAP rdap.arin.net/registry/autnum/415, bgp.he.net/AS415, ipinfo.io/AS415
AS name
AFCONC-BLOCK1-AS [Confirmed] — ARIN RDAP; CAIDA asnName AFCONC-BLOCK1-AS
Country / RIR
United States, ARIN [Confirmed] — RIPEstat abuse-contact-finder (authoritative_rir: arin), CAIDA country.iso US
Allocated
1989-08-04 (ARIN RDAP top-level autnum registration event for the AFCONC-BLOCK1-AS range; a first-party RIR registry date, NOT an IEEE/database-artifact date); last changed 2008-06-06 [Confirmed] — ARIN RDAP autnum top-level events. Caveat: RDAP returns the block-level record (AS379–AS508), so this is the containing block's registration event, not an AS415-scoped one; recorded per project convention.
Org status
registered/allocated but flagged Inactive by ipinfo.io; on-file record last updated 2008-06-06, consistent with zero current routing activity [Confirmed] — ipinfo.io/AS415
Contacts
abuse/registration disa.columbus.ns.mbx.arin-registrations@mail.mil (DISA Columbus, 300 North James Road, Whitehall, OH 43213); registrant org address 501 East Moore Dr, Bldg 884 Rm 1100, Gunter Annex, Maxwell AFB, AL 36114 [Confirmed] — RIPEstat abuse-contact-finder, ARIN RDAP
Website
Unknown — no dedicated ASN-specific operator site; ipinfo.io lists af.mil (general USAF domain), not a network-ops page [Likely] — ipinfo.io/AS415

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-02 — not in Spamhaus ASN-DROP, general abuse feeds, or NANOG archives; no live traffic to abuse-scan (unrouted)

[Likely] — spamhaus.org/drop/asndrop.txt, bgp.he.net/AS415, archive.nanog.org

Network & routing

Network type
U.S. military / DoD internal legacy ASN block (part of AFCONC-BLOCK1-AS, AS379–AS508); dormant with zero announced prefixes [Confirmed] — bgp.he.net/AS415, ARIN RDAP, RIPEstat as-overview (block.resource 1-1876, "Assigned by ARIN")
Size
dormant — 0 IPv4 prefixes / 0 IPv4 addresses and 0 IPv6 prefixes announced; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — RIPEstat routing-status / announced-prefixes / CAIDA AS Rank (2026-07-02)
Routing/peering
NOT announced — RIPEstat announced:false; 0/324 RIS peers (v4), 0/320 (v6); CAIDA degree total 0 (customer 0, peer 0, provider 0); observed_neighbours 0; no PeeringDB net record (live API 404) [Confirmed] — RIPEstat routing-status, CAIDA, peeringdb.com/api/net?asn=415
Historical routing
exactly one announcement on record — prefix 132.23.0.0/16, first_seen 2001-09-26, last_seen 2001-10-23 (~4 weeks); none since [Confirmed] — RIPEstat routing-status
RPKI
not assessable — validation endpoint requires a specific prefix (none supplied) and there is no currently announced prefix to validate against a ROA [Unknown] — RIPEstat rpki-validation (skipped)
Notable usage
none publicly documented specific to AS415; same org (7ESG) and DISA-Columbus contact as sibling ASNs in the AFCONC-BLOCK1-AS block. Community sources associate the block with Air Force Systems Networking / 754th Electronic Systems Group (secure DoD/USAF/Federal information systems)
[Likely] — hanscom.af.mil (754 ELSG), airforce.togetherweserved.com; no AS415-specific corroboration
Related ASNs
AFCONC-BLOCK1-AS block siblings AS379–AS508 (e.g. AS414, same org 7ESG, same DISA-Columbus contact) [Confirmed] — ARIN RDAP block record
Analyst note
Legacy dormant DoD ASN. RDAP resolves to the block-level record (AS379–AS508); the single 2001 announcement is the only routing ever observed. Clean, inactive.
[ 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.