Observed topology
AS25394 MK-NETZDIENSTE-AS
Residential RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS25394: 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 |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 481 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 342 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 325 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 70 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 58 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 32 |
| AS401753 | BIXCE Inc | Unclassified | IPv4 IPv6 | 32 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 31 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 30 |
| AS57821 | Nonattached Network e.V. | Unclassified | IPv4 IPv6 | 30 |
Transit
Downstream networks
Networks for which AS25394 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS59790 | Marco Bungalski GmbH | Residential | IPv4 IPv6 | 454 |
| AS206423 | binsec systems GmbH | Unclassified | IPv4 IPv6 | 394 |
| AS41723 | Jens Christian Schneeweiss trading as Technische Systemprogrammierung | Unclassified | IPv4 IPv6 | 285 |
| AS9188 | InfoServe GmbH | Hosting | IPv4 IPv6 | 232 |
| AS41163 | RIZ IT MOTION GmbH | Unclassified | IPv4 IPv6 | 189 |
| AS209981 | System Crew GmbH | Unclassified | IPv4 | 188 |
| AS211909 | Hope Media Europe e.V. | Unclassified | IPv4 | 184 |
| AS9197 | becom Systemhaus Verwaltungs-GmbH | Unclassified | IPv4 IPv6 | 163 |
| AS20792 | VISTEC Internet Service GmbH | Unclassified | IPv4 IPv6 | 148 |
| AS31147 | Inline Internet Online Dienste GmbH | Hosting | IPv4 | 124 |
Adjacency
Adjacent networks
Every AS seen directly next to AS25394 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 1,324 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,005 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 881 |
| AS59790 | Marco Bungalski GmbH | Residential | IPv4 IPv6 | 496 |
| AS206423 | binsec systems GmbH | Unclassified | IPv4 IPv6 | 394 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 333 |
| AS41723 | Jens Christian Schneeweiss trading as Technische Systemprogrammierung | Unclassified | IPv4 IPv6 | 285 |
| AS9188 | InfoServe GmbH | Hosting | IPv4 IPv6 | 232 |
| AS25560 | rh-tec Business GmbH | Hosting | IPv4 IPv6 | 192 |
| AS41163 | RIZ IT MOTION GmbH | Unclassified | IPv4 IPv6 | 189 |
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.