Autonomous system detail

AS212

Not announced

Last known operator Headquarters, Air Force Systems Command (HQAFSC). RIPEstat has no current registration record for this AS number.

Summary

// analyst note
Dormant/legacy DoD ASN. ARIN RDAP returns HTTP 404 (no autnum record served for this 1988-era legacy/.mil allocation), so allocated_date is sourced from IPinfo's ARIN-derived registry and tagged Likely. RIPEstat, bgp.he.net, and CAIDA agree on zero announcements, zero peers, zero cone.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-06-19; absent from Spamhaus ASN-DROP, CleanTalk ASN blacklist, and AbuseIPDB (404).
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: Medium

AS212 is an early, legacy autonomous system number registered under ARIN to Headquarters, Air Force Systems Command (HQAFSC) — a U.S. Air Force Major Command that conducted research, development, test, and acquisition of weapons systems from the 1950s until 1 July 1992, when it merged with Air Force Logistics Command to form Air Force Materiel Command (AFMC, Wright-Patterson AFB, Ohio). The ASN dates to the pre-commercial Internet era; third-party registry data sourced from ARIN gives an allocation date of 1988-07-07, while AFSC itself was still active. The key triage point for AS212 is that it is entirely dormant today: every routing source consulted (RIPEstat, bgp.he.net, CAIDA) agrees it announces zero IPv4 and zero IPv6 prefixes, has zero visible BGP peers, zero upstreams, and zero customers, and is not visible to any of RIPE's ~327 IPv4 / ~324 IPv6 RIS peers. ARIN RDAP returns HTTP 404 for AS212 — no autnum RDAP record is served for this legacy .mil-era allocation — so the allocation date is carried from IPinfo's ARIN-derived database rather than from an RDAP autnum top-level events[] array. RPKI posture is not assessable because there are no active originations and therefore no ROAs. No notable public abuse signal was found as of June 2026 — AS212 is absent from Spamhaus ASN-DROP, CleanTalk's ASN blacklist, and AbuseIPDB (which returns 404, consistent with zero hosted IPs), and it does not appear in NANOG security archives — which is consistent with a clean, dormant ASN held by a now-dissolved U.S. military command.

Operator
Headquarters, Air Force Systems Command (HQAFSC; ARIN handle HQAFSC-LONS-GW-AS); the command was dissolved 1992-07-01 and succeeded by Air Force Materiel Command (AFMC) [Confirmed] — ipinfo.io/AS212, bgp.he.net/AS212, en.wikipedia.org/wiki/Air_Force_Systems_Command
Country / RIR
US, ARIN (AS212 falls in IANA 16-bit block 1-1876, "Assigned by ARIN") [Confirmed] — iana.org as-numbers registry, RIPEstat as-overview, ipinfo.io/AS212
Allocated
1988-07-07 (ARIN RIR allocation date per IPinfo's ARIN-derived registry — a first-party RIR fact); read from IPinfo, not from RDAP autnum events[], because ARIN RDAP returns HTTP 404 for this legacy ASN [Likely] — ipinfo.io/AS212
Org status
dissolved — Air Force Systems Command was inactivated 1992-07-01 when it merged with Air Force Logistics Command to form Air Force Materiel Command; the ASN predates this (allocated 1988, while AFSC was active) and is held by no active operator in production use
[Confirmed] — en.wikipedia.org/wiki/Air_Force_Systems_Command, ipinfo.io/AS212
Website
Unknown — the original operator is dissolved; successor AFMC operates afmc.af.mil, but there is no official website associated with AS212 itself (an IPinfo "thera.net.br" host.io reference appears to be an unverified third-party database artifact) [Unknown] — ipinfo.io/AS212, afmc.af.mil

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-06-19 — absent from Spamhaus ASN-DROP (list dated 2026-05-29, 430 records), CleanTalk ASN blacklist, and AbuseIPDB (HTTP 404, consistent with zero hosted IPs); no NANOG security-archive mentions; dormant ASN cannot currently originate hijacks or spam

[Confirmed] — spamhaus.org/drop/asndrop.json, cleantalk.org/blacklists/asn, abuseipdb.com/asn/AS212, seclists.org/nanog/

Network & routing

Network type
U.S. Department of Defense / military government network; legacy and inactive [Confirmed] — ipinfo.io/AS212, bgp.he.net/AS212
Size
dormant — 0 IPv4 prefixes / 0 IPv4 addresses and 0 IPv6 prefixes; not announced in BGP; 0/327 RIS peers see it on v4, 0/324 on v6 [Confirmed] — RIPEstat routing-status / announced-prefixes, bgp.he.net/AS212
Routing/peering
NOT announced — 0 upstreams, 0 peers, 0 downstreams, 0 observed neighbours; no peering policy document exists [Confirmed for routing inactivity; Unknown for any policy] — bgp.he.net/AS212, ipinfo.io/AS212, RIPEstat routing-status
RPKI
not assessable — AS212 announces no prefixes, so there are no ROAs to validate [Unknown] — derived from zero announcements (RIPEstat, bgp.he.net)
Notable usage
historically the network gateway for HQ Air Force Systems Command (handle HQAFSC-LONS-GW-AS), the USAF command responsible for R&D and acquisition of major weapons systems; dormant since the command's 1992 dissolution, with no prefixes, peers, or hosted domains today [Confirmed for dormancy; Likely for the handle] — bgp.he.net/AS212, ipinfo.io/AS212, en.wikipedia.org/wiki/Air_Force_Systems_Command
Last changed
2024-11-07 (per IPinfo ARIN-derived registry) [Likely] — ipinfo.io/AS212
RDAP status
HTTP 404 from both rdap.org and ARIN — no autnum RDAP record exists for this legacy 1988-era ASN; allocation date is therefore sourced from IPinfo's ARIN-derived database, not from RDAP autnum top-level events[] [Confirmed] — A1 canonical fetch (rdap.org 404), A3 routing angle
Analyst note
encountered as a dormant legacy DoD ASN; ARIN RDAP 404 (military/legacy records not served via standard ARIN RDAP), so the allocation date is best-effort from IPinfo's ARIN-derived data and tagged [Likely]. Clean, inactive ASN.
[ 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.