Observed topology
AS39351 ESAB-AS 31173 Services AB
VPN RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS39351: 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 |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 890 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 835 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 392 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 143 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 124 |
| AS58057 | Securebit AG | Unclassified | IPv4 IPv6 | 81 |
| AS1836 | green.ch AG | Residential | IPv4 IPv6 | 61 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 61 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 61 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 61 |
Transit
Downstream networks
Networks for which AS39351 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS39287 | Materialism s.r.l. | Hosting | IPv4 IPv6 | 641 |
| AS199656 | Zyner | Unclassified | IPv4 IPv6 | 162 |
| AS214365 | Hypefox AB | Hosting | IPv4 IPv6 | 154 |
| AS61282 | BrainMill AB | Residential | IPv4 IPv6 | 136 |
| AS51519 | Karabro AB | Unclassified | IPv4 IPv6 | 122 |
| AS43969 | Prinode AB | Unclassified | IPv4 | 120 |
| AS204538 | Kareby Hosting AB | Hosting | IPv4 IPv6 | 102 |
| AS39910 | Famco AB | Unclassified | IPv4 IPv6 | 94 |
| AS197854 | Eisenia AB | Unclassified | IPv4 IPv6 | 94 |
| AS216025 | Mullvad VPN AB | VPN | IPv4 IPv6 | 94 |
Adjacency
Adjacent networks
Every AS seen directly next to AS39351 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,535 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 1,189 |
| AS41051 | Openfactory GmbH | Unclassified | IPv4 IPv6 | 861 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 763 |
| AS39287 | Materialism s.r.l. | Hosting | IPv4 IPv6 | 670 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 654 |
| AS51519 | Karabro AB | Unclassified | IPv4 IPv6 | 343 |
| AS199656 | Zyner | Unclassified | IPv4 IPv6 | 340 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 307 |
| AS204538 | Kareby Hosting AB | Hosting | IPv4 IPv6 | 238 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-04 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.33M 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.