Observed topology

AS38165 ADSNET-AS-ID PT. AMBHARA DUTA SHANTI

Residential ARIN Cable/DSL/ISP

Upstreams 7 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 0

Upstream graph Who carries AS38165, and who carries them, drawn as a map up to the transit-free core. 5 exchanges Where AS38165 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS38165: 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.

AS	Network	Type	Families	Paths seen
AS4800	PT Aplikanusa Lintasarta	Hosting	IPv4	579
AS7713	PT Telekomunikasi Indonesia	Residential	IPv4	216
AS17451	BIZNET NETWORKS	Residential	IPv4	134
AS23947	PT.Mora Telematika Indonesia	Unclassified	IPv4	110
AS24534	PT. Transhybrid Communication	Unclassified	IPv4	95
AS136106	PT. Mega Akses Persada	Residential	IPv4	31
AS24482	SG.GS	Hosting	IPv4	12

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS140426	Pemerintah Kabupaten Klungkung	Unclassified	IPv4	65

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS4800	PT Aplikanusa Lintasarta	Hosting	IPv4	585
AS7713	PT Telekomunikasi Indonesia	Residential	IPv4	230
AS17451	BIZNET NETWORKS	Residential	IPv4	176
AS23947	PT.Mora Telematika Indonesia	Unclassified	IPv4	110
AS24534	PT. Transhybrid Communication	Unclassified	IPv4	96
AS140426	Pemerintah Kabupaten Klungkung	Unclassified	IPv4	65
AS136106	PT. Mega Akses Persada	Residential	IPv4	31
AS24482	SG.GS	Hosting	IPv4	13

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-30 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.49M 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.