Observed topology

AS17685 PLAYONLINE SQUARE ENIX CO., LTD.

Unclassified APNIC Enterprise

Upstreams 10 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 11

Adjacent (IPv6) 0

Upstream graph Who carries AS17685, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS17685 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS17685: 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.

AS	Network	Type	Families	Paths seen
AS32787	Akamai Technologies, Inc.	Hosting	IPv4	180
AS2914	NTT America, Inc.	Transit	IPv4	19
AS2518	BIGLOBE Inc.	Residential	IPv4	13
AS174	Cogent Communications, LLC	Transit	IPv4	12
AS6939	Hurricane Electric LLC	Transit	IPv4	9
AS2497	Internet Initiative Japan Inc.	Unclassified	IPv4	2
AS9002	RETN Limited	Unclassified	IPv4	1
AS12389	PJSC Rostelecom	Residential	IPv4	1
AS17639	Converge ICT Solutions Inc.	Unclassified	IPv4	1
AS24482	SG.GS	Hosting	IPv4	1

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS23784	SQUARE ENIX CO., LTD.	Unclassified	IPv4	476

Adjacency

Adjacent networks

All 11

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

AS	Network	Type	Families	Paths seen
AS23784	SQUARE ENIX CO., LTD.	Unclassified	IPv4	476
AS32787	Akamai Technologies, Inc.	Hosting	IPv4	420
AS2914	NTT America, Inc.	Transit	IPv4	98
AS2518	BIGLOBE Inc.	Residential	IPv4	64
AS174	Cogent Communications, LLC	Transit	IPv4	60
AS6939	Hurricane Electric LLC	Transit	IPv4	45
AS2497	Internet Initiative Japan Inc.	Unclassified	IPv4	10
AS12389	PJSC Rostelecom	Residential	IPv4	5
AS17639	Converge ICT Solutions Inc.	Unclassified	IPv4	5
AS24482	SG.GS	Hosting	IPv4	5

All 11 adjacent →

Provenance

Where this comes from

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