Observed topology
AS57753 Radist-AS Radist LTD
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS57753: 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 |
|---|---|---|---|---|
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 170 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 | 60 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 52 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 42 |
| AS24482 | SG.GS | Hosting | IPv4 | 6 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 6 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 6 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 6 |
| AS56655 | Gigahost AS | Unclassified | IPv4 | 6 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 6 |
Transit
Downstream networks
Networks for which AS57753 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS200613 | Imeretinskay Riviera LLC | Unclassified | IPv4 | 177 |
Adjacency
Adjacent networks
Every AS seen directly next to AS57753 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 245 |
| AS200613 | Imeretinskay Riviera LLC | Unclassified | IPv4 | 177 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 | 96 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 91 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 63 |
| AS24482 | SG.GS | Hosting | IPv4 | 9 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 9 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 6 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 6 |
| AS56655 | Gigahost AS | Unclassified | IPv4 | 6 |
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.