Skip to content

Autonomous System

AS2153CENIC-2153 - CENIC(US)

Last fetched

AS2153 is an Autonomous System operated by CENIC-2153 - CENIC and registered in US. As of Wed, 20 May 2026 21:52:27 GMT, it announces 12 routed IP prefixes and peers with 13 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS2153Routing diversity5.6/10Peering density4.6/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/2153

Routing footprint

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

Peering ecosystem

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

Peer ASNOperatorCountry
AS24AS24 - National Aeronautics and Space AdministrationUS
AS46985IGC-TYN - Intelsat General CorporationUS
AS26397JOHNSON-CONTROLS - Johnson Controls IncUS
AS22323PLUMCHOICE-DC1 - PlumChoiceUS
AS11537INTERNET2-RESEARCH-EDU - Internet2US
AS7575AARNET-AS-AP Australian Academic and Research Network AARNetAU
AS6192UCDAVIS-CORE - University of California, DavisUS
AS6106UCR-EDU - University of California, RiversideUS
AS5653UCSF - University of California San FranciscoUS
AS2907SINET-AS Research Organization of Information and Systems, National Institute of InformaticsJP
AS2152CENIC-2152 - CENICUS
AS567ASN-LNET-AS - Los NettosUS
AS195SDSC-AS - San Diego Supercomputer CenterUS

Blast radius

Approximate count of dependent hostnames if AS2153 disappeared from the routing table.

~76 hostnames depend on this network.Sampled from 10 prefixes, snapshot Wed, 20 May 2026 21:52:27 GMT.

MOAS / hijack watch

Prefixes routed by AS2153 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 AS2153 is unique to AS2153 in the current routing snapshot.

Threat posture

Related pages

Pivot deeper into the graph from AS2153.

Cypher and MCP

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

MATCH (a:ASN {name: "AS2153"})-[: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.