Observed topology
AS50628 LEONIX-TELECOM Leonix Telecom
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS50628: 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 |
|---|---|---|---|---|
| AS35280 | F5 Networks SARL | Hosting | IPv4 IPv6 | 368 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 126 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 121 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 55 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 | 34 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 16 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 16 |
| AS12779 | IT.Gate S.p.A. | Unclassified | IPv4 | 11 |
| AS20766 | Association "Gitoyen" | Unclassified | IPv4 | 11 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 11 |
Transit
Downstream networks
Networks for which AS50628 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS16509 | Amazon.com, Inc. | Hosting | IPv4 IPv6 | 4,725 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 IPv6 | 1,888 |
| AS714 | Apple Inc. | Hosting | IPv4 IPv6 | 1,688 |
| AS8075 | Microsoft Corporation | Hosting | IPv4 IPv6 | 1,305 |
| AS15169 | Google LLC | Hosting | IPv4 IPv6 | 1,070 |
| AS12322 | Free SAS | Residential | IPv4 IPv6 | 1,065 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 1,031 |
| AS16276 | OVH SAS | Hosting | IPv4 IPv6 | 703 |
| AS47583 | Hostinger International Limited | Hosting | IPv4 IPv6 | 512 |
| AS8560 | IONOS SE | Hosting | IPv4 IPv6 | 482 |
Adjacency
Adjacent networks
Every AS seen directly next to AS50628 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 170,197 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 141,608 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 102,449 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 13,728 |
| AS23764 | CTGNet | Unclassified | IPv4 IPv6 | 12,920 |
| AS39386 | Saudi Telecom Company JSC | Unclassified | IPv4 IPv6 | 12,001 |
| AS9002 | RETN Limited | Unclassified | IPv6 | 8,714 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 IPv6 | 8,349 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 7,971 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 | 7,474 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-21 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.