Observed topology
AS6667 EUNET-FINLAND
Residential APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS6667: 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 |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 40 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 35 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 29 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 20 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 19 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 14 |
| AS1836 | green.ch AG | Residential | IPv4 IPv6 | 4 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 4 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 4 |
| AS42708 | Glesys AB | Unclassified | IPv4 IPv6 | 4 |
Transit
Downstream networks
Networks for which AS6667 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS719 | Elisa Oyj | Unclassified | IPv4 IPv6 | 9,091 |
| AS2586 | Elisa Eesti AS | Unclassified | IPv4 IPv6 | 1,001 |
| AS207003 | Web1 Oy | Hosting | IPv4 IPv6 | 886 |
| AS34263 | MPY Telecom Oy | Unclassified | IPv4 IPv6 | 563 |
| AS57732 | LennuNet Oy | Unclassified | IPv4 | 432 |
| AS8829 | ElmoNet Oy | Residential | IPv4 IPv6 | 385 |
| AS51941 | BaseN Oy | Unclassified | IPv4 IPv6 | 280 |
| AS39194 | Vakka-Suomen Puhelin Oy | Unclassified | IPv4 IPv6 | 267 |
| AS39699 | Lounea Palvelut Oy | Residential | IPv4 IPv6 | 260 |
| AS51935 | BLC Telecom Oy | Unclassified | IPv4 | 240 |
Adjacency
Adjacent networks
Every AS seen directly next to AS6667 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS719 | Elisa Oyj | Unclassified | IPv4 IPv6 | 14,633 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 4,405 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 4,119 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 2,938 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 2,079 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 2,078 |
| AS2586 | Elisa Eesti AS | Unclassified | IPv4 IPv6 | 1,915 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 1,648 |
| AS207003 | Web1 Oy | Hosting | IPv4 IPv6 | 974 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 686 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-19 10: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.