Observed topology
AS8369 INTERSVYAZ-AS Intersvyaz-2 JSC
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS8369: 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,267 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 | 710 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 606 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 338 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 212 |
| AS43298 | Storm Networks LLC | Unclassified | IPv4 | 61 |
| AS50384 | iHome LLC | Unclassified | IPv4 | 56 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 48 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 26 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 24 |
Transit
Downstream networks
Networks for which AS8369 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS198683 | "Sistemy Papilon" Ltd. | Unclassified | IPv4 | 63 |
| AS198856 | Valmaks LLC | Unclassified | IPv4 | 63 |
| AS199153 | PSF Maximum LLC | Unclassified | IPv4 | 63 |
| AS202800 | TechnoKom Ltd | Unclassified | IPv4 | 63 |
| AS207935 | INSI Steal Constructions LLC | Unclassified | IPv4 | 63 |
| AS204713 | URAL CONSULTING COMPANY LTD | Unclassified | IPv4 | 51 |
| AS47842 | JSC "Teplopribor" | Unclassified | IPv4 | 48 |
| AS57629 | LLC IVI.RU | Hosting | IPv6 | 25 |
Adjacency
Adjacent networks
Every AS seen directly next to AS8369 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 1,468 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 | 752 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 691 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 352 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 267 |
| AS198683 | "Sistemy Papilon" Ltd. | Unclassified | IPv4 | 63 |
| AS198856 | Valmaks LLC | Unclassified | IPv4 | 63 |
| AS199153 | PSF Maximum LLC | Unclassified | IPv4 | 63 |
| AS202800 | TechnoKom Ltd | Unclassified | IPv4 | 63 |
| AS207935 | INSI Steal Constructions LLC | Unclassified | IPv4 | 63 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.