Autonomous system detail  ·  US flag US

AS682

Not announced

Last known operator Oak Ridge National Laboratory (ORNL). No prefixes for this AS number were observed in the RouteViews RIB.

Summary

// analyst note
Dormant/legacy-pattern ASN: registered and status-active in ARIN since 1990-06-13, but RIPEstat and CAIDA agree it currently announces zero prefixes and has zero peers/upstreams. A single bgp.tools search snippet corroborates 'inactive BGP network' but was not fetched in full.
// security note
NEUTRAL/DATED: no notable public abuse or threat-feed signal found for AS682 as of 2026-07-18 via web search of Spamhaus, AbuseIPDB, Talos, and NANOG archives (search sweep, not a live feed pull).
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  ·  16 sources  ·  How this page is checked

AS682 (AS-ORNL-IGRP1-AS) is a registered but dormant autonomous system held by Oak Ridge National Laboratory (ORNL), a U.S. Department of Energy national laboratory in Oak Ridge, Tennessee. ARIN's registry status shows it as active, but RIPEstat and CAIDA agree the ASN currently announces zero IPv4 and zero IPv6 prefixes, with none of roughly 325 RIS peers seeing a route to it.

The ASN was registered on 1990-06-13 per ARIN RDAP's top-level autnum event, and last modified 2025-09-24. Registrant contact runs through the ORNL NetMgr group (netmgr@ornl.gov), listed under the organizational handle ORNL-Z. ORNL itself is a DOE-owned facility operated under contract by UT-Battelle, LLC, a joint venture of the University of Tennessee and Battelle Memorial Institute.

CAIDA AS Rank places AS682 at 79,459 globally, with a customer cone limited to itself: zero downstream prefixes, zero addresses, and zero observed peer or provider relationships. No PeeringDB network record exists for AS682, and no publicly documented peering policy was found on ornl.gov or ut-battelle.org, leaving current interconnection arrangements unconfirmed.

ORNL is DOE's largest national laboratory by budget and staff, and it operates the Oak Ridge Leadership Computing Facility (OLCF), a leading DOE supercomputing center. OLCF publicly documented a 2025 upgrade of its network intrusion-detection capacity to 400 Gbps, evidencing a substantial research-network footprint — though that upgrade was not tied to AS682 by name in available sourcing.

Exposure
AS682 announces no prefixes, so there is no directly routed address space to probe under this ASN today; ORNL's live network traffic is believed to run through other infrastructure not confirmed by this research.
Abuse signal
No public abuse or threat-feed listing found for AS682 as of 2026-07-18 via web search of Spamhaus, AbuseIPDB, Talos, and NANOG archives — a search-coverage sweep, not a live database query.
Institutional incidents
ORNL has disclosed being the target of a 2007 spear-phishing campaign and a 2011 APT intrusion attempt; both are attacks against the lab, not outbound abuse from AS682's address space.
Operator
Oak Ridge National Laboratory (ORNL), U.S. Department of Energy national laboratory; registrant org handle ORNL-Z; operated under DOE contract by UT-Battelle, LLC [Confirmed] — https://rdap.arin.net/registry/autnum/682, https://www.ut-battelle.org/about/
Country / RIR
US, ARIN [Confirmed] — RIPEstat abuse-contact-finder (authoritative_rir: arin)
Allocated
1990-06-13 (ARIN RDAP autnum top-level registration event, first-party registry fact); last changed 2025-09-24 [Confirmed] — https://rdap.arin.net/registry/autnum/682
Org status
active per ARIN RDAP autnum status field; registrant is Oak Ridge National Laboratory (DOE FFRDC managed by UT-Battelle, LLC) [Confirmed] — https://rdap.arin.net/registry/autnum/682
Contacts
netmgr@ornl.gov, +1-865-567-3364 (ORNL NetMgr group, ARIN handle NM5-ORG-ARIN); postal One Bethel Valley Road, P.O. Box 2008, Oak Ridge, TN 37830, United States [Confirmed] — https://rdap.arin.net/registry/autnum/682

Security/abuse context (NEUTRAL, DATED)

no notable public abuse or threat-feed signal found as of 2026-07-18 via web search of Spamhaus, AbuseIPDB, Talos, and NANOG archives (a search sweep, not a live feed pull); ORNL has disclosed institution-level incidents (2007 phishing, 2011 APT) unrelated to outbound ASN abuse [Likely] — https://www.spamhaus.org/resource-hub/botnet-c-c/networks-hosting-botnet-ccs/, https://www.computerworld.com/article/1453725/oak-ridge-national-lab-shuts-down-internet-email-after-cyberattack-2.html, https://thehackernews.com/2011/04/oak-ridge-national-laboratory-hacked.html

Network & routing

Network type
institutional/research network of a federal laboratory, not a commercial ISP or IXP; no PeeringDB network record exists (peeringdb.com/asn/682 returns 404) [Confirmed] — https://rdap.arin.net/registry/autnum/682, https://www.peeringdb.com/asn/682
Size
dormant — 0 IPv4 and 0 IPv6 prefixes announced; customer cone = 1 ASN (itself only), 0 prefixes, 0 addresses [Confirmed] — RIPEstat routing-status / CAIDA AS Rank (2026-07-18)
Routing/peering
NOT announced — 0 of 325 RIS peers seeing it on v4, 0 of 321 on v6; CAIDA degree total 0 (customer 0, peer 0, provider 0); no upstreams or peers visible in any source [Confirmed]. Peering policy is not publicly documented [Unknown] — https://stat.ripe.net/AS682, https://asrank.caida.org/asns/682
RPKI
not assessable — AS682 announces no prefixes, so there are no ROAs to validate; RIPEstat's rpki-validation check was skipped for lack of an announced prefix [Confirmed] — https://stat.ripe.net/AS682
Notable usage
ORNL is DOE's largest national laboratory by budget and staff and operates the Oak Ridge Leadership Computing Facility (OLCF), a leading DOE supercomputing center; OLCF documented a 2025 upgrade of its network intrusion-detection capacity to 400 Gbps [Confirmed for ORNL/OLCF; not tied to AS682 by name] — https://www.olcf.ornl.gov/2025/08/20/olcf-upgrades-its-network-security-infrastructure/, https://en.wikipedia.org/wiki/Oak_Ridge_National_Laboratory
Analyst note
registered and status-active in ARIN's database since 1990 but not currently announcing any routes; a single bgp.tools search snippet (not fetched) describes it as an "inactive BGP network," corroborating the RIPEstat/CAIDA dormancy finding [Likely, single-source] — https://bgp.tools/as/682
[ 02 ] — Announced prefixes

What this network routes.

0 prefixes total · as observed by RouteViews at 2026-09-20 · one collector view, not a global census
// 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.