Country
—
ASN LANDING PAGE
SRS-6-Z-7381 - BroadbandONE
Last updated · Apr 4, 2026
Country
—
Total prefixes
225
IPv4 prefixes
222
IPv6 prefixes
3
SRS-6-Z-7381 - BroadbandONE currently shows 225 prefixes and 23 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.
SRS-6-Z-7381 - BroadbandONE 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.
AS26666
AS26666
—
AS19311
AS19311
—
AS20314
AS20314
—
AS29708
AS29708
—
AS395414
AS395414
—
AS18891
AS18891
—
AS31757
AS31757
—
AS40040
AS40040
—
AS394555
AS394555
—
AS23251
AS23251
—
AS35907
AS35907
—
AS13620
AS13620
—
AS22868
AS22868
—
AS399798
AS399798
—
AS40638
AS40638
—
AS18602
AS18602
—
AS53307
AS53307
—
AS23177
AS23177
—
AS395225
AS395225
—
AS54799
AS54799
—
AS398114
AS398114
—
| Prefix | Name | Country |
|---|---|---|
| 132.225.3.0/24 | AS7381 | — |
| 137.236.21.0/24 | AS7381 | — |
| 142.0.176.0/22 | AS7381 | — |
| 155.46.178.0/24 | AS7381 | — |
| 155.46.186.0/24 | AS7381 | — |
| 155.46.187.0/24 | AS7381 | — |
| 161.195.191.0/24 | AS7381 | — |
| 162.251.208.0/24 | AS7381 | — |
| 162.251.209.0/24 | AS7381 | — |
| 162.251.210.0/24 | AS7381 | — |
| 162.251.211.0/24 | AS7381 | — |
| 162.39.97.0/24 | AS7381 | — |
| 164.152.205.0/24 | AS7381 | — |
| 170.178.128.0/24 | AS7381 | — |
| 170.52.46.0/23 | AS7381 | — |
| 171.162.93.0/24 | AS7381 | — |
| 173.209.228.0/24 | AS7381 | — |
| 173.209.234.0/23 | AS7381 | — |
| 173.209.236.0/22 | AS7381 | — |
| 173.209.240.0/20 | AS7381 | — |
| 173.252.130.0/23 | AS7381 | — |
| 173.252.132.0/22 | AS7381 | — |
| 173.252.137.0/24 | AS7381 | — |
| 173.252.138.0/23 | AS7381 | — |
| 173.252.140.0/23 | AS7381 | — |
| 173.252.142.0/24 | AS7381 | — |
| 173.252.146.0/23 | AS7381 | — |
| 173.252.147.0/24 | AS7381 | — |
| 173.252.148.0/22 | AS7381 | — |
| 173.252.152.0/21 | AS7381 | — |
| 173.252.161.0/24 | AS7381 | — |
| 173.252.162.0/23 | AS7381 | — |
| 173.252.164.0/23 | AS7381 | — |
| 173.252.168.0/21 | AS7381 | — |
| 173.252.176.0/20 | AS7381 | — |
| 198.136.149.0/24 | AS7381 | — |
| 198.207.195.0/24 | AS7381 | — |
| 198.62.209.0/24 | AS7381 | — |
| 198.62.210.0/24 | AS7381 | — |
| 199.127.14.0/24 | AS7381 | — |
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.
AS7381 is an autonomous system number used to identify an independently operated network. The current page associates it with SRS-6-Z-7381 - BroadbandONE 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 AS7381. 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 AS7381, 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.