AS626

AS626 is one of fifty ASNs (AS616 through AS665) inside a single ARIN-registered legacy block, DNIC-ASBLK-00616-00665, held by the United States Department of Defense. ARIN issues one RDAP autnum record per contiguous block rather than per individual number, so the block's top-level registration event — 1990-04-19 — is the correct allocated_date for AS626, and the block's last-changed timestamp is 2025-09-12. The registrant organization is "United States Department of Defense (DoD)" (ARIN org handle USDDD), with day-to-day registration and technical contacts routed through the Defense Information Systems Agency's Columbus, Ohio hostmaster and registrations mailboxes. There is no separate corporate identity, website, or peering-policy page for AS626 itself; DISA's general site (disa.mil) contains nothing specific to this ASN or block. Every routing data source consulted — RIPEstat as-overview and routing-status, CAIDA AS Rank, and a live bgp.he.net looking-glass fetch — agrees AS626 currently announces zero IPv4 and zero IPv6 prefixes and has zero observed BGP peers, upstreams, or customers, placing it firmly among the large population of DoD-held ASNs that are registered but not operationally routed on the public Internet (its likely operational traffic, if any, rides internal DoD networks such as NIPRNet rather than the open BGP table). No PeeringDB entry exists for AS626 (404), and no NANOG discussion, public outage, hijack, or abuse-feed signal specific to AS626 was found in this cycle's searches, consistent with a quiet, government-held, unannounced ASN rather than a confirmed clean bill of health from a dedicated tracking service.

Operator

United States Department of Defense (DoD), registrant org USDDD; block administered via DISA's DNIC hostmaster in Columbus, OH [Confirmed] — https://rdap.arin.net/registry/autnum/626

Country / RIR

US, ARIN [Confirmed] — https://rdap.arin.net/registry/autnum/626 (RIPEstat abuse-contact-finder authoritative_rir: arin)

Allocated

1990-04-19 (ARIN RDAP autnum top-level registration event for the DNIC-ASBLK-00616-00665 block; this is a first-party RIR registry date, not an IEEE/OUI-style artifact); last changed 2025-09-12 [Confirmed] — https://rdap.arin.net/registry/autnum/626

Org status

Active per ARIN RDAP record status; block record last maintained 2025-09-12 [Confirmed] — https://rdap.arin.net/registry/autnum/626

Contacts

NOC/technical/abuse — disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil; administrative/registrations — disa.columbus.ns.mbx.arin-registrations@mail.mil; registrant address 3990 E. Broad Street, Columbus, OH 43218 [Confirmed] — https://rdap.arin.net/registry/autnum/626

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-17 across Spamhaus ASN-DROP framing, community ASN blocklists, CleanTalk spam-activity stats, or NANOG-style hijack/compromise search terms; absence of hits is consistent with a quiet, low-visibility government ASN rather than a confirmed clean record from a dedicated abuse-tracking service [Likely] — https://www.spamhaus.org/resource-hub/dnsbl/the-return-of-the-asn-drop/, https://github.com/bountyyfi/bad-asn-list, https://cleantalk.org/blacklists/asn

Network & routing

Network type

government/military legacy ASN block; not a commercial operator with its own site or peering-policy page [Confirmed] — https://rdap.arin.net/registry/autnum/626, https://www.disa.mil/

Size

dormant on the public Internet — 0 IPv4 prefixes / 0 addresses, 0 IPv6 prefixes; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — RIPEstat routing-status, CAIDA ASRank, https://bgp.he.net/AS626 (2026-07-17)

Routing/peering

NOT announced — 0/326 RIS peers seeing v4, 0/322 seeing v6; CAIDA degree total 0 (customer 0, peer 0, provider 0); no PeeringDB entry (404) [Confirmed] — RIPEstat routing-status, https://www.peeringdb.com/asn/626, https://bgp.he.net/AS626

RPKI

not assessable — AS626 originates no prefixes, so there are no ROAs to validate against [Unknown/not applicable, honestly null] — RIPEstat rpki-validation endpoint (skipped: no prefix supplied)

Notable usage

none found; no public news, technical writeups, or notable-usage references specific to AS626; any real usage would be internal DoD networking (e.g. NIPRNet) not independently verifiable via open sources [Likely] — https://bgp.he.net/AS626

Related ASNs

part of the contiguous DNIC-ASBLK-00616-00665 block (AS616–AS665, 50 ASNs total), all registered to the same DoD registrant [Confirmed] — https://rdap.arin.net/registry/autnum/626

Community/reputation signals

no NANOG mailing-list discussion, no documented outages, hijacks, or route leaks found for AS626 [Confirmed, absence-based] — https://bgpstream.com, https://bgp.he.net

Analyst note

Classic dormant DoD-block ASN — RIR registration is long-standing (1990) and actively maintained, but the number is not visibly routed today; do not confuse block-level registrant/contact records with an individual operational entity for AS626 specifically.