Country
—
ASN LANDING PAGE
MTS-ASN - Bell Canada
Last updated · Apr 4, 2026
Country
—
Total prefixes
19
IPv4 prefixes
18
IPv6 prefixes
1
MTS-ASN - Bell Canada currently shows 19 prefixes and 22 upstream, downstream, or peer relationships. Larger prefix inventories often indicate broader network footprint, but they should still be read together with country and peering context.
ASN landing pages are more useful than a single IP page when you want cloud provider attribution, routing research, infrastructure comparison, or network topology analysis at the organization level.
MTS-ASN - Bell Canada is currently associated with an unknown region. Country data is only a starting point; the more important signals are the organization name, website, prefix volume, and peering relationships that reveal whether the network behaves like a cloud platform, ISP, CDN, or enterprise backbone.
This page is currently showing live ASN data that can be used for peer, prefix, and network scale analysis. The most useful next step is usually to return to a related IP landing page, then compare that concrete address with this ASN profile and with broader topic pages for routing, cloud attribution, or WHOIS ownership analysis.
Detailed data for this ASN is not available right now.
AS16796
AS16796
—
AS398713
AS398713
—
AS53443
AS53443
—
AS19053
AS19053
—
AS62846
AS62846
—
AS33158
AS33158
—
AS399923
AS399923
—
AS900
AS900
—
AS18472
AS18472
—
AS21774
AS21774
—
AS400198
AS400198
—
AS400501
AS400501
—
AS62962
AS62962
—
AS396084
AS396084
—
AS27606
AS27606
—
AS54937
AS54937
—
AS26361
AS26361
—
AS395248
AS395248
—
AS400078
AS400078
—
AS62758
AS62758
—
AS26320
AS26320
—
| Prefix | Name | Country |
|---|---|---|
| 142.160.0.0/16 | AS7122 | — |
| 142.161.0.0/16 | AS7122 | — |
| 142.233.128.0/17 | AS7122 | — |
| 170.199.0.0/17 | AS7122 | — |
| 192.139.126.0/24 | AS7122 | — |
| 192.56.244.0/24 | AS7122 | — |
| 198.163.232.0/22 | AS7122 | — |
| 204.112.0.0/16 | AS7122 | — |
| 205.200.0.0/16 | AS7122 | — |
| 206.45.0.0/16 | AS7122 | — |
| 207.161.0.0/16 | AS7122 | — |
| 209.202.0.0/18 | AS7122 | — |
| 216.130.64.0/19 | AS7122 | — |
| 216.55.192.0/20 | AS7122 | — |
| 216.55.216.0/21 | AS7122 | — |
| 216.55.224.0/20 | AS7122 | — |
| 216.81.0.0/19 | AS7122 | — |
| 2607:ca00:8000::/33 | AS7122 | — |
| 64.4.64.0/19 | AS7122 | — |
A strong reference ASN for Google DNS, Google Cloud, and global network footprint analysis.
Useful for analyzing CDN, Anycast, WAF, and large-scale edge network behavior.
Helpful when comparing Azure, enterprise backbone, and large-cloud routing patterns.
A useful ASN landing page for understanding AWS and large cloud-network ownership.
Continue from this ASN into the differences between WHOIS ownership and ASN ownership.
Continue from this ASN into route troubleshooting and network analysis.
Useful when you want to compare this ASN against larger cloud and edge networks.
Continue from the ASN page into WHOIS and ownership verification.
AS7122 is an autonomous system number used to identify an independently operated network. The current page associates it with MTS-ASN - Bell Canada in an unknown region, which helps determine whether it behaves like a cloud provider, ISP, CDN, or enterprise backbone.
They help explain the scale, interconnection depth, and route structure of AS7122. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
The best next step is usually to return to a concrete IP landing page to see how a specific address maps into AS7122, then continue into cloud, WHOIS, or routing topic pages to understand the network in a broader context.
Understand why WHOIS ownership and ASN ownership can differ, and how to combine both when deciding who really owns or operates an IP.
Use WHOIS, ASN, prefixes, and organization data to determine who ultimately owns an IP, range, or resolved domain target.
Learn what ASN, BGP routes, prefixes, upstreams, downstreams, and peers mean, then explore real ASN pages.
Compare large cloud and edge networks such as Google, Cloudflare, Microsoft, and Amazon through their ASN landing pages.