AS27720
CITTA TELECOM LTDA
AS27720 is CITTA TELECOM LTDA (cittatelecom.com.br). It announces 6,144 IPv4 addresses in 23 prefixes, and 32 IPv6 prefixes.
Brazil· LACNIC· allocated 2013-04-22· isp
6,144
IPv4 addresses announced
23
IPv4 prefixes
32
IPv6 prefixes
92.73%
of its routes RPKI-valid
1,276
of its IPv4 geolocated
1
country
Where its space is
The IPv4 it announces that IP Geolocation places, by country. A /24 counts for the AS announcing most of it.
- Brazil1,276 · 100.00%
Registry record
Its ASN Whois record, as the registry publishes it.
- name
- CITTA TELECOM LTDA
- org
- 12935241000101
- org name
- CITTA TELECOM LTDA
- org address
- BR
- org country
- BR
- country
- BR
- source
- lacnic
- status
- DIRECT ALLOCATION
- created
- 2013-04-22
- updated
- 2013-04-22
- descr
- CITTA TELECOM LTDA
- abuse
- CITEL5
- abuse name
- Citta Telecom
- abuse email
- noc@cittatelecom.com.br
- abuse kind
- role
- admin
- CITEL5
- admin name
- Citta Telecom
- admin email
- noc@cittatelecom.com.br
- 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 IP1101.79%
- novada, geonode, anyip1.33%
- floppydata0.02%
- None here
- None here
- None here
- Hosting IP3,32854.17%
- None here
- Carrier IP768TIM12.50%
- None here
- SSH IP671.09%
- 0.11%
- 0.42%
IPv4 prefixes
Every IPv4 prefix BGP Route saw it announce. A prefix another AS also announces says so.
| PREFIX | COUNTRY | RPKI | PEERS | FIRST SEEN |
|---|---|---|---|---|
| 138.59.96.0/22 | — | valid | 17 | 2026-10-02 |
| 138.59.96.0/23 | — | valid | 17 | 2026-10-02 |
| 138.59.96.0/24 | — | valid | 17 | 2026-10-02 |
| 138.59.97.0/24 | — | valid | 17 | 2026-10-02 |
| 138.59.98.0/23 | Brazil | valid | 17 | 2026-10-02 |
| 138.59.98.0/24 | Brazil | valid | 17 | 2026-10-02 |
| 138.59.99.0/24 | — | valid | 17 | 2026-10-02 |
| 143.208.156.0/22 | — | valid | 17 | 2026-10-02 |
| 143.208.156.0/24 | — | valid | 17 | 2026-10-02 |
| 143.208.157.0/24 | — | valid | 17 | 2026-10-02 |
| 143.208.158.0/24 | — | valid | 17 | 2026-10-02 |
| 143.208.159.0/24 | — | valid | 17 | 2026-10-02 |
| 177.129.8.0/21 | — | valid | 17 | 2026-10-02 |
| 177.129.8.0/22 | — | valid | 17 | 2026-10-02 |
| 177.129.11.0/24 | — | valid | 17 | 2026-10-02 |
| 177.129.12.0/22 | — | valid | 17 | 2026-10-02 |
| 177.129.12.0/24 | — | valid | 17 | 2026-10-02 |
| 177.129.15.0/24 | — | valid | 17 | 2026-10-02 |
| 191.128.224.0/22 | Brazil | not found | 17 | 2026-10-02 |
| 191.128.225.0/24 | Brazil | not found | 17 | 2026-10-02 |
| 191.128.226.0/24 | — | not found | 17 | 2026-10-02 |
| 191.128.227.0/24 | Brazil | not found | 17 | 2026-10-02 |
| 200.95.172.0/22 | — | valid | 17 | 2026-10-02 |
IPv6 prefixes
Every IPv6 prefix BGP Route saw it announce.
| PREFIX | COUNTRY | RPKI | PEERS | FIRST SEEN |
|---|---|---|---|---|
| 2804:da4::/32 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:a::/48 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:12::/48 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:14::/48 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:19::/48 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:1a::/48 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:1b::/48 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:1c::/48 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:1f::/48 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:40::/48 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:42::/48 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:45::/48 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:47::/48 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:49::/48 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:4b::/48 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:53::/48 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:54::/48 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:55::/48 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:57::/48 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:58::/48 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:59::/48 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:5a::/48 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:5c::/48 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:5d::/48 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:5e::/48 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:5f::/48 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:60::/48 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:63::/48 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:7b::/48 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:a4::/48 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:a8::/48 | Brazil | valid | 20 | 2026-10-02 |
| 2804:da4:ad::/48 | Brazil | valid | 20 | 2026-10-02 |
00 · Evaluate
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.
01 · License
Then license what you use.
Standard, for detection and decisions inside your own product and operations.
Redistribution, when the data ships onward inside what you sell — priced by scope, not by seat.
Annual terms, a named contact, and flexible payment terms — monthly, quarterly or yearly.