asn.dev

Observed topology

AS17766 NEXON-AS-AP - Nexon Asia Pacific Pty Ltd

Unclassified APNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS17766: 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
AS38195SuperloopUnclassifiedIPv4 IPv62,304
AS2764AAPT LimitedUnclassifiedIPv4 IPv61,316
AS6939Hurricane Electric LLCTransitIPv4 IPv6682
AS24482SG.GSHostingIPv4 IPv681
AS64073Vetta GroupUnclassifiedIPv4 IPv681
AS4608Asia Pacific Network Information CentreUnclassifiedIPv475
AS35280F5 Networks SARLHostingIPv45

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS133510Infinet Broadband Pty LtdUnclassifiedIPv4118
AS139246Twin Towns Services Club LtdUnclassifiedIPv418

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS38195SuperloopUnclassifiedIPv4 IPv62,407
AS2764AAPT LimitedUnclassifiedIPv4 IPv61,316
AS6939Hurricane Electric LLCTransitIPv4 IPv6706
AS133510Infinet Broadband Pty LtdUnclassifiedIPv4118
AS24482SG.GSHostingIPv4 IPv684
AS64073Vetta GroupUnclassifiedIPv4 IPv684
AS4608Asia Pacific Network Information CentreUnclassifiedIPv478
AS139246Twin Towns Services Club LtdUnclassifiedIPv418
AS35280F5 Networks SARLHostingIPv45

Provenance

Where this comes from

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