Observed topology
AS43641 SOLLUTIUM-NL
Unclassified APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS43641: 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 |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 4,841 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 1,294 |
| AS3223 | Voxility LLP | Hosting | IPv4 | 1,160 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 131 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 113 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 111 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 111 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 111 |
| AS50300 | CustodianDC Limited | Unclassified | IPv4 IPv6 | 110 |
| AS37721 | Virtual-Technologies-Solutions-SA | Residential | IPv4 | 105 |
Transit
Downstream networks
Networks for which AS43641 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS58285 | Sixnet Operation Ltd | Unclassified | IPv6 | 9,472 |
| AS30860 | Virtual Systems LLC | Hosting | IPv4 | 186 |
| AS202319 | Hezardastan Unit Cloud Computing PJSC | Unclassified | IPv4 | 144 |
| AS214300 | Layer 4 Group LLC | Unclassified | IPv4 | 128 |
| AS198231 | Sixnet Operation Ltd | Unclassified | IPv4 | 64 |
| AS33042 | Netiface LLC | Unclassified | IPv6 | 37 |
| AS211019 | moula world llc | Unclassified | IPv6 | 37 |
| AS214168 | Sixnet Operation Ltd | Unclassified | IPv6 | 37 |
| AS215158 | Sixnet Operation Ltd | Unclassified | IPv6 | 37 |
| AS215310 | Pfcloud UG (haftungsbeschrankt) | Unclassified | IPv6 | 37 |
Adjacency
Adjacent networks
Every AS seen directly next to AS43641 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 12,054 |
| AS58285 | Sixnet Operation Ltd | Unclassified | IPv6 | 9,472 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 2,145 |
| AS3223 | Voxility LLP | Hosting | IPv4 | 1,223 |
| AS29632 | Netassist International EOOD | Unclassified | IPv6 | 518 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 383 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 372 |
| AS50300 | CustodianDC Limited | Unclassified | IPv4 IPv6 | 371 |
| AS213241 | TECHIT.BE SRL | Residential | IPv6 | 271 |
| AS25091 | IP-Max SA | Unclassified | IPv6 | 263 |
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.