Observed topology
AS41998 NETCOMBW-AS
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS41998: 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 |
|---|---|---|---|---|
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 1,085 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,058 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 473 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 195 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 67 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 67 |
| AS212024 | Marc Schmitt | Unclassified | IPv4 IPv6 | 67 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 66 |
| AS29504 | Freenet Liberec, z.s. | Unclassified | IPv4 IPv6 | 66 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 66 |
Transit
Downstream networks
Networks for which AS41998 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS207572 | Stadtwerke Baden-Baden | Unclassified | IPv4 IPv6 | 253 |
| AS203865 | overturn technologies GmbH | Unclassified | IPv4 IPv6 | 214 |
| AS206374 | INNEO Solutions GmbH | Unclassified | IPv4 IPv6 | 195 |
| AS39913 | Manuel Wannemacher | Unclassified | IPv4 IPv6 | 130 |
| AS51417 | TBits.net GmbH | Unclassified | IPv4 IPv6 | 126 |
| AS30915 | Liebherr-IT Services GmbH | Unclassified | IPv4 IPv6 | 124 |
| AS31007 | Andreas Stihl AG & Co. KG | Unclassified | IPv4 | 118 |
| AS209081 | HUGO BOSS AG | Unclassified | IPv4 | 105 |
| AS201734 | Camlog Management GmbH | Unclassified | IPv4 IPv6 | 96 |
| AS203829 | Leitz GmbH & Co. KG | Unclassified | IPv4 IPv6 | 96 |
Adjacency
Adjacent networks
Every AS seen directly next to AS41998 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 1,763 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,591 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 906 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 289 |
| AS207572 | Stadtwerke Baden-Baden | Unclassified | IPv4 IPv6 | 253 |
| AS200638 | JH-Computers GmbH | Unclassified | IPv4 IPv6 | 222 |
| AS203865 | overturn technologies GmbH | Unclassified | IPv4 IPv6 | 214 |
| AS206374 | INNEO Solutions GmbH | Unclassified | IPv4 IPv6 | 195 |
| AS39913 | Manuel Wannemacher | Unclassified | IPv4 IPv6 | 130 |
| AS51417 | TBits.net GmbH | Unclassified | IPv4 IPv6 | 126 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-22 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.12M 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.