asn.dev

Observed topology

AS141056 IOSYS-AS-ID - PT IOSYS Media Data

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS141056: 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
AS55685PT Jala Lintas MediaUnclassifiedIPv4 IPv6354
AS24482SG.GSHostingIPv4 IPv68
AS23947PT.Mora Telematika IndonesiaUnclassifiedIPv46

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS149694PT Oke Digital MediaUnclassifiedIPv4190
AS152423PT Sindoro Sumbing Network SolutionUnclassifiedIPv4190
AS140028PT Brahmayasa Sejahtera AbadiUnclassifiedIPv4104
AS140389PT Dewa Bisnis DigitalHostingIPv4 IPv637

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS55685PT Jala Lintas MediaUnclassifiedIPv4 IPv6736
AS149694PT Oke Digital MediaUnclassifiedIPv4190
AS152423PT Sindoro Sumbing Network SolutionUnclassifiedIPv4190
AS23947PT.Mora Telematika IndonesiaUnclassifiedIPv4 IPv6133
AS140028PT Brahmayasa Sejahtera AbadiUnclassifiedIPv4104
AS140389PT Dewa Bisnis DigitalHostingIPv4 IPv641
AS24482SG.GSHostingIPv4 IPv618
AS141137PT Media Cepat IndonesiaUnclassifiedIPv46

Provenance

Where this comes from

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