Autonomous System
AS577
Last fetched
AS577 is operated by BACOM - Bell Canada, registered in CA, and announces 16,187 prefixes to 271 BGP neighbours. AS577 has a reputation score of 11.0 (NEUTRAL); 745 of its 7,029,504 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 16,187
- BGP neighbours
- 271
- RPKI ROAs
- 211
- MOAS conflicts
- 2
- CAIDA AS-rank
- 131
- Customer-cone ASNs
- 449
- Facilities
- 32
- Internet exchanges
- 5
- Customer degree
- 256
- Peer degree
- 58
- Provider degree
- 6
- 24.142.116.0/24
- 44.31.12.0/23
- 44.31.14.0/24
- 47.54.2.0/24
- 47.54.3.0/24
- 47.54.20.0/24
- 47.54.21.0/24
- 47.54.22.0/24
- 47.54.23.0/24
- 47.54.72.0/24
- 47.54.73.0/24
- 47.54.74.0/24
- 47.54.75.0/24
- 47.54.88.0/24
- 47.54.89.0/24
- 47.54.90.0/24
- 47.54.91.0/24
- 47.54.92.0/24
- 47.54.93.0/24
- 47.54.94.0/24
- 47.54.95.0/24
- 47.54.96.0/24
- 47.54.97.0/24
- 47.54.98.0/24
- 47.54.99.0/24
Routing posture
- Hijack posture score
- 0.03
- Route leaks
- 1
Leak types observed: TYPE2_LATERAL_PEER_TO_PEER.
Infrastructure presence
Internet exchanges (5 total)
Facilities (32 total)
- Equinix DC1-DC15,DC21-DC22 - Ashburn
- Equinix CH1/CH2/CH4 - Chicago
- Equinix NY1 - New York, Newark
- Digital Realty NYC (60 Hudson)
- Digital Realty NYC (111 8th Ave)
- Equinix NY2/NY4/NY5/NY6 - New York, Secaucus
- Equinix NY9 - New York, 111 8th Avenue
- Digital Realty Seattle SEA10
- Equinix SE2/SE3 - Seattle
- 165 Halsey Meet-Me Room
- KOMO Plaza Seattle (Formerly Fisher Plaza)
- Digital Realty CHI (350 E Cermak)
- Equinix NY7 - New York, North Bergen
- Intergate West / Digital.forest / Fortress
- CoreSite - New York (NY1)
- Equinix CU1/CU2/CU3/CU4 - Culpeper
- Telehouse - Teleport Center (New York)
- Cologix MIN1
- Equinix CH3 - Elk Grove
- Telehouse - New York Chelsea
- Cologix MIN2
- Centersquare Seattle (SEA1-B)
- H5 Data Centers Seattle
- Cologix MIN3
- Cologix MIN4
Route origin authorizations
A sample of 10 of this network’s 211 ROAs.
- 104.88.156.0/22 · max length /22
- 104.98.196.0/22 · max length /22
- 134.41.0.0/16 · max length /24
- 139.142.0.0/16 · max length /24
- 142.112.0.0/16 · max length /24
- 142.113.0.0/16 · max length /24
- 142.114.0.0/16 · max length /24
- 142.115.0.0/16 · max length /24
- 142.116.0.0/16 · max length /24
- 142.117.0.0/16 · max length /24
Upstreams
The networks that most often share an observed BGP path with AS577.
Blast radius
- Announced IPv4 addresses
- 7,029,504
- Threat-listed addresses
- 745
- Threat density
- 0.0106 %
- Routed prefixes
- 16,117
How much of the internet this network is responsible for, and how much of that address space currently appears on a threat feed. Coverage: computed.
Peering ecosystem
A sample of 25 of this network’s 271 BGP neighbours.
- COGENT-174 - Cogent Communications, LLC · AS174
- UUNET - Verizon Business · AS701
- APPLE-ENGINEERING - Apple Inc. · AS714
- SASKTEL - Saskatchewan Telecommunications · AS803
- ROGERS-COMMUNICATIONS - Rogers Communications Canada Inc. · AS812
- ASN852 - TELUS Communications Inc. · AS852
- CANET-ASN-4 - Bell Canada · AS855
- CW - IDDQD-AS · AS1273
- TWELVE99 - Arelion Sweden AB · AS1299
- EBOX - EBOX · AS1403
- TBCDSB - TBCDSB · AS1604
- HOSTING - Vertisoft · AS1824
- IIJ - Internet Initiative Japan Inc. · AS2497
- KDDI - KDDI CORPORATION · AS2516
- DIGICOMTECH - Digicom · AS2568
- AS2579 - Nokia of America Corporation · AS2579
- CDAGOVN - Shared Services Canada · AS2675
- NTT-DATA-2914 - NTT America, Inc. · AS2914
- GTT-BACKBONE - GTT Communications Inc. · AS3257
- SWISSCOM - Swisscom (Schweiz) AG · AS3303
- LEVEL3 - Level 3 Parent, LLC · AS3356
- SMH-ASN - St. Michael's Hospital · AS3411
- PCCWG-APAC-HK - PCCW Global (HK) Ltd. · AS3491
- WORLDLINX - WorldLinx Telecommunications, Inc. · AS3804
- WORLDLINX-2 - WorldLinx Telecommunications, Inc. · AS3848
MOAS / hijack watch
2 announced prefixes conflict with AS577 — another network announces the same address space. A sample:
Reputation
11.0reputation score (NEUTRAL)
AS577 (BACOM - Bell Canada, CA) has a reputation score of 68.0 (NEUTRAL).
- Threat density
- 67.8/100
- Graph metrics
- 90.0/100
- Historical behaviour
- 75.0/100
- Prefix age
- 20.0/100
These are reputation signals about the network as a whole, not a threat-feed verdict about a specific address.
Registration
- Registered to
- Bell Canada
- RIR
- ARIN
- Registered
- Wed, 03 Mar 1999 05:00:00 GMT
- Abuse contact
- abuse@bellnexxia.net
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS577 into the prefixes, peers and country it routes for.
Queries
This ASN's full card — routing footprint, peers, conflicts and RIR facts.
MATCH (a:ASN {name: $asn})
OPTIONAL MATCH (a)-[:HAS_NAME]->(an:ASN_NAME)
OPTIONAL MATCH (a)-[:HAS_COUNTRY]->(co:COUNTRY)
OPTIONAL MATCH (a)-[:REGISTERED_BY]->(org:ORGANIZATION)
WITH a,
collect(an.name) AS operatorNames,
collect(co.name) AS countries,
collect(org.name) AS organizations
OPTIONAL MATCH (a)-[:ROUTES]->(prefix:ANNOUNCED_PREFIX)
WITH a, operatorNames, countries, organizations,
collect(prefix.name)[0..25] AS samplePrefixes
OPTIONAL MATCH (a)-[:BGP_NEIGHBOR]-(peer:ASN)
OPTIONAL MATCH (peer)-[:HAS_NAME]->(peern:ASN_NAME)
WITH a, operatorNames, countries, organizations, samplePrefixes,
collect({asn: peer.name, operator: peern.name})[0..25] AS samplePeers
OPTIONAL MATCH (a)<-[:CONFLICTS_WITH]-(conflict:ANNOUNCED_PREFIX)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers,
collect(conflict.name)[0..25] AS sampleConflicts
OPTIONAL MATCH (a)-[:HAS_SIGNAL]->(sig:THREAT_SIGNAL_TYPE)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts,
collect(DISTINCT sig.name) AS signals
OPTIONAL MATCH (a)-[:IX_MEMBER]->(ix:INTERNET_EXCHANGE)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts, signals,
collect({id: ix.id, name: ix.name})[0..25] AS sampleExchanges
OPTIONAL MATCH (a)-[:AS_PRESENT_AT]->(fac:FACILITY)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts, signals, sampleExchanges,
collect({id: fac.id, name: fac.name})[0..25] AS sampleFacilities
OPTIONAL MATCH (roa:ROA)-[:ROA_AUTHORIZES_ORIGIN]->(a)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts, signals, sampleExchanges, sampleFacilities,
collect({prefix: roa.prefix, maxLength: roa.maxLength})[0..10] AS sampleRoas
CALL { WITH a MATCH (a)-[:ROUTES]->(p:ANNOUNCED_PREFIX) RETURN count(p) AS prefixCount }
CALL { WITH a MATCH (a)-[:BGP_NEIGHBOR]-(n:ASN) RETURN count(n) AS peerCount }
CALL { WITH a MATCH (a)<-[:CONFLICTS_WITH]-(c:ANNOUNCED_PREFIX) RETURN count(c) AS conflictCount }
CALL { WITH a MATCH (a)-[:ROA_AUTHORIZES_ORIGIN]-(r:ROA) RETURN count(r) AS roaCount }
CALL { WITH a MATCH (a)-[:AS_PRESENT_AT]->(f:FACILITY) RETURN count(f) AS facilityCount }
CALL { WITH a MATCH (a)-[:IX_MEMBER]->(x:INTERNET_EXCHANGE) RETURN count(x) AS ixpCount }
RETURN a.name AS name,
a.rir AS rir,
a.orgName AS orgName,
a.asRank AS asRank,
a.coneAsns AS coneAsns,
a.conePrefixes AS conePrefixes,
a.coneAddresses AS coneAddresses,
a.registrationDate AS registrationDate,
a.reputationScore AS reputationScore,
a.reputationCategory AS reputationCategory,
a.overallThreatLevel AS overallThreatLevel,
a.abuseEmail AS abuseEmail,
a.hijackPostureScore AS hijackPostureScore,
a.hijackOriginMismatchCount AS hijackOriginMismatchCount,
a.routeLeakCount AS routeLeakCount,
a.routeLeakTypes AS routeLeakTypes,
a.degreeCustomer AS degreeCustomer,
a.degreePeer AS degreePeer,
a.degreeProvider AS degreeProvider,
operatorNames, countries, organizations,
samplePrefixes, samplePeers, sampleConflicts,
signals, sampleExchanges, sampleFacilities, sampleRoas,
prefixCount, peerCount, conflictCount, roaCount, facilityCount, ixpCountRun yourself →The five networks that most often share this ASN's observed BGP paths.
MATCH (a:ASN {name: $asn})<-[:BGP_PATH]-(b:BGP_PATH_OBSERVATION)
WITH b LIMIT 200
MATCH (b)-[:BGP_PATH]->(up:ASN)
WHERE up.name <> $asn
WITH up.name AS asn, count(*) AS observations
ORDER BY observations DESC
LIMIT 5
RETURN asn, observationsRun yourself →Or query Whisper from your own LLM workflow via the Whisper MCP server.