Observed topology
AS25513 ASN-MGTS-USPD
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS25513: 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.
Transit
Downstream networks
Networks for which AS25513 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS29285 | PJSC Moscow city telephone network | Unclassified | IPv4 | 173 |
| AS34500 | FGUP CTSPI MGA Russia | Unclassified | IPv4 | 76 |
| AS44232 | Slavyanskaya Hotel and Business Center Ltd | Unclassified | IPv4 | 63 |
| AS5548 | Federalnoe gosudarstvennoe avtonomnoe obrazovatelnoe uchrezhdenie vysshego obrazovaniya "Rossiyskiy Universitet Transporta" | Education | IPv4 | 57 |
| AS39415 | PJSC Moscow city telephone network | Unclassified | IPv4 | 57 |
| AS58071 | PEOPLES FRIENDSHIP UNIVERSITY OF RUSSIA | Unclassified | IPv4 | 57 |
| AS199093 | Moscow Polytechnic University | Unclassified | IPv4 | 57 |
| AS199502 | OOO WestCall Ltd. | Unclassified | IPv4 | 57 |
| AS56537 | JSC Centr programm loyalnosti | Unclassified | IPv4 | 37 |
| AS56619 | Safety Integrated Systems Ltd | Unclassified | IPv4 | 36 |
Adjacency
Adjacent networks
Every AS seen directly next to AS25513 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS8359 | MTS PJSC | Mobile | IPv4 IPv6 | 3,928 |
| AS29285 | PJSC Moscow city telephone network | Unclassified | IPv4 | 173 |
| AS34500 | FGUP CTSPI MGA Russia | Unclassified | IPv4 | 76 |
| AS44232 | Slavyanskaya Hotel and Business Center Ltd | Unclassified | IPv4 | 63 |
| AS5548 | Federalnoe gosudarstvennoe avtonomnoe obrazovatelnoe uchrezhdenie vysshego obrazovaniya "Rossiyskiy Universitet Transporta" | Education | IPv4 | 57 |
| AS39415 | PJSC Moscow city telephone network | Unclassified | IPv4 | 57 |
| AS58071 | PEOPLES FRIENDSHIP UNIVERSITY OF RUSSIA | Unclassified | IPv4 | 57 |
| AS199093 | Moscow Polytechnic University | Unclassified | IPv4 | 57 |
| AS199502 | OOO WestCall Ltd. | Unclassified | IPv4 | 57 |
| AS56537 | JSC Centr programm loyalnosti | Unclassified | IPv4 | 37 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-12 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.21M 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.