asn.dev

Observed topology

AS17686 ACCELIA ACCELIA

Hosting APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS17686: 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
AS2516KDDI CORPORATIONMobileIPv4 IPv6426
AS2519ARTERIA Networks CorporationUnclassifiedIPv4 IPv6364
AS6939Hurricane Electric LLCTransitIPv4170
AS4713NTT DOCOMO BUSINESS,Inc.ResidentialIPv4 IPv689
AS24482SG.GSHostingIPv4 IPv619
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv618
AS131948FORNEXT Inc.UnclassifiedIPv418
AS9304HGC Global Communications LimitedHostingIPv41
AS12389PJSC RostelecomResidentialIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS4693CSK-IT MANAGEMENT CORPORATIONUnclassifiedIPv4 IPv6231
AS59095ACCELIAUnclassifiedIPv460

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS2519ARTERIA Networks CorporationUnclassifiedIPv4 IPv6637
AS2516KDDI CORPORATIONMobileIPv4 IPv6475
AS4693CSK-IT MANAGEMENT CORPORATIONUnclassifiedIPv4 IPv6289
AS6939Hurricane Electric LLCTransitIPv4180
AS4713NTT DOCOMO BUSINESS,Inc.ResidentialIPv4 IPv694
AS59095ACCELIAUnclassifiedIPv460
AS131948FORNEXT Inc.UnclassifiedIPv428
AS24482SG.GSHostingIPv4 IPv620
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv619
AS9304HGC Global Communications LimitedHostingIPv41

All 11 adjacent →

Provenance

Where this comes from

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