Skip to content

Autonomous System

AS61624 — AS61624 - INFNOC TECNOLOGIA LTDA(BR)

Last fetched

AS61624 is an Autonomous System operated by AS61624 - INFNOC TECNOLOGIA LTDA and registered in BR. As of Sun, 06 Sep 2026 16:12:46 GMT, it announces 5 routed IP prefixes and peers with 13 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS61624Routing diversity3.9/10Peering density4.6/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/61624

Routing footprint

AS61624 announces 5 distinct routed prefixes. The 5-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
AS24482SGGS-AS-AP - SG.GSSG
AS264092AS264092 - STA TELECOM LTDABR
AS266400AS266400 - Ferenz NetworksBR
AS269783AS269783 - WIND NET S.A.PY
AS270052AS270052 - STARTELECOM S.A.PY
AS272026AS272026 - HERNAN GALEANO KIM (HERKIM - SOLUCIONES TECNOLOGICAS)PY
AS272065AS272065 - PUNTO DOC SOCIEDAD ANONIMAPY
AS273847AS273847 - P.A. NETWORKS E.A.SPY
AS274041AS274041 - INTERCABLE COMERCIAL Y SERVICIOS S.R.L.PY
AS3356LEVEL3 - Level 3 Parent, LLCUS
AS37721Virtual Technologies & Solutions - Virtual Technologies & SolutionsBF
AS52925AS52925 - Ascenty Data Centers e Telecomunicacoes S/ABR
AS6939HURRICANE - Hurricane Electric LLCUS

Blast radius

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

Blast radius: Computing — check back later. The precompute pipeline refreshes this panel within a few days.

MOAS / hijack watch

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

Threat posture

Related pages

Pivot deeper into the graph from AS61624.

Cypher and MCP

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

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