Skip to content

Autonomous System

AS6161467 TELECOM(BR)

Last fetched

AS61614 is an Autonomous System operated by 67 TELECOM and registered in BR. As of Thu, 21 May 2026 06:24:33 GMT, it announces 21 routed IP prefixes and peers with 19 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS61614Routing diversity6.7/10Peering density5.2/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/61614

Routing footprint

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

Peering ecosystem

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

Peer ASNOperatorCountry
AS3356LEVEL3 - Level 3 Parent, LLCUS
AS273629CONECT ISP LTDABR
AS273453R G DE SOUZA INFORMATICABR
AS270912MARCIO HAUBRICHT FILHO MEBR
AS270735COMPUTIZE NETWORK TELECOMUNICACOES LTDABR
AS269664MAIS TELECOMUNICACOES LTDABR
AS269529M2 TELECOMUNICACAOBR
AS26947867 TELECOMUNICACOESBR
AS268817Acelera TelecomBR
AS268811GFA Telecomunicacoes LTDABR
AS268492JL ProvedorBR
AS268308VIVA CONNECTION TELECOMUNICACOES LTDA MEBR
AS267363LINK TELECOMUNICACOES LTDABR
AS263539NEW SYSTEM INTERNETBR
AS262990VIRTUAL CENTER HOSTING TECNOLOGIA EIRELIBR
AS64165EXTRA S.A.PY
AS37468ANGOLA-CABLESAO
AS28146MHNET TELECOMBR
AS7195EDGEUNO S.A.SCO

Blast radius

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

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

MOAS / hijack watch

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

Threat posture

Related pages

Pivot deeper into the graph from AS61614.

Cypher and MCP

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

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