asn.dev

Observed topology

AS16186 ASN-SSC

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS16186: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6376
AS6939Hurricane Electric LLCTransitIPv4 IPv6171
AS174Cogent Communications, LLCTransitIPv4 IPv6119
AS24482SG.GSHostingIPv4 IPv615
AS42708Glesys ABUnclassifiedIPv4 IPv615
AS56655Gigahost ASUnclassifiedIPv4 IPv615
AS33891Core-Backbone GmbHHostingIPv410
AS50304Blix Solutions ASUnclassifiedIPv410
AS49788Nexthop ASUnclassifiedIPv49
AS12552GlobalConnect ABUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS50582Bent Oystein BostadUnclassifiedIPv4 IPv6122
AS197000Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv41

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6433
AS6939Hurricane Electric LLCTransitIPv4 IPv6199
AS174Cogent Communications, LLCTransitIPv4 IPv6145
AS50582Bent Oystein BostadUnclassifiedIPv4 IPv6122
AS24482SG.GSHostingIPv4 IPv618
AS42708Glesys ABUnclassifiedIPv4 IPv618
AS56655Gigahost ASUnclassifiedIPv4 IPv618
AS33891Core-Backbone GmbHHostingIPv411
AS50304Blix Solutions ASUnclassifiedIPv411
AS49788Nexthop ASUnclassifiedIPv410

All 12 adjacent →

Provenance

Where this comes from

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