Observed topology
AS31261 GARS-AS PJSC MegaFon
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS31261: 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 |
|---|---|---|---|---|
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 2,041 |
Transit
Downstream networks
Networks for which AS31261 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS48197 | UNISTREAM COMMERCIAL BANK (JSC) | Unclassified | IPv4 | 177 |
| AS203203 | Limited Liability Company "RTS-tender" | Unclassified | IPv4 | 116 |
| AS202344 | LLC Basalt Svobodnoe Programnoe Obespechenie | Unclassified | IPv4 IPv6 | 94 |
| AS212491 | Continent Express JSC | Unclassified | IPv4 | 49 |
| AS60186 | Eurasian Development Bank | Unclassified | IPv4 | 42 |
| AS34121 | RUSAL MANAGEMENT JSC | Unclassified | IPv4 IPv6 | 40 |
| AS212764 | Public Joint Stock Company "Research and production corporation "United Wagon Company" | Unclassified | IPv4 | 34 |
| AS197379 | INVITRO-Information technology LLC | Unclassified | IPv4 | 33 |
| AS213133 | Corporate Networking Academy ANO | Unclassified | IPv4 | 24 |
| AS44900 | AO NIP "INFORMZASCHITA" | Unclassified | IPv4 | 15 |
Adjacency
Adjacent networks
Every AS seen directly next to AS31261 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 2,758 |
| AS48197 | UNISTREAM COMMERCIAL BANK (JSC) | Unclassified | IPv4 | 177 |
| AS203203 | Limited Liability Company "RTS-tender" | Unclassified | IPv4 | 116 |
| AS202344 | LLC Basalt Svobodnoe Programnoe Obespechenie | Unclassified | IPv4 IPv6 | 94 |
| AS212491 | Continent Express JSC | Unclassified | IPv4 | 49 |
| AS60186 | Eurasian Development Bank | Unclassified | IPv4 | 42 |
| AS34121 | RUSAL MANAGEMENT JSC | Unclassified | IPv4 IPv6 | 40 |
| AS212764 | Public Joint Stock Company "Research and production corporation "United Wagon Company" | Unclassified | IPv4 | 34 |
| AS197379 | INVITRO-Information technology LLC | Unclassified | IPv4 | 33 |
| AS213133 | Corporate Networking Academy ANO | Unclassified | IPv4 | 24 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M 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.