Observed topology
AS48642 FOR-AS Russia
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS48642: 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 | 1,390 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 391 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 140 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 117 |
| AS25478 | iHome LLC | Unclassified | IPv4 | 102 |
| AS9049 | JSC "ER-Telecom Holding" | Unclassified | IPv4 | 87 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 57 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 39 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 38 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 36 |
Transit
Downstream networks
Networks for which AS48642 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS60489 | OOO "Center informational technologies" | Unclassified | IPv4 | 89 |
| AS12341 | Ural State Polzunov College | Unclassified | IPv4 | 62 |
| AS41022 | CCS LLC | Unclassified | IPv4 | 62 |
| AS43328 | TELEKOM" | Unclassified | IPv4 | 45 |
| AS204477 | UralKali PJSC | Unclassified | IPv4 | 35 |
| AS201643 | GBU SO Operator of Electronic Government | Unclassified | IPv4 | 29 |
| AS206338 | Rosseti Ural PJSC | Unclassified | IPv4 | 10 |
| AS197007 | Ural Electronics Factory Ltd. | Unclassified | IPv4 | 1 |
Adjacency
Adjacent networks
Every AS seen directly next to AS48642 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 1,585 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 391 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 176 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 151 |
| AS25478 | iHome LLC | Unclassified | IPv4 | 124 |
| AS60489 | OOO "Center informational technologies" | Unclassified | IPv4 | 89 |
| AS9049 | JSC "ER-Telecom Holding" | Unclassified | IPv4 | 88 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 67 |
| AS12341 | Ural State Polzunov College | Unclassified | IPv4 | 62 |
| AS41022 | CCS LLC | Unclassified | IPv4 | 62 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-19 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.