bgpreport

Network · data from 2026-11-12

AS266737 AS266737 - UNIVERSIDAD DEL CAUCA

Registry name: AS266737 - UNIVERSIDAD DEL CAUCA, CO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266737, 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.
45.231.184.0/22 Valid Other IRR onlyRADB 672 100% 67
2801:12:7000::/48 Valid Other IRR onlyRADB 632 99% 69
38.211.70.0/24 Valid RIR databaseARIN, RADB 673 100% 67
38.211.71.0/24 Valid RIR databaseARIN, RADB 673 100% 67
177.73.152.0/24 Valid RIR databaseLACNIC 670 100% 67
177.73.154.0/24 Valid RIR databaseLACNIC 670 100% 67
2803:b5a0:400c::/48 Valid RIR databaseLACNIC, RADB 632 99% 69
2803:1780::/48 Valid RIR databaseLACNIC 631 99% 69

AS-SET

AS266737 isn't in PeeringDB, where networks name their 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 4 are in fix.csv.

  • Route object: RIR2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: RIR45.231.184.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2801:12:7000::/48Route object only in RADB. Add it in the RIR database for the space.632 of 636

Route objects not announced

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

38.211.70.0/23ARINValid
45.231.184.0/23RADBValid

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.