asn.dev

Observed topology

AS28890 INSYS-AS INSYS ISP

Residential RIPE

Upstreams 12 carry this network
Downstreams 11 this network carries
Adjacent (IPv4) 23
Adjacent (IPv6) 5
Upstream graph Who carries AS28890, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS28890 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 12

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.

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4 IPv6722
AS3216PJSC "Vimpelcom"MobileIPv4388
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6202
AS31133PJSC MegaFonMobileIPv4 IPv6108
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv668
AS50673Serverius Holding B.V.UnclassifiedIPv446
AS24482SG.GSHostingIPv4 IPv624
AS9002RETN LimitedUnclassifiedIPv423
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv423
AS37721Virtual Technologies & SolutionsResidentialIPv423

Transit

Downstream networks

All 11

Networks for which AS28890 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS41082Company Uraltranskom Ltd.UnclassifiedIPv4248
AS59495Uralskie lokomotivy LtdUnclassifiedIPv490
AS34869INSYS LLCUnclassifiedIPv463
AS42776I T Hands LLCUnclassifiedIPv463
AS44528INSYS LLCUnclassifiedIPv463
AS57200"MoiDokumenti.ru" LLC.UnclassifiedIPv463
AS51883Pumori-Telecom LtdUnclassifiedIPv462
AS41578ERC LLCUnclassifiedIPv437
AS199120AO Sinara GroupUnclassifiedIPv435
AS209666Shakhmin Alexandr SergeevichUnclassifiedIPv413

Adjacency

Adjacent networks

All 23

Every AS seen directly next to AS28890 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4 IPv61,008
AS3216PJSC "Vimpelcom"MobileIPv4598
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6270
AS41082Company Uraltranskom Ltd.UnclassifiedIPv4248
AS31133PJSC MegaFonMobileIPv4 IPv6147
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv6123
AS59495Uralskie lokomotivy LtdUnclassifiedIPv490
AS50673Serverius Holding B.V.UnclassifiedIPv472
AS34869INSYS LLCUnclassifiedIPv463
AS42776I T Hands LLCUnclassifiedIPv463

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.