Observed topology
AS34879 CCT-AS NGENIX
Hosting RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS34879: 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 | 3,715 |
| AS8359 | MTS PJSC | Mobile | IPv4 | 670 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 400 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 186 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 | 167 |
| AS49800 | GNC-Alfa CJSC | Residential | IPv4 | 120 |
| AS8402 | PJSC "Vimpelcom" | Residential | IPv4 | 88 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 83 |
| AS21299 | Kar-Tel LLC | Unclassified | IPv4 | 65 |
| AS208407 | LLC BYCOM SYSTEMS | Unclassified | IPv4 | 65 |
Transit
Downstream networks
Networks for which AS34879 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS204878 | OOO "Sovremennye setevye tekhnologii" | Unclassified | IPv4 | 120 |
Adjacency
Adjacent networks
Every AS seen directly next to AS34879 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 3,815 |
| AS8359 | MTS PJSC | Mobile | IPv4 | 686 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 400 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 186 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 | 167 |
| AS49800 | GNC-Alfa CJSC | Residential | IPv4 | 120 |
| AS204878 | OOO "Sovremennye setevye tekhnologii" | Unclassified | IPv4 | 120 |
| AS8402 | PJSC "Vimpelcom" | Residential | IPv4 | 88 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 83 |
| AS21299 | Kar-Tel LLC | Unclassified | IPv4 | 65 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-15 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.09M 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.