Observed topology
AS49505 SELECTEL JSC Selectel
Hosting DROP-listed space RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS49505: 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 |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 14,587 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 6,989 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 6,661 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 3,117 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 2,058 |
| AS8359 | MTS PJSC | Mobile | IPv4 | 2,022 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 1,563 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 1,313 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 668 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 657 |
Transit
Downstream networks
Networks for which AS49505 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS62300 | Address Limited | Unclassified | IPv4 | 364 |
| AS200487 | OOO VPS | Unclassified | IPv4 IPv6 | 243 |
| AS199851 | Adam Muratovich Tutaev | Unclassified | IPv4 | 178 |
| AS214294 | NOOB RP LTD | Unclassified | IPv4 IPv6 | 130 |
| AS204343 | Compubyte Limited | Unclassified | IPv4 | 120 |
| AS61087 | DGTL TECH UK LLP | Unclassified | IPv4 IPv6 | 98 |
| AS20611 | UK PS Group Ltd | Unclassified | IPv4 | 60 |
| AS200172 | Luna LLC | Unclassified | IPv4 | 60 |
| AS215745 | Vadim Salikhov | Unclassified | IPv4 | 59 |
| AS400992 | ZhouyiSat Communications | Unclassified | IPv4 | 58 |
Adjacency
Adjacent networks
Every AS seen directly next to AS49505 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 14,616 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 7,215 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 7,036 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 3,314 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 2,178 |
| AS8359 | MTS PJSC | Mobile | IPv4 | 2,086 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 1,789 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 1,332 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 690 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 675 |
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.