Observed topology
AS28890 INSYS-AS INSYS ISP
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS28890: 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 | 722 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 388 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 202 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 108 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 68 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 46 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 24 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 23 |
| AS9049 | JSC "ER-Telecom Holding" | Unclassified | IPv4 | 23 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 23 |
Transit
Downstream networks
Networks for which AS28890 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS41082 | Company Uraltranskom Ltd. | Unclassified | IPv4 | 248 |
| AS59495 | Uralskie lokomotivy Ltd | Unclassified | IPv4 | 90 |
| AS34869 | INSYS LLC | Unclassified | IPv4 | 63 |
| AS42776 | I T Hands LLC | Unclassified | IPv4 | 63 |
| AS44528 | INSYS LLC | Unclassified | IPv4 | 63 |
| AS57200 | "MoiDokumenti.ru" LLC. | Unclassified | IPv4 | 63 |
| AS51883 | Pumori-Telecom Ltd | Unclassified | IPv4 | 62 |
| AS41578 | ERC LLC | Unclassified | IPv4 | 37 |
| AS199120 | AO Sinara Group | Unclassified | IPv4 | 35 |
| AS209666 | Shakhmin Alexandr Sergeevich | Unclassified | IPv4 | 13 |
Adjacency
Adjacent networks
Every AS seen directly next to AS28890 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 1,008 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 598 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 270 |
| AS41082 | Company Uraltranskom Ltd. | Unclassified | IPv4 | 248 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 147 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 123 |
| AS59495 | Uralskie lokomotivy Ltd | Unclassified | IPv4 | 90 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 72 |
| AS34869 | INSYS LLC | Unclassified | IPv4 | 63 |
| AS42776 | I T Hands LLC | Unclassified | IPv4 | 63 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-21 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.