Observed topology
AS2854 ROSPRINT-AS LLC Orange Business Services
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS2854: 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 |
|---|---|---|---|---|
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 470 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 347 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 260 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 152 |
| AS8359 | MTS PJSC | Mobile | IPv4 IPv6 | 150 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 115 |
| AS25478 | iHome LLC | Unclassified | IPv4 | 62 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 45 |
| AS50384 | iHome LLC | Unclassified | IPv4 IPv6 | 37 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 35 |
Transit
Downstream networks
Networks for which AS2854 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS197986 | PJSC "PIPE METALLURGICAL COMPANY" | Unclassified | IPv4 | 177 |
| AS49675 | SKB Kontur Production JSC | Unclassified | IPv4 IPv6 | 129 |
| AS215983 | LLC "LIPT Soft" | Unclassified | IPv4 | 116 |
| AS50038 | Joint Stock Company "Sirena-Travel" | Unclassified | IPv4 | 95 |
| AS41983 | Kaspersky Lab Switzerland GmbH | Unclassified | IPv4 | 82 |
| AS59792 | Microfinance company Bystrodengi LLC | Unclassified | IPv4 | 81 |
| AS60186 | Eurasian Development Bank | Unclassified | IPv4 | 80 |
| AS41187 | National system of payment cards Joint-stock Society | Unclassified | IPv4 | 73 |
| AS15632 | JSC "Alfa-Bank" | Unclassified | IPv4 IPv6 | 70 |
| AS15707 | Open Joint Stock Company INGOSSTRAKH Insurance Company | Unclassified | IPv4 | 67 |
Adjacency
Adjacent networks
Every AS seen directly next to AS2854 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 1,225 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 839 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 560 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 418 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 356 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 314 |
| AS197986 | PJSC "PIPE METALLURGICAL COMPANY" | Unclassified | IPv4 | 177 |
| AS49675 | SKB Kontur Production JSC | Unclassified | IPv4 IPv6 | 157 |
| AS50038 | Joint Stock Company "Sirena-Travel" | Unclassified | IPv4 | 156 |
| AS8359 | MTS PJSC | Mobile | IPv4 IPv6 | 150 |
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.