Autonomous system detail

AS618

Not announced

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

Summary

// analyst note
Dormant/legacy DoD DNIC-block ASN. Allocation date well-corroborated at the autnum top level (1990-04-19) across multiple angles. One unresolved, single-source routing anomaly (bgp.he.net) conflicts with RIPEstat's clean zero-announcement view; flagged, not resolved, pending future re-check.
// security note
No notable public abuse signal found as of 2026-07-17.
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: Medium

AS618 is a legacy autonomous system number sitting inside a reserved U.S. Department of Defense block, DNIC-ASBLK-00616-00665 (AS616AS665), registered under ARIN to the United States Department of Defense (org handle USDDD) and administered day-to-day by the Defense Information Systems Agency's Columbus, Ohio field office. ARIN's RDAP record for the block carries a top-level registration date of 1990-04-19, corroborated independently by two research angles reading the same autnum-level events array (distinct from several later, unrelated entity/POC record dates nested underneath it), so it is recorded here with high confidence rather than nulled. Routing-wise, AS618 is effectively dormant: RIPEstat shows zero currently announced IPv4/IPv6 prefixes, zero visible RIS peers, and a brief historical announcement of a single /24 (103.107.90.0/24) that lasted from August 2024 to February 2025 before disappearing from view. CAIDA ranks it 79,006th globally with a singleton customer cone. One unresolved anomaly surfaced on a single third-party looking-glass (bgp.he.net), showing live, bogon-flagged prefix announcements peered to an unrelated Chinese commercial ASN — flagged here as an unconfirmed discrepancy, not an established incident, since it directly conflicts with RIPEstat's contemporaneous zero-announcement snapshot and no independent source corroborates it.

Operator / registrant
United States Department of Defense (DoD), org handle USDDD; operationally managed by DISA-Columbus [Confirmed] — https://rdap.arin.net/registry/autnum/618
Country / RIR
US, ARIN [Confirmed] — https://rdap.arin.net/registry/autnum/618
Allocated
1990-04-19 (ARIN RDAP autnum TOP-LEVEL registration event, corroborated across two independent research angles reading the same field; distinct from later entity/POC-level dates 1993, 2007, 2009, 2025, 2026 which are contact-record artifacts, not the ASN's own registration)
[Confirmed] — https://rdap.arin.net/registry/autnum/618
Org status
parent block record status "active" per ARIN RDAP [Confirmed] — https://rdap.arin.net/registry/autnum/618
Website
none found — no dedicated public site for AS618 itself; only mail.mil contact addresses appear in RDAP [Unknown] — https://rdap.arin.net/registry/autnum/618
Contacts
abuse/NOC/technical — disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil (MIL-HSTMST-ARIN); registration — disa.columbus.ns.mbx.arin-registrations@mail.mil (REGIS10-ARIN); DISA-Columbus, 300 North James Road, Whitehall, OH 43213 [Confirmed] — https://rdap.arin.net/registry/autnum/618

Security/abuse context

no notable public abuse signal found as of 2026-07-17 in general abuse/threat feeds or NANOG archives; the bgp.he.net anomaly above is the only notable signal and is unconfirmed

[Likely] — https://seclists.org/nanog/, https://bgp.he.net/AS618

Network & routing

Network type
government/military DoD network block; currently a dormant/stub AS with no active hosted infrastructure [Likely] — https://rdap.arin.net/registry/autnum/618, https://ipinfo.io/AS618
Size / routing
0 IPv4 and 0 IPv6 prefixes currently announced per RIPEstat consensus view; historical announcement of 103.107.90.0/24 from 2024-08-16 to 2025-02-05, since dropped from RIS visibility (0/327 v4 peers, 0/322 v6 peers)
[Confirmed] — RIPEstat routing-status/announced-prefixes for AS618, queried 2026-07-17
CAIDA AS Rank
#79,006; customer cone = singleton (1 ASN, 0 prefixes, 0 addresses); 1 provider relationship, 0 peer, 0 customer edges; no geo coordinates (longitude/latitude = 0) [Confirmed] — CAIDA ASRank API, asn=618, fetched 2026-07-17
Peering
no observed BGP neighbours per RIPEstat; no public peering-policy page found tied to this specific ASN (DISA's general DISN connection-process docs are not ASN-specific) [Unknown] — https://dl.dod.cyber.mil/wp-content/uploads/connect/CPG/ConnProcGuide.html
RPKI posture
not assessable at the ASN level — RIPEstat's rpki-validation endpoint requires a specific prefix, none was supplied [Unknown] — RIPEstat rpki-validation response (skipped)
ASN / block
AS618, part of DNIC-ASBLK-00616-00665 (block AS616–AS665) [Confirmed] — https://rdap.arin.net/registry/autnum/618
Last changed (registry record)
2025-09-12 (autnum top-level "last changed" event) [Confirmed] — https://rdap.arin.net/registry/autnum/618
Unresolved anomaly
bgp.he.net (single fetch, 2026-07-17) shows AS618 currently originating 9 IPv4 prefixes (~6,912 IPs) via a lone BGP peer, AS131486 (Beijing Jingdong 360 Degree E-commerce Co.), flagged "announces bogons" / "IRR Invalid — Origin Mismatch" on that page; this directly conflicts with RIPEstat's zero-announcement snapshot and has no independent corroboration (no NANOG thread, no vendor advisory) — reported as an unconfirmed anomaly, not a confirmed hijack
[Unknown] — https://bgp.he.net/AS618
[ 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.