Country
—
ASN LANDING PAGE
CCI-TEXAS - Fidium
Last updated · Apr 4, 2026
Country
—
Total prefixes
67
IPv4 prefixes
66
IPv6 prefixes
1
CCI-TEXAS - Fidium currently shows 67 prefixes and 33 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.
CCI-TEXAS - Fidium 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.
AS19201
AS19201
—
AS33128
AS33128
—
AS17093
AS17093
—
AS398260
AS398260
—
AS14808
AS14808
—
AS395868
AS395868
—
AS395183
AS395183
—
AS63325
AS63325
—
AS16716
AS16716
—
AS4900
AS4900
—
AS22788
AS22788
—
AS397980
AS397980
—
AS399388
AS399388
—
AS31859
AS31859
—
AS394742
AS394742
—
AS54999
AS54999
—
AS19366
AS19366
—
AS22442
AS22442
—
AS62467
AS62467
—
AS22645
AS22645
—
AS13760
AS13760
—
| Prefix | Name | Country |
|---|---|---|
| 135.26.0.0/18 | AS6300 | — |
| 135.26.64.0/18 | AS6300 | — |
| 135.26.64.0/19 | AS6300 | — |
| 135.26.96.0/19 | AS6300 | — |
| 156.47.128.0/18 | AS6300 | — |
| 156.47.128.0/20 | AS6300 | — |
| 156.47.144.0/20 | AS6300 | — |
| 156.47.172.0/22 | AS6300 | — |
| 156.47.176.0/20 | AS6300 | — |
| 162.217.208.0/22 | AS6300 | — |
| 162.217.211.0/24 | AS6300 | — |
| 207.70.128.0/19 | AS6300 | — |
| 207.70.134.0/24 | AS6300 | — |
| 207.70.135.0/24 | AS6300 | — |
| 207.70.136.0/24 | AS6300 | — |
| 207.70.139.0/24 | AS6300 | — |
| 207.70.140.0/24 | AS6300 | — |
| 207.70.142.0/24 | AS6300 | — |
| 207.70.143.0/24 | AS6300 | — |
| 207.70.146.0/24 | AS6300 | — |
| 207.70.148.0/24 | AS6300 | — |
| 207.70.153.0/24 | AS6300 | — |
| 207.70.160.0/19 | AS6300 | — |
| 207.70.161.0/24 | AS6300 | — |
| 207.70.162.0/24 | AS6300 | — |
| 207.70.164.0/24 | AS6300 | — |
| 207.70.165.0/24 | AS6300 | — |
| 207.70.166.0/24 | AS6300 | — |
| 207.70.167.0/24 | AS6300 | — |
| 207.70.168.0/24 | AS6300 | — |
| 207.70.169.0/24 | AS6300 | — |
| 207.70.175.0/24 | AS6300 | — |
| 208.124.64.0/20 | AS6300 | — |
| 208.124.80.0/20 | AS6300 | — |
| 209.169.112.0/20 | AS6300 | — |
| 209.169.64.0/18 | AS6300 | — |
| 209.169.64.0/19 | AS6300 | — |
| 209.169.96.0/20 | AS6300 | — |
| 209.34.0.0/19 | AS6300 | — |
| 209.34.10.0/24 | AS6300 | — |
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.
AS6300 is an autonomous system number used to identify an independently operated network. The current page associates it with CCI-TEXAS - Fidium 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 AS6300. 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 AS6300, 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.