Observed topology
AS16347 INHERENT
Hosting RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS16347: 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 | 2,672 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,647 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,494 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 466 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 308 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 308 |
| AS50628 | Leonix Telecom SAS | Unclassified | IPv4 IPv6 | 169 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 158 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 158 |
| AS50300 | CustodianDC Limited | Unclassified | IPv4 IPv6 | 158 |
Transit
Downstream networks
Networks for which AS16347 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS210403 | Groupe LWS SARL | Unclassified | IPv4 IPv6 | 2,548 |
| AS214490 | ASII TELECOM SARL | Unclassified | IPv4 | 177 |
| AS210666 | MIXTRIO SAS | Unclassified | IPv4 IPv6 | 150 |
| AS202215 | OSPI SAS | Unclassified | IPv4 | 134 |
| AS51038 | Hospices civils de Lyon | Unclassified | IPv4 IPv6 | 94 |
| AS201659 | Centre Hospitalier Regional de Marseille | Unclassified | IPv4 IPv6 | 90 |
| AS57928 | Prodware SA | Hosting | IPv4 IPv6 | 68 |
| AS30839 | Chambre de Commerce et d'Industrie Pau Bearn | Unclassified | IPv4 | 59 |
| AS47300 | Institut National Recherche Securite | Unclassified | IPv4 | 59 |
| AS49068 | STORMSHIELD SAS | Unclassified | IPv4 | 59 |
Adjacency
Adjacent networks
Every AS seen directly next to AS16347 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 3,996 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 3,100 |
| AS210403 | Groupe LWS SARL | Unclassified | IPv4 IPv6 | 2,548 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,925 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 539 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 346 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 334 |
| AS50628 | Leonix Telecom SAS | Unclassified | IPv4 IPv6 | 201 |
| AS50300 | CustodianDC Limited | Unclassified | IPv4 IPv6 | 193 |
| AS204092 | Association GRIFON | Unclassified | IPv4 IPv6 | 189 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-24 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 72.94M 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.