asn.dev

Observed topology

AS38500 CROSSNET-AS-ID - PT. Cross Network Indonesia

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS38500: 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
AS138840PT. PARSAORAN GLOBAL DATATRANS - NAPUnclassifiedIPv4300
AS7713PT Telekomunikasi IndonesiaResidentialIPv4286
AS23679PT. Media Antar NusaUnclassifiedIPv4246
AS24482SG.GSHostingIPv411
AS139449PT Lintas Data MultimediaResidentialIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS139459Dinas Komunikasi dan Informatika Pemerintah Kota ProbolinggoUnclassifiedIPv474

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS138840PT. PARSAORAN GLOBAL DATATRANS - NAPUnclassifiedIPv4370
AS7713PT Telekomunikasi IndonesiaResidentialIPv4286
AS23679PT. Media Antar NusaUnclassifiedIPv4246
AS139459Dinas Komunikasi dan Informatika Pemerintah Kota ProbolinggoUnclassifiedIPv474
AS24482SG.GSHostingIPv413
AS139449PT Lintas Data MultimediaResidentialIPv42

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.