Skip to content

Autonomous System

AS269180 — AS269180 - VIPNET Conexao(BR)

Last fetched

AS269180 is an Autonomous System operated by AS269180 - VIPNET Conexao and registered in BR. As of Sun, 06 Sep 2026 13:54:52 GMT, it announces 7 routed IP prefixes and peers with 13 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS269180Routing diversity4.5/10Peering density4.6/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/269180

Routing footprint

AS269180 announces 7 distinct routed prefixes. The 7-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
AS10429AS10429 - TELEFONICA BRASIL S.ABR
AS24482SGGS-AS-AP - SG.GSSG
AS263283AS263283 - JGNET - J G DE OLIVEIRA MATOS & CIA LTDABR
AS264416AS264416 - WIANET SOLUCOES E TECNOLOGIA LTDABR
AS268190AS268190 - LINK NET TELECOMUNICACOES LTDA - MEBR
AS272766AS272766 - ATOS COMERCIO E EMPREENDIMENTOS DE INFORMATICABR
AS273782AS273782 - S & M Nacional Telecom LtdaBR
AS2914NTT-DATA-2914 - NTT America, Inc.US
AS35280F5 - F5 Networks SARLFR
AS37721Virtual Technologies & Solutions - Virtual Technologies & SolutionsBF
AS4230AS4230 - CLARO S.A.BR
AS61664AS61664 - RONDOTECH SERVICO DE COMUNICACAO EIRELI-EPPBR
AS61745AS61745 - NBS TELECOMBR

Blast radius

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

12 hostnames depend on this network.Exact count across all 7 announced prefixes. Snapshot Tue, 21 Jul 2026 09:00:26 GMT.

MOAS / hijack watch

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

Threat posture

Related pages

Pivot deeper into the graph from AS269180.

Cypher and MCP

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

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