Skip to content

Autonomous System

AS3399(SE)

Last fetched

AS3399 is an Autonomous System registered in SE. As of Tue, 21 Jul 2026 09:17:20 GMT, it announces 29 routed IP prefixes and peers with 57 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS3399Routing diversity7.4/10Peering density7.0/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/3399

Routing footprint

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

Peering ecosystem

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

Peer ASNOperatorCountry
AS1103NL
AS174COGENT-174 - Cogent Communications, LLCUS
AS1764AT
AS202448CY
AS203861GB
AS204092FR
AS204179SE
AS204615SC
AS20473AS-VULTR - The Constant Company, LLCUS
AS206075DE
AS206296SE
AS20766FR
AS208453SE
AS209625CY
AS209659SE
AS210083BZ
AS210648SE
AS211927SE
AS21227SE
AS213113SE
AS213540SE
AS214379UA
AS214503SE
AS214640SE
AS21485SE
AS215467EE
AS215551GB
AS24482SG
AS24668SE
AS29169FR
AS31561FR
AS3257US
AS35661FR
AS38945SE
AS39889SE
AS41281GB
AS41564GB
AS41634SE
AS42237GB
AS42675SE
AS42708SE
AS44394SE
AS50304NO
AS50629DE
AS50989SE
AS51040SE
AS51546SE
AS51815SE
AS52177SE
AS5405DE
AS5511FR
AS56414SE
AS59750SE
AS62020SE
AS63473HOSTHATCH - HostHatch, LLCUS
AS6939HURRICANE - Hurricane Electric LLCUS
AS918SE

Blast radius

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

Threat posture

Related pages

Pivot deeper into the graph from AS3399.

Cypher and MCP

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

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