Skip to content

Autonomous System

AS47626 — ASTIMER(RU)

Last fetched

AS47626 is an Autonomous System operated by ASTIMER and registered in RU. As of Thu, 21 May 2026 10:36:49 GMT, it announces 16 routed IP prefixes and peers with 27 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS47626Routing diversity6.1/10Peering density5.8/10MOAS conflict✓ noneThreat-feed listings—WHOIS transparency—Resolver footprint—canon.whisper.security/asn/47626

Routing footprint

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

Peering ecosystem

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

Peer ASNOperatorCountry
AS6939HURRICANE - Hurricane Electric LLCUS
AS209393DONTEL-ASRU
AS209219ASDINRU
AS208972GIBIRNET-TR
AS208720ROS-LTDRU
AS208544PAUTINA05RU
AS206649SHAMILOV-ASRU
AS203695ISP-ASRU
AS199008TVSPUTNIK-ASRU
AS197185ASTLANRU
AS60936SKANETDAG-ASRU
AS59416NEVZ-ASRU
AS58306GALACTIKA-SERVICE-ASRU
AS57766ENERGOINFORM-AS Makhachkala, Daghestan, RussiaRU
AS57562PULS-KT-ASRU
AS57531REGIONINFOCOM-ASRU
AS56655GIGAHOSTNO
AS56374NPI-TURU
AS49897ALIANSNETRU
AS45055DONTECHSVYAZRU
AS37721Virtual-Technologies-Solutions-SABF
AS34927IFOG-GMBHCH
AS31500GNM-ASAG
AS31133MF-MGSM-AS PJSC MegaFonRU
AS28917FIORD-AS IP-transit operator in EuropeLT
AS24482SGGS-AS-AP SG.GSSG
AS9002RETN-ASGB

Blast radius

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

~349 hostnames depend on this network.Sampled from 10 prefixes, snapshot Thu, 21 May 2026 10:36:49 GMT.

MOAS / hijack watch

Prefixes routed by AS47626 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 AS47626 is unique to AS47626 in the current routing snapshot.

Threat posture

Related pages

Pivot deeper into the graph from AS47626.

Cypher and MCP

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

MATCH (a:ASN {name: "AS47626"})-[: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.