Skip to content

Autonomous System

AS200845 — AVATEL-AS AVATEL TELECOM SA(ES)

Last fetched

AS200845 is an Autonomous System operated by AVATEL-AS AVATEL TELECOM SA and registered in ES. As of Thu, 21 May 2026 15:16:48 GMT, it announces 464 routed IP prefixes and peers with 21 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS200845Routing diversity10.0/10Peering density5.4/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/200845

Routing footprint

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

Peering ecosystem

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

Peer ASNOperatorCountry
AS174COGENT-174 - Cogent Communications, LLCUS
AS213138ALFANETWORKES
AS212052ASNETEXPERIENCEES
AS206451GPONLINEAES
AS203936MismeNet TelecomunicacionesES
AS200290AUSTRALTELES
AS56571HTELECOMES
AS51152VALMESA-ASES
AS49353AS-JSANSES
AS48362TKSWF-ASAT
AS37721Virtual-Technologies-Solutions-SABF
AS34549MEER-AS meerfarbig GmbH & Co. KGDE
AS33891CORE-BACKBONE CORE-BACKBONE GMBH GLOBAL NETWORKDE
AS29632NASSIST-ASBG
AS29390CTU-ASBG
AS16030ALTECOMES
AS9002RETN-ASGB
AS8218NEO-ASN Zayo EuropeFR
AS6939HURRICANE - Hurricane Electric LLCUS
AS3257GTT-BACKBONE GTTUS
AS1299TWELVE99 Arelion, fka Telia CarrierSE

Blast radius

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

Threat posture

Related pages

Pivot deeper into the graph from AS200845.

Cypher and MCP

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

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