Skip to content

Autonomous System

AS38524 — LAXONET-AS-ID Laxo Global Akses, PT(ID)

Last fetched

AS38524 is an Autonomous System operated by LAXONET-AS-ID Laxo Global Akses, PT and registered in ID. As of Thu, 21 May 2026 15:06:56 GMT, it announces 17 routed IP prefixes and peers with 12 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS38524Routing diversity6.3/10Peering density4.4/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/38524

Routing footprint

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

Peering ecosystem

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

Peer ASNOperatorCountry
AS24209INTERMEDIANET-AS-ID PT. Inter Media Lintas NusaID
AS153673IDNIC-PINNUTA-ID PT Pioneer Nusatama TechnologyID
AS152056IDNIC-SGU-AS-ID PT Sangkakala Gema UtamaID
AS141081ONET-AS-ID PT Indo Access SemestaID
AS137361IDNIC-KOMINFOKABMGL-AS-ID DISKOMINFO Kab. MagelangID
AS137291IDNIC-TRENGGALEKKAB-ID Diskominfo Kabupaten TrenggalekID
AS136106FIBERSTAR-AS-ID PT. Mega Akses PersadaID
AS133354IDNIC-AKPA-AS-ID PT Anugerah Karunia Perkasa AbadiID
AS58389SDI-NAP-AS-ID PT Sumber Data IndonesiaID
AS45315POLARIS-AS-ID PT POLARISNETID
AS35280F5FR
AS24534TRANSHYBRID-AS-ID PT. Transhybrid CommunicationID

Blast radius

Approximate count of dependent hostnames if AS38524 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 AS38524 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 AS38524 is unique to AS38524 in the current routing snapshot.

Threat posture

Related pages

Pivot deeper into the graph from AS38524.

Cypher and MCP

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

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