Observed topology
AS50477 SV-EN-AS Svyaz-Energo Ltd.
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS50477: 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 |
|---|---|---|---|---|
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 555 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 417 |
| AS58067 | JOINT-STOCK COMPANY "MOSCOW ENERGY COMMUNICATION NODE" | Unclassified | IPv4 IPv6 | 359 |
| AS8359 | MTS PJSC | Mobile | IPv4 IPv6 | 253 |
| AS60388 | JSC "Oil Transportation and Production Telecommunications" | Residential | IPv4 | 88 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 78 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 14 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 13 |
| AS44507 | JSC Kostroma Municipal Telephone Network | Unclassified | IPv4 | 3 |
Transit
Downstream networks
Networks for which AS50477 was observed as the last hop before the origin, meaning it appears to provide them transit.
Adjacency
Adjacent networks
Every AS seen directly next to AS50477 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 1,299 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 921 |
| AS197298 | Multifunctional Telecommunications Systems LTD | Unclassified | IPv4 | 821 |
| AS58067 | JOINT-STOCK COMPANY "MOSCOW ENERGY COMMUNICATION NODE" | Unclassified | IPv4 IPv6 | 448 |
| AS44507 | JSC Kostroma Municipal Telephone Network | Unclassified | IPv4 | 430 |
| AS8359 | MTS PJSC | Mobile | IPv4 IPv6 | 253 |
| AS60388 | JSC "Oil Transportation and Production Telecommunications" | Residential | IPv4 | 138 |
| AS205062 | LightPort Ltd | Unclassified | IPv4 | 124 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 78 |
| AS42551 | TALTEL LLC | Unclassified | IPv4 | 15 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-10 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 71.97M 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.