asn.dev

Observed topology

AS140866 TRUEPACKETSDNBHD-AS-AP TRUE PACKET SDN BHD

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS140866: 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 LLCTransitIPv4258
AS56111Agarto Sdn BhdUnclassifiedIPv476

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS56111Agarto Sdn BhdUnclassifiedIPv4310
AS131310CX2 Computer ExchangeUnclassifiedIPv4188
AS139761Gigabit Fiber Sdn BhdUnclassifiedIPv459
AS134202E-WORLD COMMUNICATION SDN BHDUnclassifiedIPv47

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv41,866
AS56111Agarto Sdn BhdUnclassifiedIPv41,553
AS131310CX2 Computer ExchangeUnclassifiedIPv4188
AS139761Gigabit Fiber Sdn BhdUnclassifiedIPv459
AS136978JNI SYSTEM SDN BHDUnclassifiedIPv423
AS134202E-WORLD COMMUNICATION SDN BHDUnclassifiedIPv47

Provenance

Where this comes from

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