Autonomous system detail

AS419

Not announced

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

Summary

// analyst note
Dormant/legacy ASN. ARIN RDAP returns the shared AS379–AS508 block record (handle AS379, name AFCONC-BLOCK1-AS); RIPEstat resource=419 and CAIDA asn=419 confirm the holder mapping. Block-level top-level registration event 1989-08-04 recorded as AS419's allocated_date (first-party RIR fact). All routing sources agree on zero announcements, zero peers, zero cone.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-02; not in Spamhaus ASN-DROP (txt+json), no NANOG archive mentions, no abuse-feed hits.
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

AS419 is a legacy autonomous system number registered under ARIN to Air Force Systems Networking, part of the U.S. Department of the Air Force and administered within Department of Defense network space managed by DISA-Columbus. ARIN's RDAP response for AS419 returns a range object spanning startAutnum 379 to endAutnum 508 (handle AS379, name AFCONC-BLOCK1-AS) — this is ARIN's standard representation for a block of sequentially allocated military AS numbers sharing a single flat registration event, not a mismatched or decoy record. That mapping is corroborated independently: RIPEstat as-overview reports resource 419 with holder "AFCONC-BLOCK1-AS - Air Force Systems Networking," and CAIDA AS Rank reports asnName AFCONC-BLOCK1-AS for asn 419, so the block record is the authoritative source for AS419's registration facts. The key triage point is that AS419 is dormant today: every routing source consulted (RIPEstat announced-prefixes and as-overview, CAIDA AS Rank) agrees it announces zero IPv4 and zero IPv6 prefixes, has zero visible peers, zero upstreams, zero customers, and a singleton customer cone (itself, 0 prefixes, 0 addresses). RIPEstat routing-status preserves a historical footprint — the ASN originated 199.251.253.0/24 (first seen 2000-08-25) and 132.25.0.0/16 (last seen 2003-01-16) — but no RIS peer has seen any announcement since (0 of 324 v4 peers, 0 of 320 v6 peers). Its CAIDA AS rank of 79,459 reflects that complete routing inactivity. RPKI posture is not assessable because there are no active originations and therefore no ROAs to validate. No notable public abuse signal was found as of 2026-07-02 — AS419 is absent from the Spamhaus ASN-DROP list (checked live in both txt and json form dated 2026/07/02), has no NANOG archive mentions, and no abuse-feed hits — consistent with a clean, dormant number inside a legacy DoD/USAF block allocated in 1989.

Operator
Air Force Systems Networking (U.S. Air Force / DoD; registrant org handle 7ESG, Maxwell AFB, AL 36114; admin/tech/abuse via DISA-Columbus, Whitehall, OH 43213) [Confirmed] — ARIN RDAP autnum/419 registrant + entity records
Country / RIR
US, ARIN [Confirmed] — RIPEstat abuse-contact-finder (authoritative_rir: arin)
Allocated
1989-08-04 (ARIN registry date, NOT an IEEE date — IEEE publishes no ASN registration dates); last changed 2008-06-06 [Confirmed] — ARIN RDAP autnum top-level events (registration event on the AS379–AS508 block record that includes AS419)
Org status
active U.S. federal/military registrant (Air Force Systems Networking / DoD; DISA-Columbus administers) [Confirmed] — ARIN RDAP autnum/419
Website
Unknown — no operator-published page specific to AS419; af.mil/disa.mil publish no per-ASN network documentation [Unknown] — disa.mil, help.disa.mil/network-connections
Contacts
disa.columbus.ns.mbx.arin-registrations@mail.mil (DISA-Columbus, +1-844-347-2457 ext2) [Confirmed] — ARIN RDAP entity REGIS10-ARIN / RIPEstat abuse-contact-finder

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-02 — not in Spamhaus ASN-DROP (txt+json, dated 2026/07/02), no NANOG archive mentions, no abuse-feed hits; org-level Scamalytics aggregate for "Air Force Systems Networking" shows 0/100 fraud risk. Absence of evidence on an unrouted ASN, not a live-traffic clean bill

[Likely] — spamhaus.org/drop/asndrop.txt, spamhaus.org/drop/asndrop.json, scamalytics.com/ip/isp/air-force-systems-networking

Network & routing

Network type
U.S. federal/military network block; AS419 is legacy/inactive (unrouted since 2003) [Likely] — ARIN RDAP (registrant DoD/USAF), ipinfo.io/AS419 (classified "Inactive")
Size
dormant — 0 IPv4 prefixes / 0 IPv4 addresses and 0 IPv6 prefixes; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — RIPEstat announced-prefixes / as-overview, CAIDA AS Rank (2026-07)
Routing/peering
NOT announced — as-overview announced=false; 0 RIS peers seeing it (0/324 v4, 0/320 v6); CAIDA degree total 0 (customer 0, peer 0, provider 0); RIPEstat observed_neighbours 0 [Confirmed]. No PeeringDB network record exists (peeringdb.com/asn/419 → 404), consistent with an inactive government ASN with no public peering presence [Likely]
RPKI
not assessable — AS419 announces no prefixes, so there are no ROAs to validate [Unknown/N-A] — RIPEstat rpki-validation requires a prefix; none announced
Routing history
historically announced but not currently visible — first_seen 199.251.253.0/24 (2000-08-25, origin AS419), last_seen 132.25.0.0/16 (2003-01-16, origin AS419); no announcements since [Confirmed] — RIPEstat routing-status
Notable usage
none documented — no hosted domains, no announced prefixes, no peers/upstreams/downstreams found on any source consulted [Likely] — ipinfo.io/AS419, bgp.tools/as/419
Analyst note
Encountered as a dormant legacy ASN inside the AS379–AS508 military block. ARIN RDAP returns the shared block record (handle AS379); RIPEstat resource=419 and CAIDA asn=419 confirm the holder mapping, so the block-level 1989-08-04 registration date is recorded as AS419's allocated_date (first-party RIR fact), not nulled.
[ 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.