Country
—
ASN LANDING PAGE
ATLANTICBB-JOHNSTOWN - Breezeline
Last updated · Apr 4, 2026
Country
—
Total prefixes
1920
IPv4 prefixes
1897
IPv6 prefixes
23
ATLANTICBB-JOHNSTOWN - Breezeline currently shows 1920 prefixes and 37 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.
ATLANTICBB-JOHNSTOWN - Breezeline 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.
AS398427
AS398427
—
AS16611
AS16611
—
AS21767
AS21767
—
AS401023
AS401023
—
AS19357
AS19357
—
AS62514
AS62514
—
AS19765
AS19765
—
AS40593
AS40593
—
AS40742
AS40742
—
AS11370
AS11370
—
AS36857
AS36857
—
AS399295
AS399295
—
AS16993
AS16993
—
AS18751
AS18751
—
AS30399
AS30399
—
AS32757
AS32757
—
AS55118
AS55118
—
AS21658
AS21658
—
AS397488
AS397488
—
AS23041
AS23041
—
AS36240
AS36240
—
AS395790
AS395790
—
AS397018
AS397018
—
AS398312
AS398312
—
AS53796
AS53796
—
AS19917
AS19917
—
AS397038
AS397038
—
AS30012
AS30012
—
AS397606
AS397606
—
AS398320
AS398320
—
AS20392
AS20392
—
| Prefix | Name | Country |
|---|---|---|
| 104.153.40.0/22 | AS11776 | — |
| 104.192.128.0/23 | AS11776 | — |
| 104.192.130.0/24 | AS11776 | — |
| 104.192.131.0/24 | AS11776 | — |
| 132.147.0.0/21 | AS11776 | — |
| 132.147.0.0/24 | AS11776 | — |
| 132.147.1.0/24 | AS11776 | — |
| 132.147.10.0/23 | AS11776 | — |
| 132.147.12.0/23 | AS11776 | — |
| 132.147.14.0/23 | AS11776 | — |
| 132.147.16.0/23 | AS11776 | — |
| 132.147.18.0/23 | AS11776 | — |
| 132.147.2.0/23 | AS11776 | — |
| 132.147.20.0/23 | AS11776 | — |
| 132.147.22.0/23 | AS11776 | — |
| 132.147.24.0/23 | AS11776 | — |
| 132.147.26.0/24 | AS11776 | — |
| 132.147.27.0/24 | AS11776 | — |
| 132.147.28.0/23 | AS11776 | — |
| 132.147.30.0/24 | AS11776 | — |
| 132.147.31.0/24 | AS11776 | — |
| 132.147.32.0/23 | AS11776 | — |
| 132.147.34.0/24 | AS11776 | — |
| 132.147.35.0/24 | AS11776 | — |
| 132.147.36.0/24 | AS11776 | — |
| 132.147.37.0/24 | AS11776 | — |
| 132.147.38.0/23 | AS11776 | — |
| 132.147.4.0/23 | AS11776 | — |
| 132.147.40.0/23 | AS11776 | — |
| 132.147.42.0/23 | AS11776 | — |
| 132.147.44.0/23 | AS11776 | — |
| 132.147.46.0/23 | AS11776 | — |
| 132.147.48.0/20 | AS11776 | — |
| 132.147.48.0/22 | AS11776 | — |
| 132.147.52.0/22 | AS11776 | — |
| 132.147.56.0/22 | AS11776 | — |
| 132.147.6.0/23 | AS11776 | — |
| 132.147.60.0/22 | AS11776 | — |
| 132.147.8.0/23 | AS11776 | — |
| 137.103.0.0/19 | AS11776 | — |
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.
AS11776 is an autonomous system number used to identify an independently operated network. The current page associates it with ATLANTICBB-JOHNSTOWN - Breezeline 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 AS11776. 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 AS11776, 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.