AS619

AS619 is a legacy autonomous system number carved from ARIN block DNIC-ASBLK-00616-00665 (covering AS616 through AS665), registered to the United States Department of Defense and administratively handled by DISA-Columbus on the DoD's behalf. The ARIN RDAP autnum record's top-level registration event dates the block to 1990-04-19, with a last-changed event of 2025-09-12; this is a first-party registry fact, not a database-artifact date, and is recorded here as such. Live routing data shows AS619 originating exactly two IPv4 prefixes — 163.251.120.0/24 and 163.251.121.0/24, 512 addresses total — both of which resolve in ARIN WHOIS to the Navy Network Information Center (NNIC) inside the larger 163.251.0.0/16 block ("SRFYOKONET2," registered 2006-09-21). No IPv6 is announced. The ASN sits near-fully visible in the IPv4 default-free zone (326 of 327 RIS peers) with a single observed BGP neighbor, AS27066, itself another DoD-registered ASN. CAIDA's topology data resolves that single edge as a provider relationship — AS619 has one provider (AS27066), zero peers, and zero customers — and its customer cone is a singleton: 1 ASN, 2 prefixes, 512 addresses, i.e. the ASN and its own announcements alone. That is a pattern consistent with a small, largely self-contained military routing block reaching the DFZ through one DoD upstream rather than a commercial network with public transit or peering. There is no dedicated operator website, no PeeringDB profile, and no published peering policy; DoD external connectivity instead runs through DISA's controlled DISN connection-approval process. No notable public abuse signal was found as of 2026-07-17.

Operator

United States Department of Defense (DoD); ARIN registrant handle USDDD; administrative/abuse contact via DISA-Columbus [Confirmed] — https://rdap.arin.net/registry/autnum/619

Country / RIR

US, ARIN [Confirmed] — https://rdap.arin.net/registry/autnum/619 ; https://stat.ripe.net/AS619

Allocated

1990-04-19 (ARIN RDAP autnum top-level registration event, block DNIC-ASBLK-00616-00665 covering AS619); last changed 2025-09-12 [Confirmed] — https://rdap.arin.net/registry/autnum/619

Org status

Active per ARIN; block DNIC-ASBLK-00616-00665, org "United States Department of Defense (DoD)," last modified 2025-09-12 [Confirmed] — https://rdap.arin.net/registry/autnum/619

Website

no dedicated official website exists for AS619 or for NNIC as a public operator page; the historical DoD Network Information Center site (nic.mil) is defunct (archived 2008) [Confirmed] — https://www.disa.mil/

Security/abuse context (NEUTRAL, DATED)

not present on Spamhaus ASN-DROP as of 2026-07-17; no NANOG/security-mailing-list discussion of AS619 located; AbuseIPDB's check page returned HTTP 403 to automated fetch and could not be verified, so its status is recorded as Unknown rather than clean or flagged [Likely for Spamhaus/NANOG; Unknown for AbuseIPDB] — https://www.spamhaus.org/drop/asndrop.json

Network & routing

Network type

Government/Military — DoD internal network infrastructure (Navy component), not a commercial ISP or public peering network [Confirmed] — https://rdap.arin.net/registry/autnum/619 ; https://bgp.he.net/AS619

Size

2 IPv4 prefixes announced (163.251.120.0/24, 163.251.121.0/24; 512 addresses); 0 IPv6 prefixes [Confirmed] — https://stat.ripe.net/AS619 ; https://bgp.he.net/AS619 ; https://bgp.tools/as/619

CAIDA AS rank

54406; clique member: true; customer cone = singleton (1 ASN; 2 prefixes; 512 addresses) — the cone contains only AS619 itself and its own two announcements [Confirmed] — https://asrank.caida.org/asns/619

CAIDA AS degree

total 1 — 1 provider, 0 peers, 0 customers. The single observed neighbor AS27066 is a provider (upstream), not a lateral peer, which matches the zero-customer singleton cone [Confirmed] — https://asrank.caida.org/asns/619

Upstreams / peering relationships

AS27066 (sole upstream/provider, also US DoD); no peer or customer relationships observed [Confirmed] — https://asrank.caida.org/asns/619 ; https://stat.ripe.net/AS619

Peering/routing hygiene

no PeeringDB profile exists for AS619 (404); no published peering policy — DoD external connectivity runs through DISA's controlled DISN connection-approval process rather than open peering. bgp.he.net flags no RPKI-valid origins and an IRR origin-mismatch on one announced prefix — a routing-hygiene note, not a confirmed abuse finding

[Likely] — https://www.peeringdb.com/asn/619 ; https://bgp.he.net/AS619

RPKI posture

unsigned (NotFound) — RIPEstat's rpki-validation endpoint, validator Routinator, returns status "unknown" with an empty validating_roas[] for both announced prefixes, 163.251.120.0/24 and 163.251.121.0/24, originated by AS619, as of 2026-07-28. No ROA covers either announcement, so both are RPKI-NotFound rather than valid or invalid — consistent with bgp.he.net's "no RPKI-valid origins" flag [Confirmed] — https://stat.ripe.net/data/rpki-validation/data.json?resource=AS619&prefix=163.251.120.0/24, https://stat.ripe.net/data/rpki-validation/data.json?resource=AS619&prefix=163.251.121.0/24, https://bgp.he.net/AS619

Notable usage

the two announced prefixes register in ARIN WHOIS to the Navy Network Information Center (NNIC, handle NNICN-1) within the larger 163.251.0.0/16 allocation ("SRFYOKONET2," registered 2006-09-21) [Confirmed] — https://rdap.arin.net/registry/ip/163.251.120.0

Related ASNs

AS27066 (sole observed BGP neighbor and CAIDA-confirmed provider, also US DoD) [Confirmed]; the block also spans AS616–AS665 under the same DoD registrant [Likely] — https://stat.ripe.net/AS619 ; https://asrank.caida.org/asns/619

Visibility

IPv4 seen by 326/327 RIS peers; IPv6 seen by 0/322 RIS peers; 1 observed BGP neighbor (AS27066, also US DoD) [Confirmed] — https://stat.ripe.net/AS619

Analyst note

legacy DoD ASN block; ARIN returns the parent DNIC-ASBLK-00616-00665 record (handle shown as "AS616") for any ASN in the 616–665 range, but the RDAP links[] confirm the response is scoped to autnum/619. Entity-level contact dates (e.g. MIL-HSTMST-ARIN, REGIS10-ARIN "last changed" 2026-02-12) are decoys and were not used for allocated_date.