Skip to content

Autonomous System

AS41009 — VIZITNETUA-AS - Oleksandr Melnyk(UA)

Last fetched

AS41009 is an Autonomous System operated by VIZITNETUA-AS - Oleksandr Melnyk and registered in UA. As of Wed, 05 Aug 2026 18:56:49 GMT, it announces 8 routed IP prefixes and peers with 14 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS41009Routing diversity4.8/10Peering density4.7/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/41009

Routing footprint

AS41009 announces 8 distinct routed prefixes. The 8-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
AS1299TWELVE99 - Arelion Sweden ABSE
AS201094gmhost - Mulgin Alexander SergeevichUA
AS205127EURO-NET-AS - PP "Euronet"UA
AS210555D2CLOUD-ZA-AS - D2CLOUD NETWORK SERVICES (PTY) LTDZA
AS211947KREMEN-IX - PP Vizit-ServiceUA
AS29632NASSIST-AS - Netassist International EOODBG
AS35297DATALINE-AS - Dataline LLCUA
AS41229LIKONET-AS - Lushchan Evgenij IvanovichUA
AS43380DTEL-IX-PUBLIC-AS - Digital Telecom IX LLCUA
AS43744ORIONCITY-AS - Orion City LLCUA
AS50576FREEEWAY-PLUS-UA - FREEWAY Plus LLCUA
AS57197SOYUZTELECOM-AS - Shaporenko Yuri NikolaevichUA
AS6939HURRICANE - Hurricane Electric LLCUS
AS9002RETN-AS - RETN LimitedGB

Blast radius

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

Threat posture

Related pages

Pivot deeper into the graph from AS41009.

Cypher and MCP

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

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