Country
—
ASN LANDING PAGE
AS52527 - IWNET TELECOM LTDA ME
Last updated · Jul 20, 2026
Country
—
Total prefixes
43
IPv4 prefixes
18
IPv6 prefixes
25
AS52527 - IWNET TELECOM LTDA ME currently reports 43 prefixes and 38 upstream, downstream, or peer relationships. These counts describe the current dataset; they do not by themselves prove network quality, reach, or service use.
An ASN page shows the public organization label, country or region, BGP prefixes, and available peer and upstream relationships. It adds network context but cannot confirm a website host, physical facility, security status, or service quality.
AS52527 - IWNET TELECOM LTDA ME is currently associated with an unknown region. These values come from public network sources and are useful lookup clues; an organization label, registration region, and actual service location may differ.
The page shows ASN data returned by the current upstream query; interpret it with the update time. Open representative IP pages from the same network and compare prefixes, source labels, and query times. Verify operator or service claims with the relevant registry or network operator.
Detailed data for this ASN is not available right now.
AS264144
AS264144
—
AS3356
AS3356
—
AS52468
AS52468
—
AS6939
AS6939
—
AS266409
AS266409
—
AS6057
AS6057
—
AS22548
AS22548
—
AS35280
AS35280
—
AS28634
AS28634
—
AS198150
AS198150
—
AS24482
AS24482
—
AS28624
AS28624
—
AS36236
AS36236
—
AS51185
AS51185
—
AS52873
AS52873
—
AS60503
AS60503
—
AS61573
AS61573
—
AS199524
AS199524
—
AS262427
AS262427
—
AS263152
AS263152
—
AS263237
AS263237
—
AS264479
AS264479
—
AS271253
AS271253
—
AS14840
AS14840
—
AS266931
AS266931
—
AS268643
AS268643
—
AS7195
AS7195
—
AS39120
AS39120
—
AS52320
AS52320
—
AS267366
AS267366
—
AS267530
AS267530
—
AS267998
AS267998
—
AS271666
AS271666
—
| Prefix | Name | Country |
|---|---|---|
| 177.152.80.0/24 | AS52527 | — |
| 177.152.81.0/24 | AS52527 | — |
| 177.152.82.0/24 | AS52527 | — |
| 177.152.83.0/24 | AS52527 | — |
| 177.152.84.0/22 | AS52527 | — |
| 177.152.84.0/23 | AS52527 | — |
| 177.152.84.0/24 | AS52527 | — |
| 177.152.85.0/24 | AS52527 | — |
| 177.152.86.0/23 | AS52527 | — |
| 177.152.86.0/24 | AS52527 | — |
| 177.152.87.0/24 | AS52527 | — |
| 200.150.252.0/22 | AS52527 | — |
| 200.150.252.0/23 | AS52527 | — |
| 200.150.252.0/24 | AS52527 | — |
| 200.150.253.0/24 | AS52527 | — |
| 200.150.254.0/23 | AS52527 | — |
| 200.150.254.0/24 | AS52527 | — |
| 200.150.255.0/24 | AS52527 | — |
| 2804:dec:100::/40 | AS52527 | — |
| 2804:dec:2000::/35 | AS52527 | — |
| 2804:dec:200::/40 | AS52527 | — |
| 2804:dec:301::/48 | AS52527 | — |
| 2804:dec:302::/48 | AS52527 | — |
| 2804:dec:304::/48 | AS52527 | — |
| 2804:dec:305::/48 | AS52527 | — |
| 2804:dec:4000::/34 | AS52527 | — |
| 2804:dec:4000::/35 | AS52527 | — |
| 2804:dec:4001::/48 | AS52527 | — |
| 2804:dec:400::/40 | AS52527 | — |
| 2804:dec:500::/40 | AS52527 | — |
| 2804:dec:6000::/35 | AS52527 | — |
| 2804:dec:8000::/33 | AS52527 | — |
| 2804:dec:8000::/34 | AS52527 | — |
| 2804:dec:8000::/35 | AS52527 | — |
| 2804:dec:8100::/40 | AS52527 | — |
| 2804:dec:8200::/40 | AS52527 | — |
| 2804:dec::/33 | AS52527 | — |
| 2804:dec::/34 | AS52527 | — |
| 2804:dec::/35 | AS52527 | — |
| 2804:dec:a000::/35 | AS52527 | — |
Review Google network organization fields, prefixes, peers, upstreams, and downstreams.
Review Cloudflare network organization fields, prefixes, peers, upstreams, and downstreams.
Review Microsoft network organization fields, prefixes, peers, upstreams, and downstreams.
Review Amazon network organization fields, prefixes, peers, upstreams, and downstreams.
AS52527 is an autonomous system number. The current source associates it with AS52527 - IWNET TELECOM LTDA ME and the region field an unknown region; those values add network context but do not prove a specific service, physical location, or quality level.
They help explain the scale, interconnection depth, and route structure of AS52527. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
Open a concrete IP page to check how the address maps into AS52527, then compare the prefix, source labels, and query time. Verify operator or service claims with the relevant registry or network operator.
Use real IP and ASN pages to understand ASNs, BGP prefixes, peers, upstreams, and downstreams, including the limits of each snapshot.
Build troubleshooting context from an IP, BGP prefix, ASN, and public network relationships without treating static route data as a packet path.
Compare representative cloud and edge networks by ASN, announced prefixes, peers, upstreams, and downstreams without inferring a specific host or customer workload.