asn.dev

Observed topology

AS132040 VITAL-CT-AP Vital Data Ltd

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS132040: 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
AS135069Feenix Communications LimitedUnclassifiedIPv4 IPv6950
AS6939Hurricane Electric LLCTransitIPv690
AS64073Vetta GroupUnclassifiedIPv4 IPv615
AS35280F5 Networks SARLHostingIPv65

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS15248Metaswitch Networks Corp.UnclassifiedIPv4 IPv6101
AS135606Warp Speed Computers LimitedHostingIPv4 IPv695
AS132695Optimation New Zealand LimitedUnclassifiedIPv465
AS135344Transactor Technologies LimitedUnclassifiedIPv434

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS135069Feenix Communications LimitedUnclassifiedIPv4 IPv61,245
AS15248Metaswitch Networks Corp.UnclassifiedIPv4 IPv6101
AS135606Warp Speed Computers LimitedHostingIPv4 IPv695
AS6939Hurricane Electric LLCTransitIPv690
AS132695Optimation New Zealand LimitedUnclassifiedIPv465
AS135344Transactor Technologies LimitedUnclassifiedIPv434
AS64073Vetta GroupUnclassifiedIPv4 IPv615
AS35280F5 Networks SARLHostingIPv65

Provenance

Where this comes from

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