bgpreport

Network · data from 2026-11-12

AS14795 Banco Credito e Inversiones

Registry name: AS14795 - Banco de Credito e Inversiones, CL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS14795, 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.
161.131.4.0/24 No ROA Nonecovered by 161.131.0.0/16 673 100% 67
161.131.144.0/24 No ROA Nonecovered by 161.131.0.0/16 673 100% 67
199.186.28.0/24 No ROA Other origin only 672 100% 67
161.131.0.0/24 Valid RIR databaseLACNIC, NTTCOM 673 100% 67
161.131.221.0/24 Valid RIR databaseLACNIC, NTTCOM 673 100% 67
161.131.243.0/24 Valid RIR databaseLACNIC, NTTCOM 673 100% 67
161.131.149.0/24 Valid RIR databaseLACNIC 672 100% 67
161.131.164.0/24 Valid RIR databaseLACNIC, NTTCOM 672 100% 67
161.131.185.0/24 Valid RIR databaseLACNIC, NTTCOM 672 100% 67
161.131.182.0/24 Valid RIR databaseLACNIC 671 100% 67
161.131.205.0/24 Valid RIR databaseLACNIC 671 100% 67

AS-SET

AS14795'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 8 are in fix.csv.

  • ROA: none3
  • Route object: none3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none161.131.4.0/24No ROA covers it. Add a ROA for AS14795, maxLength 24.673 of 673
Route object: none161.131.4.0/24No route object for it. A route object for 161.131.0.0/16 with origin AS14795 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14795 in the RIR database for the space.673 of 673
ROA: none161.131.144.0/24No ROA covers it. Add a ROA for AS14795, maxLength 24.673 of 673
Route object: none161.131.144.0/24No route object for it. A route object for 161.131.0.0/16 with origin AS14795 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14795 in the RIR database for the space.673 of 673
ROA: none199.186.28.0/24No ROA covers it. Add a ROA for AS14795, maxLength 24.672 of 673
Route object: none199.186.28.0/24Route objects for it name AS6429, AS19905, AS27978. Add a route object with origin AS14795 in the RIR database for the space.672 of 673

Route objects not announced

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

161.131.0.0/16NTTCOMNo ROA
161.131.69.0/24NTTCOMNo 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.