asn.dev

Observed topology

AS136978 JNI-AS-AP - JNI SYSTEM SDN BHD

Unclassified APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS136978: 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
AS142412NEXWORKS COMMUNICATIONS SDN. BHD.UnclassifiedIPv4 IPv6200
AS6939Hurricane Electric LLCTransitIPv418
AS38001NewMedia Express Pte LtdHostingIPv4 IPv63

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS132196DANAWA RESOURCES SDN BHDResidentialIPv4165
AS56111Agarto Sdn BhdUnclassifiedIPv4 IPv685
AS142631Metro LightspeedResidentialIPv4 IPv64

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS142412NEXWORKS COMMUNICATIONS SDN. BHD.UnclassifiedIPv4 IPv61,074
AS56111Agarto Sdn BhdUnclassifiedIPv4 IPv6666
AS132196DANAWA RESOURCES SDN BHDResidentialIPv4165
AS38001NewMedia Express Pte LtdHostingIPv4 IPv624
AS140866TRUE PACKET SDN BHDUnclassifiedIPv423
AS6939Hurricane Electric LLCTransitIPv421
AS142631Metro LightspeedResidentialIPv4 IPv64

Provenance

Where this comes from

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