Observed topology
AS16302 SUOMICOMMUNICATIONS Suomi Communications Oy
Residential RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS16302: 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.
Transit
Downstream networks
Networks for which AS16302 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS41369 | Advania Finland Oy | Hosting | IPv4 IPv6 | 464 |
| AS58003 | Planeetta Internet Oy | Unclassified | IPv4 IPv6 | 361 |
| AS214494 | Oy Karl Fazer Ab | Unclassified | IPv4 IPv6 | 269 |
| AS1342 | IDDQD-AS | Hosting | IPv4 IPv6 | 241 |
| AS35382 | Glesys Sweden AB | Hosting | IPv4 IPv6 | 201 |
| AS51728 | Seltimil Oy | Residential | IPv4 | 196 |
| AS60414 | Baytems Holdings Oy | Unclassified | IPv4 IPv6 | 180 |
| AS213547 | Hindersby-Backby Service Ab | Unclassified | IPv4 | 124 |
| AS203195 | DT-Link Oy | Unclassified | IPv4 | 122 |
| AS49283 | Setera Oy | Unclassified | IPv4 | 112 |
Adjacency
Adjacent networks
Every AS seen directly next to AS16302 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS24940 | Hetzner Online GmbH | Hosting | IPv4 IPv6 | 3,876 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 616 |
| AS58003 | Planeetta Internet Oy | Unclassified | IPv4 IPv6 | 471 |
| AS41369 | Advania Finland Oy | Hosting | IPv4 IPv6 | 464 |
| AS12552 | GlobalConnect AB | Unclassified | IPv4 IPv6 | 379 |
| AS51728 | Seltimil Oy | Residential | IPv4 | 315 |
| AS214494 | Oy Karl Fazer Ab | Unclassified | IPv4 IPv6 | 269 |
| AS1342 | IDDQD-AS | Hosting | IPv4 IPv6 | 241 |
| AS35382 | Glesys Sweden AB | Hosting | IPv4 IPv6 | 201 |
| AS60414 | Baytems Holdings Oy | Unclassified | IPv4 IPv6 | 180 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-09 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.03M 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.