Skip to content

Autonomous System

AS28890 — INSYS-AS INSYS ISP(RU)

Last fetched

AS28890 is an Autonomous System operated by INSYS-AS INSYS ISP and registered in RU. As of Thu, 21 May 2026 15:13:47 GMT, it announces 27 routed IP prefixes and peers with 20 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS28890Routing diversity7.2/10Peering density5.3/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

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

Peer ASNOperatorCountry
AS3216SOVAM-ASRU
AS209307CONVEX-EKBRU
AS205194INFO-LINERU
AS199120SINARA-GROUP-ASRU
AS59495ULKM-ASRU
AS57200ASMOIDOKUMENTIRU
AS51883PUMORI-ASRU
AS51507ASINTELLEKTRU
AS44528PKF-AZIMUT-ASRU
AS42776ITHANDSRU
AS41578ERC-ASRU
AS41082URALTRANSCOM-ASRU
AS37721Virtual-Technologies-Solutions-SABF
AS34927IFOG-GMBHCH
AS34869EKANET-ASRU
AS31133MF-MGSM-AS PJSC MegaFonRU
AS20485TRANSTELECOM Moscow, RussiaRU
AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRU
AS9002RETN-ASGB
AS6939HURRICANE - Hurricane Electric LLCUS

Blast radius

Approximate count of dependent hostnames if AS28890 disappeared from the routing table.

Blast radius: Computing — check back later. The precompute pipeline refreshes this panel within a few days.

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.