bgpreport

Network · data from 2026-11-12

AS20191 Pontificia Universidad Catolica de Chile

Registry name: AS20191 - Pontificia Universidad Catolica de Chile, CL · PeeringDB

47IPv4 routes 100.0% RPKI valid · 31.9% with a route object
4IPv6 routes 100.0% RPKI valid · 50.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 34 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS20191, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS20191, 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.

146.155.1.0/24 Valid Nonecovered by 146.155.0.0/16 666 99% 68
2800:1b0:5000::/36 Valid Nonecovered by 2800:1b0::/32 635 100% 67
2800:1b0:6000::/36 Valid Nonecovered by 2800:1b0::/32 635 100% 67
146.155.77.0/24 Valid Nonecovered by 146.155.0.0/16 136 20% 46
146.155.92.0/24 Valid Nonecovered by 146.155.0.0/16 136 20% 46
146.155.95.0/24 Valid Nonecovered by 146.155.0.0/16 136 20% 46
146.155.100.0/24 Valid Nonecovered by 146.155.0.0/16 136 20% 46
146.155.109.0/24 Valid Nonecovered by 146.155.0.0/16 136 20% 46
146.155.118.0/24 Valid Nonecovered by 146.155.0.0/16 136 20% 46
146.155.119.0/24 Valid Nonecovered by 146.155.0.0/16 136 20% 46
146.155.160.0/23 Valid Nonecovered by 146.155.0.0/16 136 20% 46
146.155.61.0/24 Valid Nonecovered by 146.155.0.0/16 125 19% 44
146.155.88.0/24 Valid Nonecovered by 146.155.0.0/16 125 19% 44
146.155.252.0/24 Valid Nonecovered by 146.155.0.0/16 125 19% 44
146.155.253.0/24 Valid Nonecovered by 146.155.0.0/16 125 19% 44
146.155.255.0/24 Valid Nonecovered by 146.155.0.0/16 125 19% 44
146.155.157.0/24 Valid Nonecovered by 146.155.0.0/16 121 18% 43
146.155.158.0/24 Valid Nonecovered by 146.155.0.0/16 121 18% 43
146.155.0.0/20 Valid Nonecovered by 146.155.0.0/16 112 17% 41
146.155.16.0/20 Valid Nonecovered by 146.155.0.0/16 112 17% 41
146.155.32.0/20 Valid Nonecovered by 146.155.0.0/16 112 17% 41
146.155.48.0/20 Valid Nonecovered by 146.155.0.0/16 112 17% 41
146.155.64.0/20 Valid Nonecovered by 146.155.0.0/16 112 17% 41
146.155.80.0/20 Valid Nonecovered by 146.155.0.0/16 112 17% 41
146.155.96.0/20 Valid Nonecovered by 146.155.0.0/16 112 17% 41
146.155.112.0/20 Valid Nonecovered by 146.155.0.0/16 112 17% 41
146.155.128.0/20 Valid Nonecovered by 146.155.0.0/16 112 17% 41
146.155.144.0/20 Valid Nonecovered by 146.155.0.0/16 112 17% 41
146.155.160.0/20 Valid Nonecovered by 146.155.0.0/16 112 17% 41
146.155.176.0/20 Valid Nonecovered by 146.155.0.0/16 112 17% 41
146.155.192.0/20 Valid Nonecovered by 146.155.0.0/16 112 17% 41
146.155.208.0/20 Valid Nonecovered by 146.155.0.0/16 112 17% 41
146.155.224.0/20 Valid Nonecovered by 146.155.0.0/16 112 17% 41
146.155.240.0/20 Valid Nonecovered by 146.155.0.0/16 112 17% 41
146.155.2.0/24 Valid Other IRR onlyRADB 666 99% 68
146.155.25.0/24 Valid Other IRR onlyRADB 666 99% 68
146.155.39.0/24 Valid Other IRR onlyRADB 666 99% 68
146.155.49.0/24 Valid Other IRR onlyRADB 666 99% 68
146.155.60.0/24 Valid Other IRR onlyRADB 666 99% 68
146.155.73.0/24 Valid Other IRR onlyRADB 666 99% 68
146.155.75.0/24 Valid Other IRR onlyRADB 666 99% 68
146.155.89.0/24 Valid Other IRR onlyRADB 666 99% 68
146.155.94.0/24 Valid Other IRR onlyRADB 666 99% 68
146.155.97.0/24 Valid Other IRR onlyRADB 666 99% 68
146.155.99.0/24 Valid Other IRR onlyRADB 666 99% 68
146.155.117.0/24 Valid Other IRR onlyRADB 666 99% 68
146.155.127.0/24 Valid Other IRR onlyRADB 666 99% 68
146.155.96.0/24 Valid Other IRR onlyRADB 136 20% 46
146.155.0.0/16 Valid RIR databaseLACNIC 669 99% 68
2800:1b0::/32 Valid RIR databaseLACNIC 635 100% 67
2001:1310:7171::/48 Valid RIR databaseLACNIC, RADB 23 4%low visibility 12

