Skip to content

Autonomous System

AS198044 — Ekomobile-AS - ECOSYSTEM Ltd(RU)

Last fetched

AS198044 is an Autonomous System operated by Ekomobile-AS - ECOSYSTEM Ltd and registered in RU. As of Sun, 06 Sep 2026 13:46:51 GMT, it announces 4 routed IP prefixes and peers with 14 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS198044Routing diversity3.5/10Peering density4.7/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/198044

Routing footprint

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

Peering ecosystem

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

Peer ASNOperatorCountry
AS208972gibirnet-tr - GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETITR
AS24482SGGS-AS-AP - SG.GSSG
AS31500GNM-AS - Global Network Management IncAG
AS34927iFog-GmbH - iFog GmbHCH
AS35598INETCOM - INETCOM CARRIER LLCRU
AS37721Virtual Technologies & Solutions - Virtual Technologies & SolutionsBF
AS49673TRUENETWORK - Truenetwork LLCRU
AS50509TRANSROUTE - Transroute Telecom LTDRU
AS50673Serverius-as - Serverius Holding B.V.NL
AS56655GIGAHOST - Gigahost ASNO
AS62255BEMYLINK - BiMajLink d.o.o.SI
AS6939HURRICANE - Hurricane Electric LLCUS
AS8218NEO-ASN - Zayo Infrastructure France SAFR
AS8447A1TELEKOM-AT - A1 Telekom Austria AGAT

Blast radius

Count of dependent hostnames if AS198044 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 AS198044 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 AS198044 is unique to AS198044 in the current routing snapshot.

Threat posture

Related pages

Pivot deeper into the graph from AS198044.

Cypher and MCP

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

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