Network · data from 2026-11-12

AS17147 AS17147 - Ministerio del Interior y de Seguridad Publica - Gobierno de Chile

Registry name: AS17147 - Ministerio del Interior y de Seguridad Publica - Gobierno de Chile, CL · not in PeeringDB

34IPv4 routes 100.0% RPKI valid · 100.0% with a route object

2IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

23Route objects not announced registered with origin AS17147, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS17147, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.


163.247.0.0/16	Valid	RIR databaseLACNIC, NTTCOM, RADB	673 100%	67
163.247.11.0/24	Valid	RIR databaseLACNIC	673 100%	67
163.247.12.0/24	Valid	RIR databaseLACNIC	673 100%	67
163.247.40.0/24	Valid	RIR databaseLACNIC	673 100%	67
163.247.44.0/24	Valid	RIR databaseLACNIC	673 100%	67
163.247.57.0/24	Valid	RIR databaseLACNIC	673 100%	67
163.247.109.0/24	Valid	RIR databaseLACNIC	673 100%	67
163.247.120.0/24	Valid	RIR databaseLACNIC	673 100%	67
163.247.127.0/24	Valid	RIR databaseLACNIC	673 100%	67
163.247.220.0/24	Valid	RIR databaseLACNIC	673 100%	67
163.247.15.0/24	Valid	RIR databaseLACNIC	672 100%	67
163.247.41.0/24	Valid	RIR databaseLACNIC	672 100%	67
163.247.42.0/24	Valid	RIR databaseLACNIC	672 100%	67
163.247.43.0/24	Valid	RIR databaseLACNIC	672 100%	67
163.247.45.0/24	Valid	RIR databaseLACNIC	672 100%	67
163.247.46.0/24	Valid	RIR databaseLACNIC	672 100%	67
163.247.48.0/24	Valid	RIR databaseLACNIC	672 100%	67
163.247.49.0/24	Valid	RIR databaseLACNIC	672 100%	67
163.247.50.0/24	Valid	RIR databaseLACNIC	672 100%	67
163.247.51.0/24	Valid	RIR databaseLACNIC	672 100%	67
163.247.52.0/24	Valid	RIR databaseLACNIC	672 100%	67
163.247.53.0/24	Valid	RIR databaseLACNIC	672 100%	67
163.247.55.0/24	Valid	RIR databaseLACNIC	672 100%	67
163.247.61.0/24	Valid	RIR databaseLACNIC	672 100%	67
163.247.62.0/24	Valid	RIR databaseLACNIC	672 100%	67
163.247.63.0/24	Valid	RIR databaseLACNIC	672 100%	67
163.247.66.0/24	Valid	RIR databaseLACNIC	672 100%	67
163.247.77.0/24	Valid	RIR databaseLACNIC	672 100%	67
163.247.84.0/24	Valid	RIR databaseLACNIC	672 100%	67
163.247.90.0/24	Valid	RIR databaseLACNIC	672 100%	67
163.247.93.0/24	Valid	RIR databaseLACNIC	672 100%	67
163.247.133.0/24	Valid	RIR databaseLACNIC	672 100%	67
163.247.140.0/24	Valid	RIR databaseLACNIC	672 100%	67
163.247.221.0/24	Valid	RIR databaseLACNIC	672 100%	67
2801:2::/32	Valid	RIR databaseLACNIC, RADB	635 100%	67
2801:2:140::/48	Valid	RIR databaseLACNIC	634 100%	67

AS-SET

AS17147 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 23 are in fix.csv.

Route object: not announced23

Route objects not announced

Route objects with origin AS17147 whose prefix no peer sees AS17147 announce. Many are kept on purpose (backup routes, space announced only in some places).


163.247.47.0/24	LACNIC	Valid
163.247.54.0/24	LACNIC	Valid
163.247.56.0/24	LACNIC	Valid
163.247.58.0/24	LACNIC	Valid
163.247.59.0/24	LACNIC	Valid
163.247.60.0/24	LACNIC	Valid
163.247.64.0/24	LACNIC	Valid
163.247.65.0/24	LACNIC	Valid
163.247.69.0/24	LACNIC	Valid
163.247.70.0/24	LACNIC	Valid
163.247.72.0/24	LACNIC	Valid
163.247.75.0/24	LACNIC	Valid
163.247.76.0/24	LACNIC	Valid
163.247.80.0/24	LACNIC	Valid
163.247.138.0/24	LACNIC	Valid
163.247.142.0/24	LACNIC	Valid
2801:2:85::a:0:0/96	LACNIC	Valid
2801:2:85::b:0:0/96	LACNIC	Valid
2801:2:85::54:0:0/96	LACNIC	Valid
2801:2:85::70:0:0/96	LACNIC	Valid
2801:2:85::72:0:0/96	LACNIC	Valid
2801:2:85::75:0:0/96	LACNIC	Valid
2801:2:100::/48	LACNIC	Valid

163.247.47.0/24

LACNIC

Valid

163.247.54.0/24

LACNIC

Valid

163.247.56.0/24

LACNIC

Valid

163.247.58.0/24

LACNIC

Valid

163.247.59.0/24

LACNIC

Valid

163.247.60.0/24

LACNIC

Valid

163.247.64.0/24

LACNIC

Valid

163.247.65.0/24

LACNIC

Valid

163.247.69.0/24

LACNIC

Valid

163.247.70.0/24

LACNIC

Valid

163.247.72.0/24

LACNIC

Valid

163.247.75.0/24

LACNIC

Valid

163.247.76.0/24

LACNIC

Valid

163.247.80.0/24

LACNIC

Valid

163.247.138.0/24

LACNIC

Valid

163.247.142.0/24

LACNIC

Valid

2801:2:85::a:0:0/96

LACNIC

Valid

2801:2:85::b:0:0/96

LACNIC

Valid

2801:2:85::54:0:0/96

LACNIC

Valid

2801:2:85::70:0:0/96

LACNIC

Valid

2801:2:85::72:0:0/96

LACNIC

Valid

2801:2:85::75:0:0/96

LACNIC

Valid

2801:2:100::/48

LACNIC

Valid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.