asn.dev

Observed topology

AS140586 VTSB-AS-AP - Velo Technologies SDN BHD

Unclassified APNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS140586: 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
AS136749KS IT SOLUTIONS SDN BHDUnclassifiedIPv4200
AS45352IP ServerOne Solutions Sdn BhdUnclassifiedIPv4110
AS142412NEXWORKS COMMUNICATIONS SDN. BHD.UnclassifiedIPv672
AS17666Unit 13-4, Block F1,UnclassifiedIPv464
AS24482SG.GSHostingIPv45
AS55720Gigabit Hosting Sdn BhdHostingIPv45

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS132022IP World Technologies Sdn. Bhd.HostingIPv4188
AS140710NKH SOLUTION SDN BHDUnclassifiedIPv457
AS133135TeamCloud - MalaysiaUnclassifiedIPv47

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS45352IP ServerOne Solutions Sdn BhdUnclassifiedIPv4360
AS136749KS IT SOLUTIONS SDN BHDUnclassifiedIPv4200
AS132022IP World Technologies Sdn. Bhd.HostingIPv4188
AS142412NEXWORKS COMMUNICATIONS SDN. BHD.UnclassifiedIPv4 IPv674
AS17666Unit 13-4, Block F1,UnclassifiedIPv464
AS140710NKH SOLUTION SDN BHDUnclassifiedIPv457
AS133135TeamCloud - MalaysiaUnclassifiedIPv47
AS24482SG.GSHostingIPv45
AS55720Gigabit Hosting Sdn BhdHostingIPv45

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.