Skip to content

Autonomous System

AS61010BREDBANDSFYLKET-TROMS(KG)

Last fetched

AS61010 is an Autonomous System operated by BREDBANDSFYLKET-TROMS and registered in KG. As of Thu, 21 May 2026 10:54:34 GMT, it announces 6 routed IP prefixes and peers with 18 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS61010Routing diversity4.2/10Peering density5.1/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/61010

Routing footprint

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

Peering ecosystem

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

Peer ASNOperatorCountry
AS3216SOVAM-ASRU
AS209141CMI-RUSSIARU
AS206718ASUS
AS205204NTLAB-ASKG
AS205103TELEGRAPH-ASDE
AS197000RIPE-NCC-AUTHDNS-AS Reseaux IP Europeens Network Coordination Centre RIPE NCCNL
AS61399KG-IXKG
AS51898BORNEO-BSKKG
AS47237NURTELECOM-AS-RIPEKG
AS41798TTC-AS JSC TranstelecomKZ
AS37721Virtual-Technologies-Solutions-SABF
AS34927IFOG-GMBHCH
AS25035TRANSFER-ASKG
AS12297TELECOM-ARMENIA Telecom Armenia ASAM
AS9198KAZTELECOM-ASKZ
AS9002RETN-ASGB
AS8511AS8511-AI Bishkek, KyrgyzstanKG
AS6939HURRICANE - Hurricane Electric LLCUS

Blast radius

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

~3,091 hostnames depend on this network.Sampled from 10 prefixes, snapshot Thu, 21 May 2026 10:54:34 GMT.

MOAS / hijack watch

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

Threat posture

Related pages

Pivot deeper into the graph from AS61010.

Cypher and MCP

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

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