asn.dev

Observed topology

AS149440 EVOXTENTERPRISE-AS-AP Evoxt Enterprise

Unclassified APNIC Cable/DSL/ISP

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

Transit

Upstream networks

All 21

Networks observed carrying traffic for AS149440: 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
AS18450WebNX, Inc.HostingIPv4 IPv63,500
AS13335Cloudflare, Inc.HostingIPv42,812
AS25369Hydra Communications LtdHostingIPv4 IPv61,761
AS4785xTomResidentialIPv4 IPv6835
AS6939Hurricane Electric LLCTransitIPv4 IPv6829
AS24482SG.GSHostingIPv4 IPv6575
AS58325Hydra Communications LtdHostingIPv4 IPv6328
AS2914NTT America, Inc.TransitIPv4 IPv6254
AS9312xTomHostingIPv4 IPv6202
AS201814MEVSPACE sp. z o.o.HostingIPv4 IPv6167

All 21 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 21

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

ASNetworkTypeFamiliesPaths seen
AS18450WebNX, Inc.HostingIPv4 IPv63,500
AS13335Cloudflare, Inc.HostingIPv42,812
AS25369Hydra Communications LtdHostingIPv4 IPv61,761
AS4785xTomResidentialIPv4 IPv6835
AS6939Hurricane Electric LLCTransitIPv4 IPv6829
AS24482SG.GSHostingIPv4 IPv6575
AS58325Hydra Communications LtdHostingIPv4 IPv6328
AS2914NTT America, Inc.TransitIPv4 IPv6254
AS9312xTomHostingIPv4 IPv6202
AS201814MEVSPACE sp. z o.o.HostingIPv4 IPv6167

All 21 adjacent →

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.