AS655

AS655 is a legacy autonomous system number held within ARIN's DNIC-ASBLK-00616-00665 block, a Defense Network Information Center range spanning AS616 through AS665 and registered to the United States Department of Defense (DoD). The covering block record carries a top-level ARIN RDAP registration event dated 1990-04-19, with the record's administrative data last changed 2025-09-12. AS655 is currently dormant: RIPEstat, CAIDA AS Rank, and bgp.he.net all agree it announces zero IPv4 and zero IPv6 prefixes, has no visible BGP peers or upstreams (CAIDA degree total 0), and sits outside CAIDA's observed topology entirely, with a customer cone that is a singleton containing only itself. RIPEstat's routing-status history shows AS655 was last seen originating a /24 (138.178.200.0/24) on 2016-06-23, after first being observed announcing 206.39.210.0/24 in January 2001 — it has not routed anything in roughly a decade. One angle flagged a historical anomaly worth downstream review: AS655's last announced prefixes were APNIC-region space (103.245.122.0/24, 202.52.50.0/24) peered through an Indonesian network, which is atypical for a DoD/ARIN-space ASN and may reflect a stale or leaked announcement rather than legitimate DoD routing. No public abuse signal (Spamhaus ASN-DROP, NANOG archives) was found, consistent with a long-inactive ASN.

Operator

United States Department of Defense (DoD) — DNIC-ASBLK-00616-00665, registrant handle USDDD [Confirmed] — https://rdap.arin.net/registry/autnum/655

Country / RIR

US, ARIN [Confirmed] — https://rdap.arin.net/registry/autnum/655

Allocated

1990-04-19 (ARIN RDAP top-level registration event on the covering DNIC block record AS616–AS665; no separate per-ASN record exists within this block); last changed 2025-09-12 [Confirmed] — https://rdap.arin.net/registry/autnum/655

Website / peering policy

no AS655-specific operator website or published peering policy found; AS655 does not appear among the DoD org's ~20 listed ASNs on PeeringDB [Unknown] — https://www.peeringdb.com/org/17705

Org status

RIR block status Active (covering DNIC-ASBLK-00616-00665); AS655 itself unrouted/dark [Confirmed] — https://rdap.arin.net/registry/autnum/655

Security/abuse context (NEUTRAL, DATED)

no listing on Spamhaus ASN-DROP and no NANOG-archive or general abuse-feed reporting found as of 2026-07-17; read as "no evidence observed" for a long-dormant, unrouted ASN rather than an active clean-traffic attestation

Abuse contact

disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil (authoritative RIR: ARIN)

Network & routing

Network type

government/military legacy DNIC block allocation, not a commercial network operator [Confirmed] — https://rdap.arin.net/registry/autnum/655

Routing status

dormant — 0 IPv4/IPv6 prefixes currently announced; 0/325 v4 and 0/320 v6 RIS peers seeing it [Confirmed] — https://stat.ripe.net/AS655

Historical routing

first seen 206.39.210.0/24 (2001-01-18); last seen 138.178.200.0/24 (2016-06-23) — not visible in the global routing table since roughly mid-2016 [Confirmed] — https://stat.ripe.net/AS655, https://bgp.he.net/AS655

CAIDA

AS rank 79459; customer cone singleton (1 ASN, 0 prefixes, 0 addresses); degree total/customer/peer/provider all 0; not seen in current topology [Confirmed] — https://api.asrank.caida.org/v2/restful/asns/655

RPKI

not assessable — no prefix is currently announced, so RIPEstat's rpki-validation query (which requires a prefix) could not run [Unknown] — https://stat.ripe.net/AS655

Related ASNs

part of block AS616–AS665 (DNIC-ASBLK-00616-00665), same registrant [Confirmed] — https://rdap.arin.net/registry/autnum/655

Anomaly note

historically originated 2 APNIC-region prefixes peered via an Indonesian network (AS46056) — atypical for DoD/ARIN space, possibly a leak or stale misannouncement rather than legitimate DoD activity [Likely] — https://bgp.he.net/AS655

Registrant address

3990 E. Broad Street, Columbus, OH 43218, United States (USDDD org record) [Confirmed] — https://rdap.arin.net/registry/autnum/655

Analyst note

legacy DoD DNIC-block ASN with no independent operator identity or peering footprint; last routed roughly a decade ago; the one anomalous APNIC-region historical announcement is flagged for downstream review, not asserted as fact.