Observed topology
AS49063 DTLN Data Storage Center JSC
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS49063: 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 | 4,335 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 | 1,639 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 1,001 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 | 902 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 | 653 |
| AS8359 | MTS PJSC | Mobile | IPv4 IPv6 | 573 |
| AS201706 | SERVICEPIPE LLC | Unclassified | IPv4 | 302 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 283 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 205 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 192 |
Transit
Downstream networks
Networks for which AS49063 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6761 | Invest Development LLC | Unclassified | IPv4 IPv6 | 640 |
| AS48614 | ITSOFT LLC | Unclassified | IPv4 IPv6 | 633 |
| AS61178 | Digital Transformation Plus LLC | Unclassified | IPv4 | 315 |
| AS51698 | "ActiveHost RU" LLC | Unclassified | IPv4 | 233 |
| AS199420 | OOO Fly Engeneering Group | Unclassified | IPv4 IPv6 | 224 |
| AS57212 | Mercury LLC | Unclassified | IPv4 | 189 |
| AS58084 | Newcontact ltd. | Unclassified | IPv4 | 87 |
| AS203714 | LLC Flex | Unclassified | IPv4 | 86 |
| AS40676 | Psychz Networks | Hosting | IPv6 | 66 |
| AS39697 | Borishof Holding LLC | Unclassified | IPv4 | 63 |
Adjacency
Adjacent networks
Every AS seen directly next to AS49063 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 6,057 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 | 2,062 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 | 1,476 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 1,403 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 | 1,235 |
| AS8359 | MTS PJSC | Mobile | IPv4 IPv6 | 786 |
| AS48614 | ITSOFT LLC | Unclassified | IPv4 IPv6 | 694 |
| AS6761 | Invest Development LLC | Unclassified | IPv4 IPv6 | 640 |
| AS201706 | SERVICEPIPE LLC | Unclassified | IPv4 | 468 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 365 |
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.