Observed topology
AS24961 MYLOC-AS WIIT AG
Hosting RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS24961: 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 | 523 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 379 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 365 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 167 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 154 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 129 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 122 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 108 |
| AS1836 | green.ch AG | Residential | IPv4 IPv6 | 61 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 61 |
Transit
Downstream networks
Networks for which AS24961 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS60164 | Webtrekk GmbH | Unclassified | IPv4 IPv6 | 900 |
| AS42263 | WIIT AG | Hosting | IPv4 IPv6 | 663 |
| AS204035 | oneCorp GmbH | Hosting | IPv4 IPv6 | 634 |
| AS209014 | NETGO GmbH | Hosting | IPv4 | 464 |
| AS49609 | Intersolute GmbH | Unclassified | IPv4 | 456 |
| AS60522 | KomMITT-Ratingen GmbH | Unclassified | IPv4 IPv6 | 399 |
| AS62086 | VIA-ONLINE GmbH | Hosting | IPv4 IPv6 | 392 |
| AS41412 | WIIT AG | Hosting | IPv4 IPv6 | 374 |
| AS50873 | David Doepelheuer | Hosting | IPv4 IPv6 | 357 |
| AS215004 | Sebastian Bruechner | Unclassified | IPv4 IPv6 | 345 |
Adjacency
Adjacent networks
Every AS seen directly next to AS24961 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS34872 | Sarah Rossius trading as Servperso Systems | Hosting | IPv4 IPv6 | 2,953 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 2,895 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,812 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,756 |
| AS50873 | David Doepelheuer | Hosting | IPv4 IPv6 | 1,744 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 1,723 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 1,084 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 1,025 |
| AS60164 | Webtrekk GmbH | Unclassified | IPv4 IPv6 | 900 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 820 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-09 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.03M 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.