bgpreport

Network · data from 2026-11-12

AS27892 AS27892 - Universidad del Zulia

Registry name: AS27892 - Universidad del Zulia, VE · not in PeeringDB

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

Announced routes

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

190.170.0.0/21 No ROA Nonecovered by 190.170.0.0/18 1 0%low visibility 1
190.170.8.0/21 No ROA Nonecovered by 190.170.0.0/18 1 0%low visibility 1
190.170.16.0/21 No ROA Nonecovered by 190.170.0.0/18 1 0%low visibility 1
190.170.24.0/21 No ROA Nonecovered by 190.170.0.0/18 1 0%low visibility 1
190.170.32.0/21 No ROA Nonecovered by 190.170.0.0/18 1 0%low visibility 1
190.170.0.0/18 No ROA Other IRR onlyRADB 670 100% 68
150.185.222.0/24 Valid None 673 100% 67
150.185.192.0/24 Valid None 2 0%low visibility 2
190.170.0.0/22 Valid RIR databaseLACNIC 670 100% 68
190.170.2.0/23 Valid RIR databaseLACNIC 1 0%low visibility 1

AS-SET

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

  • ROA: none6
  • Route object: none7
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none190.170.0.0/21No ROA covers it. Add a ROA for AS27892, maxLength 21.1 of 673
Route object: none190.170.0.0/21No route object for it. A route object for 190.170.0.0/18 with origin AS27892 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27892 in the RIR database for the space.1 of 673
ROA: none190.170.8.0/21No ROA covers it. Add a ROA for AS27892, maxLength 21.1 of 673
Route object: none190.170.8.0/21No route object for it. A route object for 190.170.0.0/18 with origin AS27892 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27892 in the RIR database for the space.1 of 673
ROA: none190.170.16.0/21No ROA covers it. Add a ROA for AS27892, maxLength 21.1 of 673
Route object: none190.170.16.0/21No route object for it. A route object for 190.170.0.0/18 with origin AS27892 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27892 in the RIR database for the space.1 of 673
ROA: none190.170.24.0/21No ROA covers it. Add a ROA for AS27892, maxLength 21.1 of 673
Route object: none190.170.24.0/21No route object for it. A route object for 190.170.0.0/18 with origin AS27892 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27892 in the RIR database for the space.1 of 673
ROA: none190.170.32.0/21No ROA covers it. Add a ROA for AS27892, maxLength 21.1 of 673
Route object: none190.170.32.0/21No route object for it. A route object for 190.170.0.0/18 with origin AS27892 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27892 in the RIR database for the space.1 of 673
ROA: none190.170.0.0/18No ROA covers it. Add a ROA for AS27892, maxLength 18.670 of 673
Route object: RIR190.170.0.0/18Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: none150.185.222.0/24No route object for it. Add a route object with origin AS27892 in the RIR database for the space.673 of 673
Route object: none150.185.192.0/24No route object for it. Add a route object with origin AS27892 in the RIR database for the space.2 of 673

Route objects not announced

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

2800:a028::/32LACNICValid

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.