Observed topology
AS198726 KOMDSL Wemaconnect GmbH
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS198726: 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 |
|---|---|---|---|---|
| AS51978 | WEMACOM Telekommunikation GmbH | Residential | IPv4 IPv6 | 334 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 127 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 78 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 40 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 26 |
| AS1836 | green.ch AG | Residential | IPv4 IPv6 | 14 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 14 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 14 |
| AS34019 | Hivane Association | Unclassified | IPv4 IPv6 | 14 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 14 |
Transit
Downstream networks
Networks for which AS198726 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS204672 | stadtwerker Versorgungs GmbH | Unclassified | IPv4 | 171 |
| AS41086 | N-ERGIE Aktiengesellschaft | Unclassified | IPv4 | 165 |
| AS204138 | REHAU Management SE trading as REHAU Industries SE & Co. KG | Unclassified | IPv4 IPv6 | 91 |
| AS205869 | GASCADE Gastransport GmbH | Unclassified | IPv4 IPv6 | 89 |
| AS211800 | Barmherzige Brueder Trier gGmbH | Unclassified | IPv4 | 60 |
| AS41163 | RIZ IT MOTION GmbH | Unclassified | IPv4 IPv6 | 40 |
| AS212672 | Kurtz Holding GmbH | Unclassified | IPv4 | 20 |
Adjacency
Adjacent networks
Every AS seen directly next to AS198726 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS51978 | WEMACOM Telekommunikation GmbH | Residential | IPv4 IPv6 | 609 |
| AS204672 | stadtwerker Versorgungs GmbH | Unclassified | IPv4 | 257 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 244 |
| AS41086 | N-ERGIE Aktiengesellschaft | Unclassified | IPv4 | 165 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 116 |
| AS204138 | REHAU Management SE trading as REHAU Industries SE & Co. KG | Unclassified | IPv4 IPv6 | 91 |
| AS205869 | GASCADE Gastransport GmbH | Unclassified | IPv4 IPv6 | 89 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 81 |
| AS211800 | Barmherzige Brueder Trier gGmbH | Unclassified | IPv4 | 60 |
| AS41163 | RIZ IT MOTION GmbH | Unclassified | IPv4 IPv6 | 40 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.