Observed topology

AS141639 IDNIC-L1V-AS-ID PT Lintas Satu Visi

Unclassified APNIC Cable/DSL/ISP

Upstreams 5 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS141639: 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
AS38158	PT. Cyberindo Aditama	Unclassified	IPv4 IPv6	102
AS138840	PT. PARSAORAN GLOBAL DATATRANS - NAP	Unclassified	IPv4	10
AS147094	PT. MITRA VISIONER PRATAMA	Unclassified	IPv4	10
AS24198	PT. Datakom Padma Jaya (DatakomNAP)	Unclassified	IPv4	7
AS141071	PT Jembatan Data Pangrango	Residential	IPv4	4

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS137379	Diskominfo Kota Bekasi	Unclassified	IPv4	66

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS38158	PT. Cyberindo Aditama	Unclassified	IPv4 IPv6	103
AS137379	Diskominfo Kota Bekasi	Unclassified	IPv4	66
AS147094	PT. MITRA VISIONER PRATAMA	Unclassified	IPv4	57
AS138840	PT. PARSAORAN GLOBAL DATATRANS - NAP	Unclassified	IPv4	25
AS24198	PT. Datakom Padma Jaya (DatakomNAP)	Unclassified	IPv4	13
AS141071	PT Jembatan Data Pangrango	Residential	IPv4	7

Provenance

Where this comes from

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