Skip to content

Autonomous System

AS215730 — H2NEXUS-AS - H2NEXUS CLOUD SERVICES - FZCO(AE)

Last fetched

AS215730 is an Autonomous System operated by H2NEXUS-AS - H2NEXUS CLOUD SERVICES - FZCO and registered in AE. As of Sun, 06 Sep 2026 14:19:16 GMT, it announces 38 routed IP prefixes and peers with 14 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS215730Routing diversity7.9/10Peering density4.7/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/215730

Routing footprint

AS215730 announces 38 distinct routed prefixes. The 25-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
AS199277ug-as - Maksims DoronkinsLV
AS200823MHost-AS - MHost LLCGE
AS201988VPSPay-ASN - VPSPay Networks LTDGB
AS202226GreatFlower - Emil Vitukhnovskii trading as Great FlowerIL
AS202413PRONKIN-AS - Pronkin TimofeiEE
AS203446AS203446 - SMARTNET Germany GmbHDE
AS205563zGato - Marc GomezES
AS213702QWINS-LTD - QWINS LTDGB
AS219225IDRIS-ASN - Idris Alaudievich UmaevRU
AS219336popsuiko-AS - Olha PopsuikoIT
AS28917Fiord-AS - Fiord Networks, UABLT
AS30823AUROLOGIC - aurologic GmbHDE
AS3257GTT-BACKBONE - GTT Communications Inc.US
AS6939HURRICANE - Hurricane Electric LLCUS

Blast radius

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

18,350 hostnames depend on this network.Exact count across all 36 announced prefixes. Snapshot Thu, 09 Jul 2026 14:00:50 GMT.

MOAS / hijack watch

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

Threat posture

Related pages

Pivot deeper into the graph from AS215730.

Cypher and MCP

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

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