Observed topology
AS42652 DELUNET
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS42652: 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 |
|---|---|---|---|---|
| AS8899 | inexio Informationstechnologie und Telekommunikation Gmbh | Residential | IPv4 IPv6 | 2,393 |
Transit
Downstream networks
Networks for which AS42652 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS34240 | manitu GmbH | Hosting | IPv4 IPv6 | 183 |
| AS12853 | InfraServ GmbH trading as InfraServ GmbH & Co. Gendorf KG | Unclassified | IPv4 IPv6 | 121 |
| AS202429 | Roedl IT Operation GmbH | Unclassified | IPv4 | 120 |
| AS3573 | Accenture LLP | Unclassified | IPv6 | 66 |
| AS16017 | Hager Electro GmbH & Co. KG | Unclassified | IPv4 | 60 |
| AS200397 | Bioscientia Institut fuer Medizinische Diagnostik GmbH | Unclassified | IPv4 | 60 |
| AS50332 | SQUILD GmbH | Unclassified | IPv4 IPv6 | 49 |
| AS196819 | DEMANDO GmbH | Unclassified | IPv4 IPv6 | 44 |
| AS44569 | 1api GmbH | Unclassified | IPv4 IPv6 | 34 |
| AS208574 | Communaute de Communes du Pays de Bitche | Unclassified | IPv4 IPv6 | 29 |
Adjacency
Adjacent networks
Every AS seen directly next to AS42652 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS8899 | inexio Informationstechnologie und Telekommunikation Gmbh | Residential | IPv4 IPv6 | 3,244 |
| AS34240 | manitu GmbH | Hosting | IPv4 IPv6 | 183 |
| AS12853 | InfraServ GmbH trading as InfraServ GmbH & Co. Gendorf KG | Unclassified | IPv4 IPv6 | 121 |
| AS202429 | Roedl IT Operation GmbH | Unclassified | IPv4 | 120 |
| AS50332 | SQUILD GmbH | Unclassified | IPv4 IPv6 | 73 |
| AS3573 | Accenture LLP | Unclassified | IPv6 | 66 |
| AS16017 | Hager Electro GmbH & Co. KG | Unclassified | IPv4 | 60 |
| AS200397 | Bioscientia Institut fuer Medizinische Diagnostik GmbH | Unclassified | IPv4 | 60 |
| AS196819 | DEMANDO GmbH | Unclassified | IPv4 IPv6 | 44 |
| AS44569 | 1api GmbH | Unclassified | IPv4 IPv6 | 34 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-30 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.49M 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.