bgpreport

Network · data from 2026-11-12

AS264653 AS264653 - Universidad Catolica de Oriente

Registry name: AS264653 - Universidad Catolica de Oriente, CO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264653, 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.
2800:b70:46::/48 Invalid: origin None 23 4%low visibility 11
200.9.158.0/24 No ROA Other IRR onlyRADB 671 100% 67
200.9.159.0/24 No ROA Other IRR onlyRADB 671 100% 67

AS-SET

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

  • ROA: origin1
  • ROA: none2
  • Route object: none1
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: origin2800:b70:46::/48ROAs covering it name AS262191, not AS264653. If AS264653 should announce it, add a ROA for AS264653.23 of 636
Route object: none2800:b70:46::/48No route object for it. Add a route object with origin AS264653 in the RIR database for the space.23 of 636
ROA: none200.9.158.0/24No ROA covers it. Add a ROA for AS264653, maxLength 24.671 of 673
Route object: RIR200.9.158.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none200.9.159.0/24No ROA covers it. Add a ROA for AS264653, maxLength 24.671 of 673
Route object: RIR200.9.159.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

Every route object with origin AS264653 is announced.

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.