asn.dev

Observed topology

AS9286 KINXIDC-AS-KR KINX

Hosting APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS9286: 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
AS9957KINXHostingIPv4 IPv68,518
AS9318SK Broadband Co LtdUnclassifiedIPv48
AS3786LG DACOM CorporationUnclassifiedIPv45
AS4766Korea TelecomMobileIPv43

Transit

Downstream networks

All 26

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

ASNetworkTypeFamiliesPaths seen
AS17589GABIA Inc.HostingIPv45,897
AS4792NATE Communications CorporationUnclassifiedIPv4891
AS17877KX NexG Co., LTDUnclassifiedIPv4627
AS63199CDS Global Cloud Co., LtdHostingIPv4600
AS46003CONNECTWAVEUnclassifiedIPv4555
AS24429Zhejiang Taobao Network Co.,LtdHostingIPv4 IPv6480
AS45382HostcenterUnclassifiedIPv4 IPv6470
AS45102Alibaba (US) Technology Co., Ltd.HostingIPv4 IPv6417
AS152205imobi inc,UnclassifiedIPv4248
AS9639Artist Company Inc.UnclassifiedIPv4 IPv6223

Adjacency

Adjacent networks

All 33

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

ASNetworkTypeFamiliesPaths seen
AS9957KINXHostingIPv4 IPv620,088
AS17589GABIA Inc.HostingIPv45,897
AS4766Korea TelecomMobileIPv4 IPv6910
AS20473The Constant Company, LLCHostingIPv6909
AS4792NATE Communications CorporationUnclassifiedIPv4891
AS17877KX NexG Co., LTDUnclassifiedIPv4627
AS63199CDS Global Cloud Co., LtdHostingIPv4600
AS46003CONNECTWAVEUnclassifiedIPv4555
AS24429Zhejiang Taobao Network Co.,LtdHostingIPv4 IPv6480
AS45382HostcenterUnclassifiedIPv4 IPv6470

Provenance

Where this comes from

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