AS-SET

PeeringDB's irr_as_set for AS20191: AS20191:AS-UC. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS20191 isn't in the set, or no route object for AS20191 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS20191 in itNot covered
AS20191:AS-UC LACNIC 1120 Yes 0

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 51 are in fix.csv.

  • Route object: none34
  • Route object: RIR14
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none146.155.1.0/24No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.666 of 673
Route object: none2800:1b0:5000::/36No route object for it. A route object for 2800:1b0::/32 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.635 of 636
Route object: none2800:1b0:6000::/36No route object for it. A route object for 2800:1b0::/32 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.635 of 636
Route object: none146.155.77.0/24No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.136 of 673
Route object: none146.155.92.0/24No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.136 of 673
Route object: none146.155.95.0/24No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.136 of 673
Route object: none146.155.100.0/24No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.136 of 673
Route object: none146.155.109.0/24No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.136 of 673
Route object: none146.155.118.0/24No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.136 of 673
Route object: none146.155.119.0/24No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.136 of 673
Route object: none146.155.160.0/23No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.136 of 673
Route object: none146.155.61.0/24No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.125 of 673
Route object: none146.155.88.0/24No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.125 of 673
Route object: none146.155.252.0/24No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.125 of 673
Route object: none146.155.253.0/24No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.125 of 673
Route object: none146.155.255.0/24No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.125 of 673
Route object: none146.155.157.0/24No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.121 of 673
Route object: none146.155.158.0/24No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.121 of 673
Route object: none146.155.0.0/20No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.112 of 673
Route object: none146.155.16.0/20No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.112 of 673
Route object: none146.155.32.0/20No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.112 of 673
Route object: none146.155.48.0/20No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.112 of 673
Route object: none146.155.64.0/20No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.112 of 673
Route object: none146.155.80.0/20No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.112 of 673
Route object: none146.155.96.0/20No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.112 of 673
Route object: none146.155.112.0/20No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.112 of 673
Route object: none146.155.128.0/20No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.112 of 673
Route object: none146.155.144.0/20No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.112 of 673
Route object: none146.155.160.0/20No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.112 of 673
Route object: none146.155.176.0/20No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.112 of 673
Route object: none146.155.192.0/20No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.112 of 673
Route object: none146.155.208.0/20No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.112 of 673
Route object: none146.155.224.0/20No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.112 of 673
Route object: none146.155.240.0/20No route object for it. A route object for 146.155.0.0/16 with origin AS20191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20191 in the RIR database for the space.112 of 673
Route object: RIR146.155.2.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR146.155.25.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR146.155.39.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR146.155.49.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR146.155.60.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR146.155.73.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR146.155.75.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR146.155.89.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR146.155.94.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR146.155.97.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR146.155.99.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR146.155.117.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR146.155.127.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR146.155.96.0/24Route object only in RADB. Add it in the RIR database for the space.136 of 673

Route objects not announced

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

146.155.122.0/24RADBValid
146.155.123.0/24RADBValid
2001:470:3e9::/48ARINValid

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.