Autonomous system detail

AS446

Not announced

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

Summary

// analyst note
Dormant/legacy ASN with no independent ARIN autnum object — covered by the AS379–AS508 AFCONC-BLOCK1-AS block. All routing sources (RIPEstat, CAIDA, bgp.he.net) agree on zero current announcements, zero peers, zero cone. allocated_date 1989-08-04 and last-changed 2008-06-06 are block-level RDAP top-level events.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-02; not in Spamhaus ASN-DROP, general web/abuse searches, 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

AS446 is a legacy autonomous system number registered under ARIN with no independent delegation of its own: it falls inside a single flat-range ARIN autnum object, AFCONC-BLOCK1-AS, that spans AS379 through AS508 and is held by Air Force Systems Networking, an organization of the U.S. Department of the Air Force / Department of Defense with IP management delegated to the Defense Information Systems Agency (DISA). Because ARIN exposes only the block-level record, the registrant org (handle 7ESG, Maxwell AFB, AL) and the top-level RDAP registration event of 1989-08-04 both describe the AS379–AS508 block rather than AS446 uniquely. The key triage point for AS446 is that it is effectively dormant today: RIPEstat as-overview reports it as not announced, and every routing source consulted (RIPEstat, CAIDA AS Rank, Hurricane Electric BGP Toolkit) agrees it originates zero IPv4 and zero IPv6 prefixes, has zero visible RIS peers (0/325 v4, 0/321 v6), zero upstreams, zero customers, and no IXP presence. Its CAIDA AS rank of 79,459 sits near the bottom of the global ranking, reflecting complete routing inactivity, and its customer cone is a singleton (the ASN itself, 0 prefixes, 0 addresses). Historically it did announce 199.251.27.0/24, first seen 2000-08-18 and last seen 2004-05-08, with no announcements since. RPKI posture cannot be assessed because there are no active originations and therefore no ROAs. No notable public abuse signal was found as of 2026-07-02 — not in Spamhaus ASN-DROP, general web/abuse searches, or NANOG archives — consistent with a clean, dormant ASN held by a U.S. government/military operator.

Operator / registrant
Air Force Systems Networking (ARIN org handle 7ESG, Maxwell AFB, AL; U.S. DoD/USAF, IP management via DISA) [Confirmed] — ARIN RDAP autnum (https://rdap.arin.net/registry/autnum/446)
Country / RIR
US, ARIN [Confirmed] — RIPEstat abuse-contact-finder (authoritative_rir: arin) (https://stat.ripe.net/data/abuse-contact-finder/data.json?resource=446)
Allocated
1989-08-04 (ARIN RDAP autnum top-level registration event; NOT an IEEE date — RIR dates are first-party facts). This is a block-level date for the AS379–AS508 AFCONC-BLOCK1-AS range, as ARIN exposes no autnum object for AS446 alone; last changed 2008-06-06
[Confirmed] — ARIN RDAP autnum top-level events (https://rdap.arin.net/registry/autnum/446)
Block context
AS446 is one member of the flat autnum range AS379–AS508 (startAutnum 379 / endAutnum 508), registered as AFCONC-BLOCK1-AS [Confirmed] — ARIN RDAP autnum (https://rdap.arin.net/registry/autnum/446)
Website / peering policy
none found — no dedicated operator or ASN-specific website; no published peering policy; generic DoD/DISA sites carry no ASN-level content [Unknown] — help.disa.mil/network-connections, peeringdb.com/asn/446
Contacts
abuse disa.columbus.ns.mbx.arin-registrations@mail.mil (DISA-Columbus, Whitehall, OH) [Confirmed] — RIPEstat abuse-contact-finder / ARIN RDAP
Org status
active per ARIN RDAP status on the parent block record; no independent current routing activity observed for AS446 specifically [Confirmed] — ARIN RDAP autnum

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-02 — not in Spamhaus ASN-DROP, general web/abuse searches, or NANOG archives; consistent with a dormant/unannounced ASN

[Likely] — spamhaus.org/drop/asndrop.txt, bgp.he.net/AS446

Network & routing

Network type
government/military (U.S. Department of Defense, Air Force) — not a commercial ISP or enterprise network [Likely] — ARIN RDAP registrant org
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 (2026-07)
Routing/peering
NOT announced — RIPEstat as-overview announced=false; 0 RIS peers seeing it (0/325 v4, 0/321 v6); CAIDA degree total 0 (customer 0, peer 0, provider 0); no upstreams or peers visible in any source; no PeeringDB record (404) [Confirmed] — RIPEstat as-overview / peeringdb.com/asn/446
Historical routing
announced 199.251.27.0/24, first seen 2000-08-18, last seen 2004-05-08; no announcements since [Confirmed] — RIPEstat routing-status (https://stat.ripe.net/data/routing-status/data.json?resource=446)
RPKI
not assessable — AS446 announces no prefixes, so there are no ROAs to validate [Unknown] — RIPEstat rpki-validation requires an announced prefix
CAIDA AS rank
79459; not a clique member; no IXP presence [Confirmed] — CAIDA AS Rank (https://api.asrank.caida.org/v2/restful/asns/446)
Community mentions
none specific to AS446 found in NANOG archives or Reddit networking communities; absence reflects low public visibility of government/military networks, not a problem signal [Unknown] — NANOG archive / web search
Analyst note
Encountered as a dormant legacy ASN with no independent ARIN delegation — it is one member of the AS379–AS508 AFCONC-BLOCK1-AS range held by Air Force Systems Networking (DoD/USAF, DISA-managed). All routing sources agree on zero current announcements. 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.