Autonomous system detail

AS602

Not announced

Operated by BACOM3-AS - Bell Canada.

Summary

// analyst note
Dormant/legacy Bell Canada ASN. WHOIS/RDAP resolves cleanly to Bell Canada, but Bell's actively peered backbone runs under the separate ASN AS577, not AS602. Routing sources (RIPEstat, CAIDA, bgp.he.net, bgp.tools) agree on zero announcements, zero peers, zero cone.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-16; not on the current Spamhaus ASN-DROP list.
IPv4 prefixes
0
~0 addresses
IPv6 prefixes
0
Peer networks
0
0 up · 0 down
IANA block
1-1876
Assigned by ARIN
[ 01 ] — Context

About this ASN.

Updated  ·  Confidence: High

AS602 is a legacy autonomous system number registered under ARIN to Bell Canada, the country's largest national telecommunications carrier (fibre, wireless, and IP/carrier backbone infrastructure), and a subsidiary of BCE Inc. The ARIN WHOIS/RDAP ASName for the block is BACOM3-AS, consistent with it being one of several distinct ASNs Bell holds across its multi-decade network portfolio; Bell's actively peered, publicly documented backbone ASN is a separate number, AS577, which does maintain a PeeringDB network entry, while AS602 does not. The key triage fact for AS602 is that it is currently dormant in the global routing table: RIPEstat, CAIDA AS Rank, and third-party looking glasses (bgp.he.net, bgp.tools) independently agree it announces zero IPv4 and zero IPv6 prefixes, has zero observed BGP peers or upstreams, and a customer cone limited to itself. Its CAIDA AS rank of 79,459 reflects that complete routing inactivity. RPKI posture cannot be meaningfully assessed because there are no active originations to validate against a ROA. No notable public abuse signal was found for AS602 specifically as of July 2026 — it is absent from the current Spamhaus ASN-DROP list, and a 2012 Bell-network BGP route-leak incident documented on NANOG is attributed to Bell's separate ASN AS577, not AS602.

Operator
Bell Canada, a subsidiary of BCE Inc.; ARIN ASName BACOM3-AS [Confirmed] — https://rdap.arin.net/registry/autnum/602, https://www.bce.ca/about-bce/bce-overview
Country / RIR
CA, ARIN [Confirmed] — https://stat.ripe.net/AS602, https://rdap.arin.net/registry/autnum/602
Allocated
1999-03-03 (ARIN RDAP autnum top-level registration event, read from the autnum object's own events[], not a nested entity/contact record); last changed 2006-01-30 [Confirmed, cross-corroborated by two independent angles plus bgp.tools] — https://rdap.arin.net/registry/autnum/602
Org status
ARIN RDAP shows status Active, organization Bell Canada, Ottawa ON; one technical POC flagged unvalidated by ARIN since 2025-02-12 [Confirmed] — https://rdap.arin.net/registry/autnum/602
Contacts
abuse@bellnexxia.net (business), abuse@sympatico.ca (consumer), per ARIN RDAP remarks for the Bell Canada org record; abuse@bell.ca also cited by a third-party mirror [Confirmed for ARIN-listed addresses; Likely for abuse@bell.ca] — https://rdap.arin.net/registry/autnum/602, https://ipinfo.io/AS602

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-16; AS602 not present on the current Spamhaus ASN-DROP list; a 2012 Bell-network BGP route-leak incident documented on NANOG is attributed to Bell's separate ASN AS577, not AS602 [Confirmed for the AS577 attribution; Likely overall clean-record read] — https://www.spamhaus.org/drop/asndrop.txt, https://mailman.nanog.org/pipermail/nanog/2012-August/050861.html

Network & routing

Network type
Bell Canada's national carrier network; AS602/BACOM3-AS carries no distinct operator-published network-type description, and Bell's actively peered/documented backbone runs under a different ASN, AS577 [Likely] — https://rdap.arin.net/registry/autnum/602, https://www.peeringdb.com/asn/577
Size
dormant — 0 IPv4 and 0 IPv6 prefixes announced; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — https://stat.ripe.net/AS602, https://asrank.caida.org/asns/602, https://bgp.he.net/AS602, https://bgp.tools/as/602
Routing/peering
NOT announced — 0/325 RIS peers seeing it (v4), 0/321 (v6); CAIDA degree total 0 (customer 0, peer 0, provider 0); no upstreams or peers visible in any source [Confirmed]. No AS602-specific peering policy is published; Bell's separate ASN AS577 lists a restrictive PeeringDB policy (peering@bell.ca) that is NOT confirmed to apply to AS602
[Unknown for AS602 itself] — https://stat.ripe.net/AS602, https://asrank.caida.org/asns/602, https://www.peeringdb.com/asn/577
RPKI
not assessable — AS602 announces no prefixes, so there are no ROAs to validate; bgp.tools confirms no valid or invalid RPKI-originated routes [Confirmed] — https://bgp.tools/as/602
Notable usage
no operator-published statement about AS602's usage exists on Bell's own web properties; third-party observational routing data indicates the block is not currently active/originating traffic [Likely] — https://bgp.he.net/AS602
Related ASNs
AS577 (Bell Canada's actively peered, publicly documented backbone ASN) [Confirmed] — https://www.peeringdb.com/asn/577
Analyst note
Encountered as a dormant legacy Bell Canada ASN; WHOIS/RDAP resolves cleanly to Bell Canada, but Bell's actively peered backbone runs under the separate ASN AS577, not AS602. Clean, inactive block.
[ 02 ] — Announced prefixes

What this network routes.

0 prefixes total · RIPEstat data · cached, not real-time
// IPv4 prefixes0
No IPv4 prefixes announced.
// IPv6 prefixes0
No IPv6 prefixes announced.
[ 03 ] — Notable peers & upstreams

Who it talks to.

0 observed neighbours
Neighbour data unavailable from public BGP collectors.