Skip to content

Autonomous System

AS28890 — INSYS-AS - INSYS LLC(RU)

Last fetched

AS28890 is an Autonomous System operated by INSYS-AS - INSYS LLC and registered in RU. As of Tue, 11 Aug 2026 19:39:41 GMT, it announces 27 routed IP prefixes and peers with 16 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS28890Routing diversity7.2/10Peering density4.9/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/28890

Routing footprint

AS28890 announces 27 distinct routed prefixes. The 25-prefix sample below links to per-prefix pages with full conflict and reverse-DNS detail.

Peering ecosystem

16 distinct peers via BGP. The first 16 are listed below.

Peer ASNOperatorCountry
AS12389ROSTELECOM-AS - PJSC RostelecomRU
AS199120Sinara-Group-AS - AO Sinara GroupRU
AS205194info-line - LLC "INFORMATION LINES"RU
AS209307CONVEX-EKB - LLC Cifrovie Seti UralaRU
AS31133MF-MGSM-AS - PJSC MegaFonRU
AS3216SOVAM-AS - PJSC "Vimpelcom"RU
AS34869EKANET-AS - INSYS LLCRU
AS41082URALTRANSCOM-AS - Company Uraltranskom Ltd.RU
AS41578ERC-AS - ERC LLCRU
AS42776ITHANDS - I T Hands LLCRU
AS44528PKF-AZIMUT-AS - INSYS LLCRU
AS51883PUMORI-AS - Pumori-Telecom LtdRU
AS57200ASMOIDOKUMENTI - "MoiDokumenti.ru" LLC.RU
AS59495ULKM-AS - ULKM-ASRU
AS6939HURRICANE - Hurricane Electric LLCUS
AS9002RETN-AS - RETN LimitedGB

Blast radius

Count of dependent hostnames if AS28890 disappeared from the routing table.

1,006 hostnames depend on this network.Exact count across all 27 announced prefixes. Snapshot Sat, 25 Jul 2026 16:00:42 GMT.

MOAS / hijack watch

Prefixes routed by AS28890 that another Autonomous System also announces. A non-empty list is one of the strongest BGP-hijack signals available without active probes.

No active MOAS conflicts. Every prefix announced by AS28890 is unique to AS28890 in the current routing snapshot.

Threat posture

Related pages

Pivot deeper into the graph from AS28890.

Cypher and MCP

Reproduce the headline metric directly against graph.whisper.security:

MATCH (a:ASN {name: "AS28890"})-[:HAS_NAME]->(n:ASN_NAME)
OPTIONAL MATCH (a)-[:HAS_COUNTRY]->(c:COUNTRY)
RETURN a.name AS asn, n.name AS operator, c.name AS country

Or query Whisper from your own LLM workflow via the Whisper MCP server.