Skip to content

Autonomous System

AS855 — CANET-ASN-4 - Bell Canada(CA)

Last fetched

AS855 is an Autonomous System operated by CANET-ASN-4 - Bell Canada and registered in CA. As of Thu, 21 May 2026 22:58:52 GMT, it announces 783 routed IP prefixes and peers with 13 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS855Routing diversity10.0/10Peering density4.6/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/855

Routing footprint

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

Peering ecosystem

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

Peer ASNOperatorCountry
AS577BACOM - Bell CanadaCA
AS398006360-CONDOMINIUMS - 360 CondominiumsCA
AS395431TELNET1-AS-AP Telnet Technoinfra Pvt LtdCA
AS394015GRAND-MOUND-COMMUNICATIONS - GRAND MOUND COOPERATIVE TELEPHONE ASSOCIATIONCA
AS40575CVLAB-OH-AS-01 - Steege IT Services LLCCA
AS36004NOS-NOG - NOS Network Operations GroupCA
AS32747CDI - Computer Design & Integration LLCCA
AS32441LONI - Louisiana Board of RegentsLouisiana Optical Network Initiative LONICA
AS6939HURRICANE - Hurricane Electric LLCUS
AS3958AIRCANADA - Air CanadaCA
AS3257GTT-BACKBONE GTTUS
AS1299TWELVE99 Arelion, fka Telia CarrierSE
AS603EQUINIX-EC - Equinix, Inc.US

Blast radius

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

Threat posture

Related pages

Pivot deeper into the graph from AS855.

Cypher and MCP

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

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