Observed topology
AS50509 TRANSROUTE
Unclassified DROP-listed space RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS50509: 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 | 206 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 34 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 29 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 13 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 5 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 4 |
| AS58057 | Securebit AG | Unclassified | IPv4 | 4 |
| AS202365 | Omer GOLGELI | Unclassified | IPv4 | 4 |
Transit
Downstream networks
Networks for which AS50509 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS34665 | Petersburg Internet Network ltd. | Hosting | IPv4 IPv6 | 10,871 |
| AS48347 | JSC Mediasoft ekspert | Unclassified | IPv4 IPv6 | 3,619 |
| AS35048 | Biterika Group LLC | Hosting | IPv4 | 2,697 |
| AS198610 | Beget LLC | Unclassified | IPv4 | 2,201 |
| AS9123 | JSC "TIMEWEB" | Hosting | IPv4 | 1,982 |
| AS48128 | Obyedinyonniye Lokalniye Seti Ltd. | Unclassified | IPv4 | 1,763 |
| AS8595 | OOO WestCall Ltd. | Unclassified | IPv4 IPv6 | 1,709 |
| AS44050 | Petersburg Internet Network ltd. | Residential | IPv4 IPv6 | 1,598 |
| AS20985 | ArtX LLC | Residential | IPv4 | 899 |
| AS216368 | Petersburg Internet Network ltd. | Unclassified | IPv4 IPv6 | 826 |
Adjacency
Adjacent networks
Every AS seen directly next to AS50509 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 48,225 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 13,108 |
| AS34665 | Petersburg Internet Network ltd. | Hosting | IPv4 IPv6 | 10,871 |
| AS39153 | JOINT-STOCK COMPANY "TELEPORT TELECOM" | Unclassified | IPv4 | 8,658 |
| AS48347 | JSC Mediasoft ekspert | Unclassified | IPv4 IPv6 | 6,118 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 4,695 |
| AS8595 | OOO WestCall Ltd. | Unclassified | IPv4 IPv6 | 3,807 |
| AS35048 | Biterika Group LLC | Hosting | IPv4 | 3,749 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 2,794 |
| AS44050 | Petersburg Internet Network ltd. | Residential | IPv4 IPv6 | 2,540 |
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.