asn.dev

Observed topology

AS38524 LAXONET-AS-ID - Laxo Global Akses, PT

Residential APNIC Cable/DSL/ISP

Upstreams 5 carry this network
Downstreams 6 this network carries
Adjacent (IPv4) 11
Adjacent (IPv6) 1
Upstream graph Who carries AS38524, and who carries them, drawn as a map up to the transit-free core. 8 exchanges Where AS38524 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS38524: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS58389PT Sumber Data IndonesiaUnclassifiedIPv4236
AS136106PT. Mega Akses PersadaResidentialIPv460
AS24534PT. Transhybrid CommunicationUnclassifiedIPv440
AS24482SG.GSHostingIPv4 IPv617
AS35280F5 Networks SARLHostingIPv411

Transit

Downstream networks

inferred

Networks for which AS38524 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS24209PT. Inter Media Lintas NusaResidentialIPv4455
AS45315PT POLARISNETResidentialIPv4260
AS137291Diskominfo Kabupaten TrenggalekUnclassifiedIPv466
AS141081PT Indo Access SemestaResidentialIPv461
AS137361DISKOMINFO Kab. MagelangUnclassifiedIPv450
AS142395PT Global Internet IndonesiaUnclassifiedIPv42

Adjacency

Adjacent networks

All 11

Every AS seen directly next to AS38524 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS58389PT Sumber Data IndonesiaUnclassifiedIPv41,029
AS24209PT. Inter Media Lintas NusaResidentialIPv4455
AS45315PT POLARISNETResidentialIPv4260
AS24534PT. Transhybrid CommunicationUnclassifiedIPv4131
AS137291Diskominfo Kabupaten TrenggalekUnclassifiedIPv466
AS141081PT Indo Access SemestaResidentialIPv461
AS136106PT. Mega Akses PersadaResidentialIPv460
AS137361DISKOMINFO Kab. MagelangUnclassifiedIPv450
AS24482SG.GSHostingIPv4 IPv622
AS35280F5 Networks SARLHostingIPv411

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.