asn.dev

Observed topology

AS10022 DSLAK-AS-AP - Internet access for Datacom Systems Auckland

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS10022: 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
AS9790Two Degrees Networks LimitedResidentialIPv41,696
AS55850Mercury NZ LimitedResidentialIPv4284
AS64073Vetta GroupUnclassifiedIPv431
AS6939Hurricane Electric LLCTransitIPv49

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS136497Verifone Australia (HAPL) Pty LtdUnclassifiedIPv4128

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9790Two Degrees Networks LimitedResidentialIPv41,822
AS55850Mercury NZ LimitedResidentialIPv4284
AS136497Verifone Australia (HAPL) Pty LtdUnclassifiedIPv4128
AS64073Vetta GroupUnclassifiedIPv433
AS6939Hurricane Electric LLCTransitIPv49

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.