Observed topology
AS34953 RELAIX RelAix Networks GmbH
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS34953: 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 | 489 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 327 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 276 |
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 135 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 53 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 31 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 31 |
| AS401753 | BIXCE Inc | Unclassified | IPv4 IPv6 | 31 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 30 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 30 |
Transit
Downstream networks
Networks for which AS34953 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS209740 | m3connect GmbH | Unclassified | IPv4 IPv6 | 214 |
| AS6833 | Terranets bw GmbH | Unclassified | IPv4 IPv6 | 177 |
| AS48823 | Hosting.de GmbH | Unclassified | IPv4 IPv6 | 118 |
| AS212472 | Christian Stuellenberg, trading as Engelsing, Bernd und Stuellenberg, Christian GbR | Unclassified | IPv4 IPv6 | 110 |
| AS42035 | Vikings GmbH | Unclassified | IPv4 IPv6 | 99 |
| AS215641 | Ariadne GmbH | Unclassified | IPv4 IPv6 | 99 |
| AS60393 | Hammer GmbH trading as Hammer GmbH & Co. KG | Unclassified | IPv4 IPv6 | 97 |
| AS28731 | Intrabit GmbH | Unclassified | IPv4 | 62 |
| AS205037 | Kisters AG | Unclassified | IPv4 IPv6 | 51 |
| AS29373 | Weiss-Druck GmbH & Co. KG | Unclassified | IPv4 | 46 |
Adjacency
Adjacent networks
Every AS seen directly next to AS34953 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 726 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 704 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 531 |
| AS48823 | Hosting.de GmbH | Unclassified | IPv4 IPv6 | 310 |
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 271 |
| AS209740 | m3connect GmbH | Unclassified | IPv4 IPv6 | 214 |
| AS6833 | Terranets bw GmbH | Unclassified | IPv4 IPv6 | 210 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 119 |
| AS212472 | Christian Stuellenberg, trading as Engelsing, Bernd und Stuellenberg, Christian GbR | Unclassified | IPv4 IPv6 | 110 |
| AS42035 | Vikings GmbH | Unclassified | IPv4 IPv6 | 99 |
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.