Autonomous system detail

AS654

Not announced

Operated by DNIC-ASBLK-00616-00665 - United States Department of Defense (DoD).

Summary

// analyst note
Registered but dormant DoD ASN within the DNIC-ASBLK-00616-00665 block (AS616-AS665). All routing sources agree on zero announcements, zero peers, and a singleton customer cone. No AS654-specific operator website or peering-policy page exists; the registrant is the U.S. DoD generally, managed via DISA-Columbus.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-17; Spamhaus's own lookup tool (check.spamhaus.org) returned HTTP 403 and could not be queried directly, so this is an unconfirmed absence based on secondary web search, not a verified clean record.
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

AS654 is part of a block-level ARIN autnum registration, DNIC-ASBLK-00616-00665, spanning AS616 through AS665 and registered as a single record to the United States Department of Defense (DoD). ARIN's RDAP record shows this block was registered on 1990-04-19, with the record itself last changed on 2025-09-12; day-to-day administration runs through DISA-Columbus, the DoD Network Information Center's operational contact for this ASN space. AS654 is not currently visible in the global routing table: RIPEstat, bgp.he.net, bgp.tools, and CAIDA's ASRank all agree it announces zero IPv4 and zero IPv6 prefixes, has zero observed BGP peers or upstreams, and sits in a customer cone of exactly one ASN (itself). CAIDA ranks it 79,459 of all observed ASNs, near the bottom, consistent with a dormant or reserved allocation rather than an actively routed network. PeeringDB carries an "Open" peering-policy field for AS654, but the entry has no announced prefixes or facilities attached, so it reads as an unpopulated placeholder rather than evidence of live interconnection. No public abuse, hijack, or NANOG community discussion naming AS654 was found in this research pass; that absence is treated as an honest data gap, not a verified clean record, since Spamhaus's own lookup tool returned a 403 and could not be queried directly.

Country / RIR
US, ARIN [Confirmed] — RIPEstat abuse-contact-finder (authoritative_rir: arin)
Allocated
1990-04-19 — ARIN autnum TOP-LEVEL registration event on the block record covering AS654 (block last changed 2025-09-12) [Confirmed] — ARIN RDAP autnum top-level events, corroborated independently by bgp.tools ("registered on April 19, 1990")
Org status
active per ARIN RDAP (status: active); block record last changed 2025-09-12 [Confirmed] — ARIN RDAP

Abuse contact

disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil

[Confirmed] — RIPEstat abuse-contact-finder

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-17; check.spamhaus.org could not be queried directly (HTTP 403), so this rests on secondary web-search coverage and should be read as an unconfirmed absence, not a verified clean record

[Likely] — https://www.spamhaus.org/resource-hub/dnsbl/the-return-of-the-asn-drop/

Network & routing

Network type
U.S. federal government / military network allocation (DoD Network Information Center block); not a commercial ISP, eyeball, or transit network [Confirmed] — ARIN RDAP
Routing status
NOT announced — 0 IPv4 and 0 IPv6 prefixes; 0 of 326 RIS peers see it in IPv4, 0 of 321 in IPv6; CAIDA AS-degree total 0 (customer 0, peer 0, provider 0); customer cone = 1 ASN (itself), 0 prefixes, 0 addresses
[Confirmed] — RIPEstat routing-status, CAIDA ASRank API, https://bgp.he.net/AS654, https://bgp.tools/as/654
CAIDA AS rank
79,459; clique_member: false; seen: false (no BGP-topology observation, consistent with never announcing) [Confirmed] — CAIDA ASRank API
Peering policy
PeeringDB lists policy "Open" for AS654, but the record shows 0 announced prefixes and no facilities/IX presence — reads as an unpopulated/default PeeringDB entry rather than confirmed active peering [Likely] — https://www.peeringdb.com/asn/654
RPKI
not assessable — AS654 announces no prefixes, so there is no route object to validate against; RIPEstat's rpki-validation endpoint requires a prefix and was not applicable [Unknown, honest null] — RIPEstat rpki-validation
Registrant/operator
United States Department of Defense (DoD) — ARIN org handle USDDD, day-to-day management via DISA-Columbus / DoD Network Information Center (DNIC) [Confirmed] — https://rdap.arin.net/registry/autnum/654
Registry block
DNIC-ASBLK-00616-00665 (startAutnum 616, endAutnum 665) — ARIN registers this DoD range as a single autnum record; no AS654-specific sub-registration exists in RDAP, so the block-level record is the only registration event available [Confirmed] — https://rdap.arin.net/registry/autnum/654
Registrant address
3990 E. Broad Street, Columbus, OH 43218, United States [Confirmed] — ARIN RDAP
Community discussion
no NANOG, Reddit, or general community discussion of AS654 found in searchable archives [Unknown — documented absence, not evidence of anything] — https://archive.nanog.org/list/archives.html
Analyst note
AS654 is a registered-but-dormant ASN inside the DoD's DNIC-ASBLK-00616-00665 block; it currently announces nothing and has no observed peers, consistent with an unused/reserved slot within a large federal allocation rather than an actively operated network.
[ 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.