Observed topology
AS44597 RIPN-RU-SMR for Samara Project
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS44597: 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 | 122 |
| AS3316 | Join-stock company "Internet Exchange"MSK-IX" | Unclassified | IPv4 | 58 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 53 |
| AS60764 | Telecom Samara LLC | Unclassified | IPv4 | 22 |
| AS8985 | Join-stock company "Internet Exchange"MSK-IX" | Unclassified | IPv4 IPv6 | 3 |
Transit
Downstream networks
Networks for which AS44597 was observed as the last hop before the origin, meaning it appears to provide them transit.
Adjacency
Adjacent networks
Every AS seen directly next to AS44597 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 122 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 87 |
| AS3316 | Join-stock company "Internet Exchange"MSK-IX" | Unclassified | IPv4 | 58 |
| AS41740 | Join-stock company "Internet Exchange"MSK-IX" | Unclassified | IPv6 | 34 |
| AS60764 | Telecom Samara LLC | Unclassified | IPv4 | 31 |
| AS43832 | Join-stock company "Internet Exchange"MSK-IX" | Unclassified | IPv4 | 9 |
| AS8985 | Join-stock company "Internet Exchange"MSK-IX" | Unclassified | IPv4 IPv6 | 3 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-21 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.