Skip to content

Autonomous System

AS37119unitel-AS(AO)

Last fetched

AS37119 is an Autonomous System operated by unitel-AS and registered in AO. As of Thu, 21 May 2026 10:21:47 GMT, it announces 36 routed IP prefixes and peers with 18 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS37119Routing diversity7.8/10Peering density5.1/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/37119

Routing footprint

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

Peering ecosystem

18 distinct peers via BGP. The first 24 are listed below.

Peer ASNOperatorCountry
AS1299TWELVE99 Arelion, fka Telia CarrierSE
AS329330Sociedade-Mineira-de-Catoca-LdaAO
AS329209Banco-YETUAO
AS328907AS33793AO
AS328792EEID-ASAO
AS328111IPWORLD-ASAO
AS48362TKSWF-ASAT
AS37721Virtual-Technologies-Solutions-SABF
AS37366BNAAO
AS37147bancobic-asAO
AS36976SONANGOLAO
AS36936BancoBaiAO
AS34549MEER-AS meerfarbig GmbH & Co. KGDE
AS31500GNM-ASAG
AS29075IELO IELO Main NetworkFR
AS24482SGGS-AS-AP SG.GSSG
AS20764RASCOM-AS CJSC RASCOM ISPRU
AS17639CONVERGE-AS Converge ICT Solutions Inc.PH
AS13335CLOUDFLARENET - Cloudflare, Inc.US
AS12779ITGATEIT
AS10798SBICSAZA
AS6939HURRICANE - Hurricane Electric LLCUS
AS3491PCCWG-APAC-HK PCCW Global HK Ltd.HK
AS3216SOVAM-ASRU

Blast radius

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

~76 hostnames depend on this network.Sampled from 10 prefixes, snapshot Thu, 21 May 2026 10:21:47 GMT.

MOAS / hijack watch

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

Threat posture

Related pages

Pivot deeper into the graph from AS37119.

Cypher and MCP

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

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