bgpreport

Network · data from 2026-11-12

AS22975 Banco de Chile

Registry name: AS22975 - Banco de Chile, CL · PeeringDB

9IPv4 routes 0.0% RPKI valid · 77.8% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
9No ROA 2 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS22975, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS22975, 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.
200.14.176.0/24 No ROA None 25 4%low visibility 13
200.14.177.0/24 No ROA None 25 4%low visibility 13
200.14.156.0/24 No ROA Other IRR onlyRADB 670 100% 67
200.14.160.0/24 No ROA Other IRR onlyRADB 668 99% 67
200.14.130.0/24 No ROA Other IRR onlyNTTCOM, RADB 666 99% 67
200.14.132.0/24 No ROA Other IRR onlyNTTCOM, RADB 666 99% 67
200.14.133.0/24 No ROA Other IRR onlyNTTCOM, RADB 666 99% 67
200.14.135.0/24 No ROA Other IRR onlyNTTCOM, RADB 666 99% 67
200.14.140.0/24 No ROA Other IRR onlyRADB 666 99% 67

AS-SET

AS22975's PeeringDB record names no 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 21 are in fix.csv.

  • ROA: none9
  • Route object: none2
  • Route object: RIR7
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none200.14.176.0/24No ROA covers it. Add a ROA for AS22975, maxLength 24.25 of 673
Route object: none200.14.176.0/24No route object for it. Add a route object with origin AS22975 in the RIR database for the space.25 of 673
ROA: none200.14.177.0/24No ROA covers it. Add a ROA for AS22975, maxLength 24.25 of 673
Route object: none200.14.177.0/24No route object for it. Add a route object with origin AS22975 in the RIR database for the space.25 of 673
ROA: none200.14.156.0/24No ROA covers it. Add a ROA for AS22975, maxLength 24.670 of 673
Route object: RIR200.14.156.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none200.14.160.0/24No ROA covers it. Add a ROA for AS22975, maxLength 24.668 of 673
Route object: RIR200.14.160.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none200.14.130.0/24No ROA covers it. Add a ROA for AS22975, maxLength 24.666 of 673
Route object: RIR200.14.130.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.666 of 673
ROA: none200.14.132.0/24No ROA covers it. Add a ROA for AS22975, maxLength 24.666 of 673
Route object: RIR200.14.132.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.666 of 673
ROA: none200.14.133.0/24No ROA covers it. Add a ROA for AS22975, maxLength 24.666 of 673
Route object: RIR200.14.133.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.666 of 673
ROA: none200.14.135.0/24No ROA covers it. Add a ROA for AS22975, maxLength 24.666 of 673
Route object: RIR200.14.135.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.666 of 673
ROA: none200.14.140.0/24No ROA covers it. Add a ROA for AS22975, maxLength 24.666 of 673
Route object: RIR200.14.140.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673

Route objects not announced

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

200.12.24.0/24NTTCOMNo ROA
200.14.150.0/23RADBNo ROA
200.14.160.0/23RADBNo ROA

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.