asn.dev

Observed topology

AS131758 NINGNET-AS-ID - PT. Bali Ning

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS131758: 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
AS141137PT Media Cepat IndonesiaUnclassifiedIPv4128

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS58377Sentra Niaga Solusindo, PT.UnclassifiedIPv4220
AS140476PT Ardi Jaya SolusindoUnclassifiedIPv454
AS45713PT. DEWATA TELEMATIKAHostingIPv48
AS139456PT DEWAWEBUnclassifiedIPv48
AS133337PT Menara Sinar SemestaUnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS141137PT Media Cepat IndonesiaUnclassifiedIPv4420
AS58377Sentra Niaga Solusindo, PT.UnclassifiedIPv4220
AS140476PT Ardi Jaya SolusindoUnclassifiedIPv454
AS45713PT. DEWATA TELEMATIKAHostingIPv48
AS139456PT DEWAWEBUnclassifiedIPv48
AS133337PT Menara Sinar SemestaUnclassifiedIPv42

Provenance

Where this comes from

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