Country
—
ASN LANDING PAGE
UFINET BRASIL S.A.
Last updated · Apr 4, 2026
Country
—
Total prefixes
33
IPv4 prefixes
20
IPv6 prefixes
13
UFINET BRASIL S.A. currently shows 33 prefixes and 50 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.
UFINET BRASIL S.A. 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.
AS6762
AS6762
—
AS3356
AS3356
—
AS13786
AS13786
—
AS16735
AS16735
—
AS264867
AS264867
—
AS268671
AS268671
—
AS23106
AS23106
—
AS174
AS174
—
AS52840
AS52840
—
AS263009
AS263009
—
AS270724
AS270724
—
AS273478
AS273478
—
AS264014
AS264014
—
AS52468
AS52468
—
AS52320
AS52320
—
AS264129
AS264129
—
AS272618
AS272618
—
AS28258
AS28258
—
AS265130
AS265130
—
AS265465
AS265465
—
AS262474
AS262474
—
AS263327
AS263327
—
AS263087
AS263087
—
AS271404
AS271404
—
AS37468
AS37468
—
AS265330
AS265330
—
AS52587
AS52587
—
AS53062
AS53062
—
AS265377
AS265377
—
AS268829
AS268829
—
AS271502
AS271502
—
AS264906
AS264906
—
AS268311
AS268311
—
AS268696
AS268696
—
AS28154
AS28154
—
AS61649
AS61649
—
AS263347
AS263347
—
AS263482
AS263482
—
AS266428
AS266428
—
AS267158
AS267158
—
| Prefix | Name | Country |
|---|---|---|
| 177.67.80.0/22 | AS53013 | — |
| 177.67.80.0/23 | AS53013 | — |
| 177.67.82.0/23 | AS53013 | — |
| 177.67.84.0/24 | AS53013 | — |
| 177.67.85.0/24 | AS53013 | — |
| 177.67.86.0/24 | AS53013 | — |
| 177.67.87.0/24 | AS53013 | — |
| 209.14.12.0/22 | AS53013 | — |
| 209.14.12.0/23 | AS53013 | — |
| 209.14.12.0/24 | AS53013 | — |
| 209.14.13.0/24 | AS53013 | — |
| 209.14.14.0/23 | AS53013 | — |
| 209.14.14.0/24 | AS53013 | — |
| 209.14.15.0/24 | AS53013 | — |
| 209.14.155.0/24 | AS53013 | — |
| 209.14.159.0/24 | AS53013 | — |
| 209.14.228.0/24 | AS53013 | — |
| 209.14.229.0/24 | AS53013 | — |
| 209.14.7.0/24 | AS53013 | — |
| 2804:574:100::/45 | AS53013 | — |
| 2804:574:2000::/35 | AS53013 | — |
| 2804:574:2006::/48 | AS53013 | — |
| 2804:574:3::/48 | AS53013 | — |
| 2804:574:4::/48 | AS53013 | — |
| 2804:574:5::/48 | AS53013 | — |
| 2804:574:6::/48 | AS53013 | — |
| 2804:574:8000::/33 | AS53013 | — |
| 2804:574:8::/48 | AS53013 | — |
| 2804:574::/33 | AS53013 | — |
| 2804:574:a::/48 | AS53013 | — |
| 2804:574:aaaa::/48 | AS53013 | — |
| 2804:574:c000::/48 | AS53013 | — |
| 38.226.18.0/24 | AS53013 | — |
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.
AS53013 is an autonomous system number used to identify an independently operated network. The current page associates it with UFINET BRASIL S.A. 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 AS53013. 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 AS53013, 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.