asn.dev

Observed topology

AS18119 ACSDATA-NZ ACSData

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS18119: 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
AS6461Zayo BandwidthTransitIPv4 IPv6358
AS3257GTT Communications Inc.TransitIPv4 IPv6288
AS6939Hurricane Electric LLCTransitIPv4 IPv6140
AS24482SG.GSHostingIPv4 IPv615
AS64073Vetta GroupUnclassifiedIPv4 IPv615
AS17639Converge ICT Solutions Inc.UnclassifiedIPv414
AS24115EquinixHostingIPv414
AS9002RETN LimitedUnclassifiedIPv63

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS24226Catalyst.Net LtdHostingIPv649
AS132840Neos Systems LimitedUnclassifiedIPv445
AS134845Wellington International Airport LimitedUnclassifiedIPv49

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4 IPv6424
AS3257GTT Communications Inc.TransitIPv4 IPv6310
AS6939Hurricane Electric LLCTransitIPv4 IPv6152
AS24226Catalyst.Net LtdHostingIPv649
AS132840Neos Systems LimitedUnclassifiedIPv445
AS24482SG.GSHostingIPv4 IPv617
AS24115EquinixHostingIPv415
AS64073Vetta GroupUnclassifiedIPv4 IPv615
AS17639Converge ICT Solutions Inc.UnclassifiedIPv414
AS134845Wellington International Airport LimitedUnclassifiedIPv49

All 11 adjacent →

Provenance

Where this comes from

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