bgpreport

Network · data from 2026-11-12

AS264724 Universidad Nacional Andres Bello

Registry name: AS264724 - Universidad Nacional Andres Bello, CL · PeeringDB

3IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 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
1Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS264724, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS264724, 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.27.72.0/24 Valid Other IRR onlyNTTCOM 671 100% 67
200.27.73.0/24 Valid Other IRR onlyNTTCOM 671 100% 67
146.83.81.0/24 Valid RIR databaseLACNIC, RADB 670 100% 68
2001:1310:7161::/48 Valid RIR databaseLACNIC, RADB 17 3%low visibility 18

AS-SET

PeeringDB's irr_as_set for AS264724: AS264724:AS-UNAB. 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 (AS264724 isn't in the set, or no route object for AS264724 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 objectsAS264724 in itNot covered
AS264724:AS-UNAB LACNIC 116 No 4

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

  • Route object: RIR2
  • AS-SET: own ASN1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: RIR200.27.72.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
Route object: RIR200.27.73.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
AS-SET: own ASNAS264724:AS-UNABAS264724 isn't in AS264724:AS-UNAB (LACNIC) once expanded. Add AS264724 to it.

Route objects not announced

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

200.27.72.0/23LACNICValid

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.