Mobile operator · Canada
Bell ASN, MCC/MNC and IP prefixes
Bell is a mobile network operator in Canada, part of BCE Inc. It routes traffic through 2 autonomous systems (AS36522, AS577), which announced 1,802 prefixes at our last probe, and its SIMs carry MCC/MNC 302-610, 302-630.
- ASNs
- 2
- Prefixes
- 1,802
- Reviewed
- September 2026
- Country
- Canada (CA)
- Parent group
- BCE Inc.
- ASNs
- AS36522, AS577
- MCC / MNC
- 302-610, 302-630
- Network generations
- 4G LTE, 5G
- ASNs confirmed
- 2 of 2
- Announced prefixes
- 1,802 at probe on 2026-09-06
- Official site
- www.bell.ca
Autonomous systems
Mobile network codes
| MCC-MNC | MCC | MNC | Source |
|---|---|---|---|
| 302-610 | 302 | 610 | en.wikipedia.org/wiki/Mobile_network_codes_in_IT |
| 302-630 | 302 | 630 | en.wikipedia.org/wiki/Mobile_network_codes_in_IT |
About Bell
Bell is a mobile network operator in Canada and a subsidiary of BCE Inc. The registry records AS36522, registered to Bell Mobility Inc., as the ASN carrying its mobile network, alongside AS577, the Bell Canada fixed backbone. Bell's recorded MCC/MNC codes are 302-610 and 302-630, and the registry lists 4G LTE and 5G for the network.
The registry holds two ASNs for Bell. AS36522, registered as BELLMOBILITY-1 to Bell Mobility Inc., is the one documented as mobile, and at the last probe it announced 147 IPv4 prefixes and 5 IPv6 prefixes. AS577, registered as BACOM to Bell Canada, is recorded as the fixed backbone and announced 1,579 IPv4 prefixes and 71 IPv6 prefixes at the last probe. PeeringDB has a record for AS577 under the name Bell Canada Backbone, typed NSP. It holds no record for AS36522.
An address whose origin ASN is AS36522 is routed by Bell on the side of the network documented as mobile. An address originating from AS577 is routed by Bell Canada on the fixed backbone, so it is not evidence of a mobile connection. The registry maps an ASN to the operator that announces it and to a recorded role. It does not track individual addresses, so an ASN alone will not tell you which subscriber or device held one.
Research note. Bell coverage page heading: 'Coverage Map for Bell 4G LTE, 5G, 5G+ & 5G+ Advanced Networks'. AS36522 (BELL MOBILITY INC.) is announced per RIPEstat and is the mobile ASN; AS577 (BACOM) is the Bell Canada backbone. PeeringDB returned 404 (no record) for AS36522 and 429 for AS577. Candidate MNC 302-651 does not appear in either MCC/MNC table consulted and was dropped as unconfirmed; 302-630 (Aliant Mobility / Bell Aliant) is listed with status 'Unknown' in both tables - kept as a Bell-owned code but not verified operational. 302-610 is the main Bell Mobility code (LTE + 5G bands). Table also lists 302-690 (Bell, UMTS) and 302-880 (Bell/Telus/SaskTel shared) not in candidates. Parent: Wikipedia Bell Canada infobox 'Type: Subsidiary; Parent: BCE Inc.'; bce.ca pages fetched did not state the relationship explicitly. Other candidates (601, 602, 684, 831, 855, 6539, 6608, 7122, 7398, 8187, 11489, 11566, 13650, 27181, 40304, 53829, 54182, 62596) are Bell Canada fixed/legacy/regional names (MTS, Aliant, KMTS, Axia, Bell Media) and were not verified as mobile.
Check whether an IP belongs to Bell
curl -s "https://stat.ripe.net/data/prefix-overview/data.json?resource=203.0.113.9" | jq '.data.asns'whois -h whois.radb.net -- '-i origin AS36522' | grep ^routeQuestions
- What is Bell's ASN?
- The registry records AS36522, registered to Bell Mobility Inc., as the ASN documented as carrying Bell's mobile network. AS577, registered as BACOM to Bell Canada, is recorded with a fixed role and is the Bell Canada backbone. Both were announced at the last probe.
- What is the MCC/MNC of Bell?
- The registry records two codes for Bell, both under MCC 302, with MNC 610 and MNC 630, written together as 302-610 and 302-630. 302-610 is the main Bell Mobility code. 302-630 is recorded as a Bell-owned code whose operational status the registry does not confirm.
- Is an IP from AS36522 a mobile IP?
- AS36522 is the ASN the registry documents as mobile for Bell, so an address originating there is routed by that part of the network. The registry holds no data on individual addresses, so it cannot confirm that a particular one was in use on a handset rather than another device.
Where Bell meets other networks
Sources
Operator and registry pages used for this entry, followed by the RIPEstat Data API (holder, announced prefixes) and the PeeringDB API (network records).
- [1]https://www.bell.ca/Mobility/Our_network_coverage
- [2]https://en.wikipedia.org/wiki/Bell_Canada
- [3]https://en.wikipedia.org/wiki/Bell_Mobility
- [4]https://stat.ripe.net/data/as-overview/data.json?resource=AS36522
- [5]https://stat.ripe.net/data/as-overview/data.json?resource=AS577
- [6]https://en.wikipedia.org/wiki/Mobile_network_codes_in_ITU_region_3xx_(North_America)
- [7]https://raw.githubusercontent.com/pbakondy/mcc-mnc-list/master/mcc-mnc-list.json
- [8]https://stat.ripe.net/docs/02.data-api/
- [9]https://www.peeringdb.com/apidocs/
ASN and prefix data describe how the operator's networks are registered and announced. They do not identify an individual subscriber or where a device is, since carriers route traffic from many areas through shared gateways.