Ministerio del Interior y de Seguridad Publica - Gobierno de Chile
AS17147 is Ministerio del Interior y de Seguridad Publica - Gobierno de Chile (lacnic.net). It announces 65,536 IPv4 addresses in 33 prefixes, and 2 IPv6 prefixes.
Chile· LACNIC· allocated 2000-07-31· government
Where its space is
The IPv4 it announces that IP Geolocation places, by country. A /24 counts for the AS announcing most of it.
Registry record
Its ASN Whois record, as the registry publishes it.
- name
- Ministerio del Interior y de Seguridad Publica - Gobierno de Chile
- org
- CL-GOCH1-LACNIC
- org name
- Ministerio del Interior y de Seguridad Publica - Gobierno de Chile
- org address
- -, Teatinos 220, Santiago de Chile, Santiago, 8340434, CL
- org country
- CL
- country
- CL
- source
- lacnic
- status
- DIRECT ALLOCATION
- created
- 2000-07-31
- updated
- 2004-05-17
- descr
- Ministerio del Interior y de Seguridad Publica - Gobierno de Chile
- abuse
- TMC
- abuse name
- ANCI CHILE
- abuse email
- rcse@anci.gob.cl
- abuse phone
- +56 447711131#0000
- abuse kind
- role
- admin
- TMC
- admin name
- ANCI CHILE
- admin email
- rcse@anci.gob.cl
- admin phone
- +56 447711131#0000
- admin kind
- role
- tech
- TMC
- tech name
- ANCI CHILE
- tech email
- rcse@anci.gob.cl
- tech phone
- +56 447711131#0000
- tech 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 IP4880.74%
- anyip, dataimpulse, geonode0.02%
- None here
- None here
- None here
- None here
- Hosting IP2,3043.52%
- None here
- None here
- None here
- SSH IP520.08%
- SMTP IP280.04%
- 0.13%
IPv4 prefixes
Every IPv4 prefix BGP Route saw it announce. A prefix another AS also announces says so.
| PREFIX | COUNTRY | RPKI | PEERS | FIRST SEEN |
|---|---|---|---|---|
| 163.247.0.0/16 | — | valid | 17 | 2026-10-02 |
| 163.247.11.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.12.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.15.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.40.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.41.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.42.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.43.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.44.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.46.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.48.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.49.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.50.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.51.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.52.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.53.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.55.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.57.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.61.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.62.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.63.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.66.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.77.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.84.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.90.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.93.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.109.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.120.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.127.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.133.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.140.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.220.0/24 | — | valid | 17 | 2026-10-02 |
| 163.247.221.0/24 | — | 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.