Observed topology
AS198967 BITEL-GESELLSCHAFT-FUER-TELEKOMMUNIKATION-AS - IP Transit Customer AS33873 -
Unclassified RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS198967: 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,737 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 867 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 611 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 201 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 70 |
| AS34019 | Hivane Association | Unclassified | IPv4 IPv6 | 70 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 70 |
| AS6797 | GlobalConnect AB | Unclassified | IPv4 | 62 |
| AS8551 | Bezeq International Ltd. | Unclassified | IPv4 | 62 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 | 62 |
Transit
Downstream networks
Networks for which AS198967 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS207486 | aov IT.Services GmbH | Unclassified | IPv4 IPv6 | 413 |
| AS15779 | Reply S.p.A. | Unclassified | IPv4 | 215 |
| AS43155 | Stadtwerke Bielefeld GmbH | Unclassified | IPv4 IPv6 | 159 |
| AS12466 | Bicos Computer GmbH | Unclassified | IPv4 IPv6 | 91 |
| AS25102 | CompAct GmbH Computer und Kommunikation | Unclassified | IPv4 | 56 |
| AS204065 | OXITGEN AG | Unclassified | IPv4 IPv6 | 54 |
| AS12460 | mandala IT GmbH | Unclassified | IPv4 | 43 |
Adjacency
Adjacent networks
Every AS seen directly next to AS198967 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 2,294 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 1,077 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 622 |
| AS207486 | aov IT.Services GmbH | Unclassified | IPv4 IPv6 | 413 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 263 |
| AS15779 | Reply S.p.A. | Unclassified | IPv4 | 215 |
| AS43155 | Stadtwerke Bielefeld GmbH | Unclassified | IPv4 IPv6 | 159 |
| AS12466 | Bicos Computer GmbH | Unclassified | IPv4 IPv6 | 120 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 94 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 94 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-29 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.36M 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.