Observed topology
AS47605 FNE-AS FNE-Finland Oy
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS47605: 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 | 116 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 97 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 70 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 53 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 | 21 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 14 |
| AS24482 | SG.GS | Hosting | IPv4 | 8 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 8 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 7 |
| AS8551 | Bezeq International Ltd. | Unclassified | IPv4 | 7 |
Transit
Downstream networks
Networks for which AS47605 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS209378 | Inios Oy | Unclassified | IPv4 IPv6 | 1,035 |
| AS206175 | Meidan IT ja talous Oy | Unclassified | IPv4 | 911 |
| AS198024 | Istekki Oy | Unclassified | IPv4 IPv6 | 858 |
| AS201172 | Suupohjan Seutuverkko Oy | Unclassified | IPv4 IPv6 | 563 |
| AS198859 | Osuuskunta Keskikaista | Unclassified | IPv4 | 531 |
| AS51935 | BLC Telecom Oy | Unclassified | IPv4 IPv6 | 512 |
| AS207065 | Joki ICT Oy | Unclassified | IPv4 | 495 |
| AS60869 | Jarvi-Suomen Valokuitu Oy | Unclassified | IPv4 | 471 |
| AS57359 | Pyhanet Oy | Unclassified | IPv4 | 470 |
| AS43016 | Keski-Suomen Valokuituverkot Oy | Unclassified | IPv4 | 443 |
Adjacency
Adjacent networks
Every AS seen directly next to AS47605 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 3,756 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 3,494 |
| AS209378 | Inios Oy | Unclassified | IPv4 IPv6 | 2,361 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,946 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 1,173 |
| AS206175 | Meidan IT ja talous Oy | Unclassified | IPv4 | 911 |
| AS198024 | Istekki Oy | Unclassified | IPv4 IPv6 | 858 |
| AS199508 | S1 Networks Oy | Residential | IPv4 IPv6 | 620 |
| AS39242 | Seclan Oy | Hosting | IPv4 IPv6 | 598 |
| AS39324 | Mediam Group Oy | Hosting | IPv4 IPv6 | 580 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M 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.