Observed topology
AS47122 CYBERFIRST-AS --- MASTERTEL
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS47122: 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 |
|---|---|---|---|---|
| AS31500 | Global Network Management Inc | Unclassified | IPv4 | 86 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 52 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 | 38 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 24 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 | 12 |
| AS24482 | SG.GS | Hosting | IPv4 | 4 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 4 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 | 4 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 4 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 4 |
Transit
Downstream networks
Networks for which AS47122 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS43727 | JSC KVANT-TELEKOM | Residential | IPv4 | 329 |
| AS212136 | NUBES LLC | Unclassified | IPv4 | 307 |
| AS196695 | NetOne Rus JSC | Unclassified | IPv4 | 264 |
| AS197309 | RS-Media LLC | Unclassified | IPv4 | 183 |
| AS56565 | Operator-CRPT LLC | Unclassified | IPv4 | 127 |
| AS209701 | Sberbank-factoring Ltd. | Unclassified | IPv4 | 107 |
| AS43045 | Svyaz-Holding Ltd. | Residential | IPv4 | 63 |
| AS29226 | JSC Mastertel | Unclassified | IPv4 | 60 |
| AS203891 | GKU MO "MOC IKT" | Unclassified | IPv4 | 60 |
| AS206805 | LLC "T1Cloud" | Unclassified | IPv4 | 60 |
Adjacency
Adjacent networks
Every AS seen directly next to AS47122 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS31500 | Global Network Management Inc | Unclassified | IPv4 | 921 |
| AS196695 | NetOne Rus JSC | Unclassified | IPv4 | 745 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 555 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 | 353 |
| AS43727 | JSC KVANT-TELEKOM | Residential | IPv4 | 329 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 311 |
| AS212136 | NUBES LLC | Unclassified | IPv4 | 307 |
| AS197309 | RS-Media LLC | Unclassified | IPv4 | 183 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 | 177 |
| AS56565 | Operator-CRPT LLC | Unclassified | IPv4 | 127 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-16 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.23M 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.