CLARO S.A.
AS4230 is CLARO S.A. (lacnic.net). It announces 5,155,584 IPv4 addresses in 78 prefixes, and 6 IPv6 prefixes.
Brazil· LACNIC· allocated 1999-11-16· isp
Where its space is
The IPv4 it announces that IP Geolocation places, by country. A /24 counts for the AS announcing most of it.
- Brazil4,969,075 · 100.00%
Registry record
Its ASN Whois record, as the registry publishes it.
- name
- CLARO S.A.
- org
- 40432544070609
- org name
- CLARO S.A.
- country
- BR
- source
- lacnic
- status
- DIRECT ALLOCATION
- created
- 1999-11-16
- updated
- 2015-10-20
- descr
- CLARO S.A.
- abuse
- GSE6
- abuse name
- Grupo de Segurança Internet da Embratel
- abuse kind
- role
- admin
- CAP12
- admin name
- Gerencia Técnica de Operações Internet
- admin kind
- role
What the databases see
Addresses each address-keyed database holds in the IPv4 it announces, as a share of that space, with its largest providers. Counts overlap.
- VPN IP2,524watchguard, draytek, forcepoint_ngfw0.05%
- Residential Proxy IP57,142anyip, geonode, novada1.11%
- None here
- Mobile Proxy IP5,125floppydata, dataimpulse, vibeproxies0.10%
- None here
- None here
- Hosting IP199,4243.87%
- None here
- Carrier IP4,956,160Claro96.13%
- None here
- SSH IP72,9881.42%
- SMTP IP64,7071.26%
- DNS Resolver IP5,7150.11%
IPv4 prefixes
Every IPv4 prefix BGP Route saw it announce. A prefix another AS also announces says so.
| PREFIX | COUNTRY | RPKI | PEERS | FIRST SEEN |
|---|---|---|---|---|
| 179.68.0.0/16 | Brazil | not found | 17 | 2026-10-02 |
| 179.237.0.0/20 | Brazil | valid | 17 | 2026-10-02 |
| 179.237.16.0/21 | Brazil | valid | 17 | 2026-10-02 |
| 179.237.24.0/23 | Brazil | valid | 17 | 2026-10-02 |
| 186.249.160.0/20 | Brazil | valid | 17 | 2026-10-02 |
| 187.28.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 187.29.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 187.30.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 187.43.0.0/16 | Brazil | not found | 17 | 2026-10-02 |
| 189.2.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 189.3.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 189.16.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 189.17.0.0/16 | — | valid | 17 | 2026-10-02 |
| 189.22.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 189.23.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 189.42.0.0/16 | — | valid | 17 | 2026-10-02 |
| 189.43.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 189.52.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 189.53.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 189.86.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 189.87.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 189.88.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 191.38.0.0/15 | Brazil | not found | 17 | 2026-10-02 |
| 191.56.0.0/14 | Brazil | not found | 17 | 2026-10-02 |
| 191.60.0.0/14 | Brazil | not found | 17 | 2026-10-02 |
| 200.10.159.0/24 | Brazil | valid | 17 | 2026-10-02 |
| 200.139.192.0/18 | Brazil | valid | 17 | 2026-10-02 |
| 200.166.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.167.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.172.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.173.0.0/16 | Brazil | not found | 17 | 2026-10-02 |
| 200.174.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.178.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.179.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.182.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.183.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.190.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.191.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.192.0.0/18 | Brazil | valid | 17 | 2026-10-02 |
| 200.208.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.209.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.210.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.211.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.212.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.213.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.214.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.227.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.228.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.230.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.231.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.241.0.0/16 | — | valid | 17 | 2026-10-02 |
| 200.242.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.243.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.244.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.245.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.246.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.247.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.248.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.249.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.250.0.0/16 | — | valid | 17 | 2026-10-02 |
| 200.251.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.252.0.0/16 | — | valid | 17 | 2026-10-02 |
| 200.253.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.254.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 200.255.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 201.30.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 201.31.0.0/16 | — | valid | 17 | 2026-10-02 |
| 201.38.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 201.39.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 201.44.0.0/16 | — | valid | 17 | 2026-10-02 |
| 201.45.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 201.56.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 201.57.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 201.64.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 201.65.0.0/16 | — | valid | 17 | 2026-10-02 |
| 201.72.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
| 201.73.0.0/16 | — | valid | 17 | 2026-10-02 |
| 201.90.0.0/16 | Brazil | valid | 17 | 2026-10-02 |
IPv6 prefixes
Every IPv6 prefix BGP Route saw it announce.
Test the real build first.
An evaluation license puts a full current build in your hands — every row, every column, no sampling — so you can measure it against your own traffic before anyone talks about terms.