Skip to content

Autonomous System

AS226 — LOS-NETTOS-AS - Los Nettos(US)

Last fetched

AS226 is an Autonomous System operated by LOS-NETTOS-AS - Los Nettos and registered in US. As of Tue, 21 Jul 2026 12:50:15 GMT, it announces 15 routed IP prefixes and peers with 17 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS226Routing diversity6.0/10Peering density5.0/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/226

Routing footprint

AS226 announces 15 distinct routed prefixes. The 15-prefix sample below links to per-prefix pages with full conflict and reverse-DNS detail.

Peering ecosystem

17 distinct peers via BGP. The first 17 are listed below.

Peer ASNOperatorCountry
AS12148CLEMSONU - Clemson UniversityUS
AS127JPL-AS127 - Jet Propulsion LaboratoryUS
AS14486OXY-AS - Occidental CollegeUS
AS25789LMU - Loyola Marymount UniversityUS
AS27609USC-UNIVERSITY-HOSPITAL - USC-University HospitalUS
AS2914NTT-DATA-2914 - NTT America, Inc.US
AS3659CLAREMONT - Claremont University ConsortiumUS
AS38022NZ
AS394353BROOT-AS - B.Root-Server-OPSUS
AS4ISI-AS - University of Southern CaliforniaUS
AS47USC-AS - University of Southern CaliforniaUS
AS47065US
AS5108PASADENA-ASN - City of PasadenaUS
AS567ASN-LNET-AS - Los NettosUS
AS62988ARTCENTERCAMPUSES - Art Center College of DesignUS
AS7575AU
AS85AERO-NET - The Aerospace CorporationUS

Blast radius

Count of dependent hostnames if AS226 disappeared from the routing table.

19,786 hostnames depend on this network.Exact count across all 15 announced prefixes. Snapshot Sat, 11 Jul 2026 01:01:05 GMT.

MOAS / hijack watch

Prefixes routed by AS226 that another Autonomous System also announces. A non-empty list is one of the strongest BGP-hijack signals available without active probes.

No active MOAS conflicts. Every prefix announced by AS226 is unique to AS226 in the current routing snapshot.

Threat posture

Related pages

Pivot deeper into the graph from AS226.

Cypher and MCP

Reproduce the headline metric directly against graph.whisper.security:

MATCH (a:ASN {name: "AS226"})-[:HAS_NAME]->(n:ASN_NAME)
OPTIONAL MATCH (a)-[:HAS_COUNTRY]->(c:COUNTRY)
RETURN a.name AS asn, n.name AS operator, c.name AS country

Or query Whisper from your own LLM workflow via the Whisper MCP server.