Skip to content

Autonomous System

AS25447 — JM-DATA - JM-DATA GmbH(AT)

Last fetched

AS25447 is an Autonomous System operated by JM-DATA - JM-DATA GmbH and registered in AT. As of Tue, 01 Sep 2026 12:52:46 GMT, it announces 31 routed IP prefixes and peers with 12 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS25447Routing diversity7.5/10Peering density4.4/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/25447

Routing footprint

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

Peering ecosystem

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

Peer ASNOperatorCountry
AS12447KABELINE-AS - Ernst Klingler Kabelfernsehen GmbhAT
AS15935HA-VEL-LOCAL-AS - ha-vel internet s.r.o.CZ
AS174COGENT-174 - Cogent Communications, LLCUS
AS1764NEXTLAYER-AS - Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbHAT
AS35370AINET-AS - Ainet Telekommunikations-Netzwerk Betriebs GmbHAT
AS43002KTV-GARS-Klipso-GmbH-AS43002 - Klipso GmbHAT
AS48362TKSWF-AS - Stadtwerke FeldkirchAT
AS48367Franz-Dax-GmbH - Franz Dax GmbHAT
AS49163KTVAM-AS - Kabel-TV Amstetten GMBHAT
AS60517AS-CABLEVISION - Noehmer Cablevision GmbHAT
AS61109STWIMST - Stadtgemeinde/Stadtwerke ImstAT
AS6939HURRICANE - Hurricane Electric LLCUS

Blast radius

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

1,636 hostnames depend on this network.Exact count across all 31 announced prefixes. Snapshot Wed, 15 Jul 2026 16:00:53 GMT.

MOAS / hijack watch

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

Threat posture

Related pages

Pivot deeper into the graph from AS25447.

Cypher and MCP

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

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