Observed topology
AS29226 MASTERTEL-AS Moscow, Russia
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS29226: 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 | 628 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 414 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 222 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 193 |
| AS29076 | Citytelecom LLC | Hosting | IPv4 IPv6 | 160 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 155 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 133 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 128 |
| AS47122 | CYBERFIRST LLC | Unclassified | IPv4 | 60 |
| AS59692 | IQWeb FZ-LLC | Unclassified | IPv4 | 56 |
Transit
Downstream networks
Networks for which AS29226 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS211183 | AdminVPS OOO | Unclassified | IPv4 | 4,167 |
| AS47156 | Malnet LTD. | Residential | IPv4 | 531 |
| AS43362 | Hosting Ltd | Unclassified | IPv4 | 480 |
| AS48219 | 3DATA LLC | Unclassified | IPv4 | 326 |
| AS62010 | 3DATA LLC | Unclassified | IPv4 | 320 |
| AS48018 | Fornex Hosting S.L. | Unclassified | IPv4 | 307 |
| AS200107 | Kaspersky Lab Switzerland GmbH | Unclassified | IPv4 IPv6 | 289 |
| AS215314 | Helou LLC | Unclassified | IPv4 | 283 |
| AS24774 | 3DATA LLC | Unclassified | IPv4 | 236 |
| AS51076 | LNTech LLC | Unclassified | IPv4 | 183 |
Adjacency
Adjacent networks
Every AS seen directly next to AS29226 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 4,495 |
| AS211183 | AdminVPS OOO | Unclassified | IPv4 | 4,167 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 2,830 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,636 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 1,308 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 1,299 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 1,058 |
| AS29076 | Citytelecom LLC | Hosting | IPv4 IPv6 | 717 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 706 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 IPv6 | 639 |
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.