bgpreport

Network · data from 2026-11-12

AS263779 Academia Nacional de Ciencias

Registry name: AS263779 - Academia Nacional de Ciencias, CR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263779, 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.10.176.0/24 Valid Nonecovered by 200.10.176.0/23 672 100% 67
200.10.177.0/24 Valid Nonecovered by 200.10.176.0/23 672 100% 68
200.107.82.0/24 Valid Other IRR onlyRADB 670 100% 67
45.231.52.0/24 Valid RIR databaseLACNIC 670 100% 67
2001:13c7:7004::/48 Valid RIR databaseLACNIC, RADB 635 100% 70
2801:1d:a001::/48 Valid RIR databaseLACNIC, RADB 635 100% 68
2801:1d:a002::/48 Valid RIR databaseLACNIC, RADB 635 100% 67
2a01:53c0:ff19::/48 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS263779'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 22 are in fix.csv.

  • Route object: none2
  • Route object: RIR1
  • Route object: not announced19
ChangePrefix or setDetailFull-table peers
Route object: none200.10.176.0/24No route object for it. A route object for 200.10.176.0/23 with origin AS263779 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263779 in the RIR database for the space.672 of 673
Route object: none200.10.177.0/24No route object for it. A route object for 200.10.176.0/23 with origin AS263779 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263779 in the RIR database for the space.672 of 673
Route object: RIR200.107.82.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

45.231.52.0/22RADBNo ROA
45.231.54.0/24LACNICValid
200.10.176.0/23LACNIC, RADBValid
200.107.82.0/23LACNICValid
200.107.83.0/24RADBValid
2801:1d:a000::/44RADBNo ROA
2801:1d:a000::/48LACNICValid
2801:1d:a003::/48RADBNo ROA
2801:1d:a004::/48LACNIC, RADBValid
2801:1d:a006::/48RADBNo ROA
2801:1d:a007::/48RADBNo ROA
2801:1d:a008::/48RADBNo ROA
2801:1d:a009::/48RADBNo ROA
2801:1d:a00a::/48RADBNo ROA
2801:1d:a00b::/48RADBNo ROA
2801:1d:a00c::/48RADBNo ROA
2801:1d:a00d::/48RADBNo ROA
2801:1d:a00e::/48RADBNo ROA
2801:1d:a00f::/48RADBNo 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.