asn.dev

Observed topology

AS141071 JEMBATANDATA-AS-ID PT Jembatan Data Pangrango

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS141071: 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
AS24534PT. Transhybrid CommunicationUnclassifiedIPv4280
AS147094PT. MITRA VISIONER PRATAMAUnclassifiedIPv4216
AS64315PT MITRA VISIONER PRATAMAUnclassifiedIPv4 IPv650
AS24482SG.GSHostingIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS141639PT Lintas Satu VisiUnclassifiedIPv44
AS149749Morizt IDUnclassifiedIPv42
AS152064PT Mitratama Mahadirga MakmurUnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS24534PT. Transhybrid CommunicationUnclassifiedIPv4280
AS147094PT. MITRA VISIONER PRATAMAUnclassifiedIPv4216
AS64315PT MITRA VISIONER PRATAMAUnclassifiedIPv4 IPv650
AS24482SG.GSHostingIPv47
AS35280F5 Networks SARLHostingIPv44
AS141639PT Lintas Satu VisiUnclassifiedIPv44
AS149749Morizt IDUnclassifiedIPv44
AS152064PT Mitratama Mahadirga MakmurUnclassifiedIPv42

Provenance

Where this comes from

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