asn.dev

Observed topology

AS142412 NEXWORKS-AS-AP - NEXWORKS COMMUNICATIONS SDN. BHD.

Unclassified APNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS142412: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv636
AS4788TM TECHNOLOGY SERVICES SDN. BHD.MobileIPv4 IPv631
AS45352IP ServerOne Solutions Sdn BhdUnclassifiedIPv4 IPv623
AS24482SG.GSHostingIPv4 IPv62
AS55720Gigabit Hosting Sdn BhdHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS136978JNI SYSTEM SDN BHDUnclassifiedIPv4 IPv6191
AS135580Neutral Transmission Malaysia Sdn. Bhd.UnclassifiedIPv4108
AS140586Velo Technologies SDN BHDUnclassifiedIPv672
AS132890IP Core Sdn BhdUnclassifiedIPv450

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS136978JNI SYSTEM SDN BHDUnclassifiedIPv4 IPv61,027
AS4788TM TECHNOLOGY SERVICES SDN. BHD.MobileIPv4 IPv6735
AS45352IP ServerOne Solutions Sdn BhdUnclassifiedIPv4 IPv6336
AS6939Hurricane Electric LLCTransitIPv4 IPv6164
AS56111Agarto Sdn BhdUnclassifiedIPv4120
AS135580Neutral Transmission Malaysia Sdn. Bhd.UnclassifiedIPv4108
AS140586Velo Technologies SDN BHDUnclassifiedIPv4 IPv674
AS132890IP Core Sdn BhdUnclassifiedIPv471
AS24482SG.GSHostingIPv4 IPv611
AS55720Gigabit Hosting Sdn BhdHostingIPv47

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.