Observed topology
AS5405 INTERDOTLINK Inter.link GmbH
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS5405: 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 |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 467 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 362 |
| AS58057 | Securebit AG | Unclassified | IPv4 IPv6 | 109 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 99 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 86 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 74 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 71 |
| AS1836 | green.ch AG | Residential | IPv4 IPv6 | 62 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 62 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 62 |
Transit
Downstream networks
Networks for which AS5405 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS202656 | Ivanov Vitaliy Sergeevich | Unclassified | IPv4 IPv6 | 11,965 |
| AS48031 | Ivanov Vitaliy Sergeevich | Unclassified | IPv4 IPv6 | 10,285 |
| AS47583 | Hostinger International Limited | Hosting | IPv4 IPv6 | 4,264 |
| AS14593 | Space Exploration Technologies Corporation | Residential | IPv4 IPv6 | 3,733 |
| AS8648 | dogado GmbH | Hosting | IPv4 IPv6 | 2,079 |
| AS25291 | SysEleven GmbH | Hosting | IPv4 IPv6 | 1,972 |
| AS49453 | Global Layer B.V. | Hosting | IPv4 IPv6 | 1,906 |
| AS200651 | FlokiNET ehf | Unclassified | IPv4 IPv6 | 1,652 |
| AS20676 | Plusnet GmbH | Unclassified | IPv4 IPv6 | 1,590 |
| AS200019 | ALEXHOST S.R.L. | Unclassified | IPv4 IPv6 | 1,493 |
Adjacency
Adjacent networks
Every AS seen directly next to AS5405 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 15,041 |
| AS202656 | Ivanov Vitaliy Sergeevich | Unclassified | IPv4 IPv6 | 11,965 |
| AS50628 | Leonix Telecom SAS | Unclassified | IPv4 IPv6 | 11,824 |
| AS6663 | Euroweb Romania S.R.L. | Unclassified | IPv4 IPv6 | 11,642 |
| AS202365 | Omer GOLGELI | Unclassified | IPv4 | 10,651 |
| AS48031 | Ivanov Vitaliy Sergeevich | Unclassified | IPv4 IPv6 | 10,354 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 9,982 |
| AS8717 | A1 Bulgaria EAD | Residential | IPv4 IPv6 | 9,893 |
| AS8280 | SYNAPSECOM S.A. Provider of Telecommunications and Internet Services | Hosting | IPv4 IPv6 | 9,726 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 8,932 |
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.