Skip to content

Autonomous System

AS3342CIBICOM-IP-NETWORK(DK)

Last fetched

AS3342 is an Autonomous System operated by CIBICOM-IP-NETWORK and registered in DK. As of Thu, 21 May 2026 11:15:56 GMT, it announces 18 routed IP prefixes and peers with 28 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS3342Routing diversity6.4/10Peering density5.8/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/3342

Routing footprint

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

Peering ecosystem

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

Peer ASNOperatorCountry
AS1299TWELVE99 Arelion, fka Telia CarrierSE
AS216313COMPLETNET-NETDK
AS212736ASITCHDK
AS212482LIVIATEDK
AS211457MAERSKBROKERDK
AS210465AS-SACITASDK
AS210418XELLIA-ASDK
AS207355KA-NETDK
AS207316VAEKSTFONDENDK
AS207017SKYWIRE-DK
AS206464DATACONDK
AS204988TDH-NETDK
AS203595KJELDSENITDK
AS201960GORRISSEN-FEDERSPIEL-ASDK
AS201455ANYCLOUDDK
AS201078ECIT_SOLUTIONS_ASDK
AS200885DK
AS200629CLOUDIODK
AS198901ORDBOGEN-DK
AS60958INFOLINK-ASDK
AS48854TEAM-BLUE-DENMARKDK
AS48295PAYCHEXDE-FDE
AS43088HOSTCENTER-ASDK
AS31027GLOBALCONNECT-AS31027DK
AS24853DK
AS21217SAFEHOSTNET Colocation center in GenevaCH
AS3356LEVEL3 - Level 3 Parent, LLCUS
AS3292TDC TDC ASDK

Blast radius

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

~7,177 hostnames depend on this network.Sampled from 10 prefixes, snapshot Thu, 21 May 2026 11:15:56 GMT.

MOAS / hijack watch

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

Threat posture

Related pages

Pivot deeper into the graph from AS3342.

Cypher and MCP

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

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