Observed topology
AS16097 HLKOMM 04107 Leipzig
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS16097: 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 | 551 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 402 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 305 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 264 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 167 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 148 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 98 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 43 |
| AS29504 | Freenet Liberec, z.s. | Unclassified | IPv4 IPv6 | 43 |
| AS34019 | Hivane Association | Unclassified | IPv4 IPv6 | 43 |
Transit
Downstream networks
Networks for which AS16097 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS50436 | Tele Columbus AG | Unclassified | IPv4 IPv6 | 3,094 |
| AS16202 | Tele Columbus AG | Unclassified | IPv4 IPv6 | 1,562 |
| AS35244 | Tele Columbus AG | Unclassified | IPv4 IPv6 | 837 |
| AS20880 | Tele Columbus AG | Unclassified | IPv4 IPv6 | 410 |
| AS211007 | Netz Leipzig GmbH | Unclassified | IPv4 IPv6 | 204 |
| AS210589 | NetCommunity GmbH | Unclassified | IPv4 IPv6 | 200 |
| AS216451 | Daten- und Telekommunikations GmbH Dessau | Unclassified | IPv4 IPv6 | 186 |
| AS210994 | Relaxdays GmbH | Unclassified | IPv4 IPv6 | 140 |
| AS44365 | newone GmbH | Unclassified | IPv4 | 130 |
| AS206240 | pdv-systeme Sachsen GmbH | Unclassified | IPv4 | 118 |
Adjacency
Adjacent networks
Every AS seen directly next to AS16097 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS50436 | Tele Columbus AG | Unclassified | IPv4 IPv6 | 3,094 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 2,231 |
| AS16202 | Tele Columbus AG | Unclassified | IPv4 IPv6 | 1,575 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 1,561 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,315 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,054 |
| AS35244 | Tele Columbus AG | Unclassified | IPv4 IPv6 | 837 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 804 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 505 |
| AS20880 | Tele Columbus AG | Unclassified | IPv4 IPv6 | 410 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-11 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.47M 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.