Observed topology
AS196695 NETONERUS
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS196695: 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 | 1,093 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 486 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 270 |
| AS47122 | CYBERFIRST LLC | Unclassified | IPv4 | 268 |
| AS50509 | Transroute Telecom LTD | Unclassified | IPv4 IPv6 | 253 |
| AS29226 | JSC Mastertel | Unclassified | IPv4 | 213 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 40 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 IPv6 | 40 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 39 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 39 |
Transit
Downstream networks
Networks for which AS196695 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS39376 | PUBLIC JOINT-STOCK COMPANY WORLD TRADE CENTER MOSCOW | Unclassified | IPv4 | 996 |
| AS34192 | Amrox LLC | Unclassified | IPv4 | 640 |
| AS199546 | Moscomnet LLC | Unclassified | IPv4 | 132 |
| AS215457 | DCS LLC | Unclassified | IPv4 | 130 |
| AS207064 | DBS Technologies LLC | Unclassified | IPv4 | 128 |
| AS209343 | Svyaz Ltd | Unclassified | IPv4 | 125 |
| AS209684 | Action-digital LLC | Unclassified | IPv4 | 108 |
| AS42135 | AVGA-TERRA Ltd. | Unclassified | IPv4 IPv6 | 102 |
| AS207986 | LLC OZON BANK | Unclassified | IPv4 | 100 |
| AS51641 | VSK Insurance Joint Stock Company | Unclassified | IPv4 | 98 |
Adjacency
Adjacent networks
Every AS seen directly next to AS196695 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 3,242 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 1,227 |
| AS39376 | PUBLIC JOINT-STOCK COMPANY WORLD TRADE CENTER MOSCOW | Unclassified | IPv4 | 996 |
| AS50509 | Transroute Telecom LTD | Unclassified | IPv4 IPv6 | 872 |
| AS47122 | CYBERFIRST LLC | Unclassified | IPv4 | 815 |
| AS34192 | Amrox LLC | Unclassified | IPv4 | 640 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 589 |
| AS29226 | JSC Mastertel | Unclassified | IPv4 | 492 |
| AS215457 | DCS LLC | Unclassified | IPv4 | 161 |
| AS199546 | Moscomnet LLC | Unclassified | IPv4 | 144 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-29 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.36M 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.