Observed topology
AS16086 DNA
Unclassified APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS16086: 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 |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 2,074 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 1,216 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 686 |
| AS1257 | Tele2 Sverige AB | Mobile | IPv4 IPv6 | 84 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 84 |
| AS42708 | Glesys AB | Unclassified | IPv4 IPv6 | 84 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 84 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 77 |
| AS8434 | Telenor Sverige AB | Residential | IPv4 | 77 |
| AS12552 | GlobalConnect AB | Unclassified | IPv4 | 77 |
Transit
Downstream networks
Networks for which AS16086 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS29240 | Loihde Trust Oy | Unclassified | IPv4 IPv6 | 565 |
| AS199486 | Tietokeskus Finland Oy | Unclassified | IPv4 IPv6 | 324 |
| AS62357 | 2M-IT Oy | Unclassified | IPv4 | 295 |
| AS206175 | Meidan IT ja talous Oy | Unclassified | IPv4 | 270 |
| AS214494 | Oy Karl Fazer Ab | Unclassified | IPv4 IPv6 | 250 |
| AS39324 | Mediam Group Oy | Hosting | IPv4 IPv6 | 240 |
| AS8236 | DNA Oyj | Unclassified | IPv4 | 177 |
| AS35175 | Oulun kaupunki | Unclassified | IPv4 | 177 |
| AS206381 | Pinja Digital Oy | Unclassified | IPv4 | 177 |
| AS29282 | Enfo Oy | Unclassified | IPv4 IPv6 | 154 |
Adjacency
Adjacent networks
Every AS seen directly next to AS16086 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 4,243 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 2,525 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,519 |
| AS8236 | DNA Oyj | Unclassified | IPv4 IPv6 | 678 |
| AS29240 | Loihde Trust Oy | Unclassified | IPv4 IPv6 | 565 |
| AS199486 | Tietokeskus Finland Oy | Unclassified | IPv4 IPv6 | 324 |
| AS62357 | 2M-IT Oy | Unclassified | IPv4 | 295 |
| AS39324 | Mediam Group Oy | Hosting | IPv4 IPv6 | 292 |
| AS206175 | Meidan IT ja talous Oy | Unclassified | IPv4 | 270 |
| AS214494 | Oy Karl Fazer Ab | Unclassified | IPv4 IPv6 | 250 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-26 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.