Skip to content

Autonomous System

AS6653VERO-NETWORKS-AS6653 - Vero Broadband(US)

Last fetched

AS6653 is an Autonomous System operated by VERO-NETWORKS-AS6653 - Vero Broadband and registered in US. As of Thu, 21 May 2026 10:33:45 GMT, it announces 42 routed IP prefixes and peers with 14 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS6653Routing diversity8.1/10Peering density4.7/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/6653

Routing footprint

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

Peering ecosystem

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

Peer ASNOperatorCountry
AS174COGENT-174 - Cogent Communications, LLCUS
AS400126CMCMD - Copper Mountain Consolidated Metropolitan DistrictUS
AS394195CLEARNETWORX - ClearnetworxUS
AS62503NPGCO-KRDO - News-Press & Gazette CompanyUS
AS54393FLC-DURANGO - Fort Lewis CollegeUS
AS25899LSNET - LS NetworksUS
AS21803CEDAR-NETWORKS - Cedar NetworksUS
AS19108SUDDENLINK-COMMUNICATIONS - OptimumUS
AS16654VERO-NETWORKS-AS16654 - Vero BroadbandUS
AS7922COMCAST-7922 - Comcast Cable Communications, LLCUS
AS6939HURRICANE - Hurricane Electric LLCUS
AS6461ZAYO-6461 - Zayo BandwidthUS
AS3257GTT-BACKBONE GTTUS
AS2914NTT-DATA-2914 - NTT America, Inc.US

Blast radius

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

~155 hostnames depend on this network.Sampled from 10 prefixes, snapshot Thu, 21 May 2026 10:33:45 GMT.

MOAS / hijack watch

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

Threat posture

Related pages

Pivot deeper into the graph from AS6653.

Cypher and MCP

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

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