Country
—
ASN LANDING PAGE
UTANDE
Last updated · Apr 4, 2026
Country
—
Total prefixes
91
IPv4 prefixes
90
IPv6 prefixes
1
UTANDE currently shows 91 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.
UTANDE 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.
AS37468
AS37468
—
AS6939
AS6939
—
AS30844
AS30844
—
AS33763
AS33763
—
AS174
AS174
—
AS37204
AS37204
—
AS58453
AS58453
—
AS917
AS917
—
AS37680
AS37680
—
AS24482
AS24482
—
AS32653
AS32653
—
AS36236
AS36236
—
AS37239
AS37239
—
AS39120
AS39120
—
AS199524
AS199524
—
AS327804
AS327804
—
AS328137
AS328137
—
AS31856
AS31856
—
AS37697
AS37697
—
AS37721
AS37721
—
AS328320
AS328320
—
AS6774
AS6774
—
AS327960
AS327960
—
AS327983
AS327983
—
AS37329
AS37329
—
AS328291
AS328291
—
AS328701
AS328701
—
| Prefix | Name | Country |
|---|---|---|
| 196.2.64.0/20 | AS37183 | — |
| 196.2.64.0/21 | AS37183 | — |
| 196.2.64.0/24 | AS37183 | — |
| 196.2.66.0/23 | AS37183 | — |
| 196.2.66.0/24 | AS37183 | — |
| 196.2.67.0/24 | AS37183 | — |
| 196.2.69.0/24 | AS37183 | — |
| 196.2.70.0/23 | AS37183 | — |
| 196.2.70.0/24 | AS37183 | — |
| 196.2.72.0/21 | AS37183 | — |
| 196.2.72.0/24 | AS37183 | — |
| 196.2.73.0/24 | AS37183 | — |
| 196.2.75.0/24 | AS37183 | — |
| 196.2.76.0/24 | AS37183 | — |
| 196.2.79.0/24 | AS37183 | — |
| 196.29.32.0/21 | AS37183 | — |
| 196.29.32.0/22 | AS37183 | — |
| 196.29.32.0/23 | AS37183 | — |
| 196.29.32.0/24 | AS37183 | — |
| 196.29.33.0/24 | AS37183 | — |
| 196.29.34.0/23 | AS37183 | — |
| 196.29.34.0/24 | AS37183 | — |
| 196.29.35.0/24 | AS37183 | — |
| 196.29.36.0/22 | AS37183 | — |
| 196.29.36.0/23 | AS37183 | — |
| 196.29.36.0/24 | AS37183 | — |
| 196.29.37.0/24 | AS37183 | — |
| 196.29.38.0/23 | AS37183 | — |
| 196.29.38.0/24 | AS37183 | — |
| 196.29.39.0/24 | AS37183 | — |
| 196.43.100.0/24 | AS37183 | — |
| 196.43.101.0/24 | AS37183 | — |
| 196.43.102.0/24 | AS37183 | — |
| 196.43.103.0/24 | AS37183 | — |
| 196.43.104.0/23 | AS37183 | — |
| 196.43.104.0/24 | AS37183 | — |
| 196.43.105.0/24 | AS37183 | — |
| 196.43.106.0/23 | AS37183 | — |
| 196.43.106.0/24 | AS37183 | — |
| 196.43.107.0/24 | AS37183 | — |
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.
AS37183 is an autonomous system number used to identify an independently operated network. The current page associates it with UTANDE 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 AS37183. 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 AS37183, 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.