asn.dev

Observed topology

AS13170 KPO-AS

Unclassified RIPE

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS13170: 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
AS9002RETN LimitedUnclassifiedIPv4 IPv6236
AS6667Elisa OyjResidentialIPv4 IPv6173
AS6939Hurricane Electric LLCTransitIPv4 IPv6127
AS50304Blix Solutions ASUnclassifiedIPv4 IPv613
AS24482SG.GSHostingIPv4 IPv611
AS5405Inter.link GmbHUnclassifiedIPv49
AS12552GlobalConnect ABUnclassifiedIPv49
AS20764CJSC RASCOMUnclassifiedIPv49
AS35280F5 Networks SARLHostingIPv49
AS42708Glesys ABUnclassifiedIPv49

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS198024Istekki OyUnclassifiedIPv4 IPv6292
AS60970Data-Enter OyUnclassifiedIPv459
AS60937Savon ICT-palvelut OyUnclassifiedIPv418

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS9002RETN LimitedUnclassifiedIPv4 IPv6422
AS198024Istekki OyUnclassifiedIPv4 IPv6292
AS6667Elisa OyjResidentialIPv4 IPv6286
AS6939Hurricane Electric LLCTransitIPv4 IPv6140
AS60970Data-Enter OyUnclassifiedIPv459
AS50304Blix Solutions ASUnclassifiedIPv4 IPv631
AS12552GlobalConnect ABUnclassifiedIPv427
AS42708Glesys ABUnclassifiedIPv426
AS60937Savon ICT-palvelut OyUnclassifiedIPv418
AS24482SG.GSHostingIPv4 IPv612

Provenance

Where this comes from

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