Observed topology
AS12611 RKOM R-KOM Regensburger Telekommunikationsgesellschaft mbH
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS12611: 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 |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 387 |
| AS60169 | R-KOM Regensburger Telekommunikationsgesellschaft mbH | Unclassified | IPv4 IPv6 | 209 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 136 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 49 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 48 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 17 |
| AS212024 | Marc Schmitt | Unclassified | IPv4 IPv6 | 17 |
| AS213241 | TECHIT.BE SRL | Residential | IPv4 IPv6 | 17 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 16 |
| AS6797 | GlobalConnect AB | Unclassified | IPv4 | 16 |
Transit
Downstream networks
Networks for which AS12611 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS20902 | DegNet GmbH | Unclassified | IPv4 IPv6 | 399 |
| AS204796 | Krones AG | Unclassified | IPv4 IPv6 | 198 |
| AS41307 | Telepark Passau GmbH | Unclassified | IPv4 IPv6 | 151 |
| AS209537 | Vying Technologies OU | Hosting | IPv4 IPv6 | 89 |
| AS13012 | Stefan Englhardt | Unclassified | IPv4 IPv6 | 83 |
| AS205033 | Stadt Regensburg | Unclassified | IPv4 IPv6 | 78 |
| AS200224 | DWE GmbH | Unclassified | IPv4 | 62 |
| AS214014 | Stadt Straubing | Unclassified | IPv4 | 62 |
| AS25504 | Vautron Rechenzentrum AG | Hosting | IPv4 IPv6 | 60 |
Adjacency
Adjacent networks
Every AS seen directly next to AS12611 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 720 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 637 |
| AS20902 | DegNet GmbH | Unclassified | IPv4 IPv6 | 608 |
| AS60169 | R-KOM Regensburger Telekommunikationsgesellschaft mbH | Unclassified | IPv4 IPv6 | 393 |
| AS41307 | Telepark Passau GmbH | Unclassified | IPv4 IPv6 | 339 |
| AS204796 | Krones AG | Unclassified | IPv4 IPv6 | 198 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 168 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 153 |
| AS13012 | Stefan Englhardt | Unclassified | IPv4 IPv6 | 118 |
| AS209537 | Vying Technologies OU | Hosting | IPv4 IPv6 | 89 |
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.