Observed topology
AS12329 TMR
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS12329: 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 |
|---|---|---|---|---|
| AS50629 | LWLcom GmbH | Unclassified | IPv4 IPv6 | 380 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 | 211 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 138 |
| AS34309 | Link11 GmbH | Unclassified | IPv4 | 120 |
| AS15763 | DOKOM Gesellschaft fuer Telekommunikation mbH | Residential | IPv4 | 84 |
| AS16024 | GELSEN-NET Kommunikationsgesellschaft mbH | Unclassified | IPv4 | 32 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 18 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 18 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 | 17 |
| AS4657 | StarHub Ltd | Residential | IPv4 | 17 |
Transit
Downstream networks
Networks for which AS12329 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS203593 | TeleMark Telekommunikationsgesellschaft Mark mbH | Unclassified | IPv4 IPv6 | 523 |
| AS29484 | Ruhr-Universitaet Bochum | Unclassified | IPv4 IPv6 | 365 |
| AS16024 | GELSEN-NET Kommunikationsgesellschaft mbH | Unclassified | IPv4 IPv6 | 239 |
| AS197990 | T&A SYSTEME GmbH | Unclassified | IPv4 IPv6 | 200 |
| AS31184 | Michael Bussmann | Unclassified | IPv4 IPv6 | 160 |
| AS15763 | DOKOM Gesellschaft fuer Telekommunikation mbH | Residential | IPv4 IPv6 | 158 |
| AS60522 | KomMITT-Ratingen GmbH | Unclassified | IPv4 IPv6 | 129 |
| AS207439 | Korves.Net USA LLC | Unclassified | IPv4 IPv6 | 114 |
| AS208527 | Wieland-Werke AG | Unclassified | IPv4 | 61 |
| AS209405 | Westfalen Beteiligungen Aktiengesellschaft | Unclassified | IPv4 | 61 |
Adjacency
Adjacent networks
Every AS seen directly next to AS12329 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS15763 | DOKOM Gesellschaft fuer Telekommunikation mbH | Residential | IPv4 IPv6 | 1,158 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 806 |
| AS50629 | LWLcom GmbH | Unclassified | IPv4 IPv6 | 722 |
| AS203593 | TeleMark Telekommunikationsgesellschaft Mark mbH | Unclassified | IPv4 IPv6 | 616 |
| AS16024 | GELSEN-NET Kommunikationsgesellschaft mbH | Unclassified | IPv4 IPv6 | 420 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 380 |
| AS29484 | Ruhr-Universitaet Bochum | Unclassified | IPv4 IPv6 | 365 |
| AS197990 | T&A SYSTEME GmbH | Unclassified | IPv4 IPv6 | 200 |
| AS34309 | Link11 GmbH | Unclassified | IPv4 | 162 |
| AS31184 | Michael Bussmann | Unclassified | IPv4 IPv6 | 160 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-31 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.50M 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.