Skip to content

Autonomous System

AS8057 — VISIONNET - Vision Net, Inc.(US)

Last fetched

AS8057 is an Autonomous System operated by VISIONNET - Vision Net, Inc. and registered in US. As of Sun, 06 Sep 2026 18:11:04 GMT, it announces 42 routed IP prefixes and peers with 15 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS8057Routing diversity8.1/10Peering density4.8/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/8057

Routing footprint

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

Peering ecosystem

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

Peer ASNOperatorCountry
AS1378IBEL - Interbel Telephone Cooperative, Inc.US
AS174COGENT-174 - Cogent Communications, LLCUS
AS196053RC - 3 Rivers Telephone Cooperative, Inc.US
AS27022SIYEH-ASN-1 - Siyeh CorporationUS
AS3257GTT-BACKBONE - GTT Communications Inc.US
AS33339NEMONT-CELLULAR - NemontUS
AS3482MTSTGOV - State of MontanaUS
AS36046BOTC - BOTCUS
AS399079LINCTEL - Linctel Communications Inc.US
AS401920MOW-MT - Montana Outback Wireless Inc.US
AS40933TRIANGLE-COMMUNICATIONS - Triangle CommunicationsUS
AS46971FIBXTERNALIP - First Interstate BankUS
AS6081
AS6621HNS-DIRECPC - Hughes Network Systems, LLCUS
AS6939HURRICANE - Hurricane Electric LLCUS

Blast radius

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

Threat posture

Related pages

Pivot deeper into the graph from AS8057.

Cypher and MCP

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

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