Network · data from 2026-11-12
AS27893 AS27893 - Universidad de Carabobo
Registry name: AS27893 - Universidad de Carabobo, VE · not in PeeringDB
22IPv4 routes
95.5% RPKI valid · 4.5% with a route object
0IPv6 routes
1RPKI invalid
1 origin · 0 maxLength
0No ROA
21 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
1Route objects not announced
registered with origin AS27893, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS27893, 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.
| 150.186.33.0/24 | Invalid: origin | None | 69 10% |
| 190.170.67.0/24 | Valid | Nonecovered by 190.170.64.0/18 | 670 100% |
| 190.170.117.0/24 | Valid | Nonecovered by 190.170.64.0/18 | 670 100% |
| 190.170.118.0/23 | Valid | Nonecovered by 190.170.64.0/18 | 670 100% |
| 190.170.120.0/24 | Valid | Nonecovered by 190.170.64.0/18 | 670 100% |
| 190.170.122.0/23 | Valid | Nonecovered by 190.170.64.0/18 | 670 100% |
| 190.170.124.0/24 | Valid | Nonecovered by 190.170.64.0/18 | 670 100% |
| 190.170.126.0/24 | Valid | Nonecovered by 190.170.64.0/18 | 670 100% |
| 190.170.76.0/22 | Valid | Nonecovered by 190.170.64.0/18 | 669 99% |
| 190.170.80.0/23 | Valid | Nonecovered by 190.170.64.0/18 | 669 99% |
| 190.170.88.0/21 | Valid | Nonecovered by 190.170.64.0/18 | 664 99% |
| 190.170.96.0/20 | Valid | Nonecovered by 190.170.64.0/18 | 664 99% |
| 190.170.68.0/22 | Valid | Nonecovered by 190.170.64.0/18 | 662 98% |
| 190.170.72.0/22 | Valid | Nonecovered by 190.170.64.0/18 | 662 98% |
| 190.170.82.0/23 | Valid | Nonecovered by 190.170.64.0/18 | 662 98% |
| 190.170.84.0/22 | Valid | Nonecovered by 190.170.64.0/18 | 662 98% |
| 190.170.112.0/22 | Valid | Nonecovered by 190.170.64.0/18 | 662 98% |
| 190.170.116.0/24 | Valid | Nonecovered by 190.170.64.0/18 | 662 98% |
| 190.170.121.0/24 | Valid | Nonecovered by 190.170.64.0/18 | 662 98% |
| 190.170.125.0/24 | Valid | Nonecovered by 190.170.64.0/18 | 662 98% |
| 190.170.127.0/24 | Valid | Nonecovered by 190.170.64.0/18 | 662 98% |
| 190.170.64.0/18 | Valid | RIR databaseLACNIC, RADB | 673 100% |
AS-SET
AS27893 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 23 are in fix.csv.
- ROA: origin1
- Route object: none21
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 150.186.33.0/24 | ROAs covering it name AS17287, AS20312, AS27807, not AS27893. If AS27893 should announce it, add a ROA for AS27893. |
| Route object: none | 150.186.33.0/24 | No route object for it. Add a route object with origin AS27893 in the RIR database for the space. |
| Route object: none | 190.170.67.0/24 | No route object for it. A route object for 190.170.64.0/18 with origin AS27893 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27893 in the RIR database for the space. |
| Route object: none | 190.170.117.0/24 | No route object for it. A route object for 190.170.64.0/18 with origin AS27893 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27893 in the RIR database for the space. |
| Route object: none | 190.170.118.0/23 | No route object for it. A route object for 190.170.64.0/18 with origin AS27893 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27893 in the RIR database for the space. |
| Route object: none | 190.170.120.0/24 | No route object for it. A route object for 190.170.64.0/18 with origin AS27893 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27893 in the RIR database for the space. |
| Route object: none | 190.170.122.0/23 | No route object for it. A route object for 190.170.64.0/18 with origin AS27893 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27893 in the RIR database for the space. |
| Route object: none | 190.170.124.0/24 | No route object for it. A route object for 190.170.64.0/18 with origin AS27893 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27893 in the RIR database for the space. |
| Route object: none | 190.170.126.0/24 | No route object for it. A route object for 190.170.64.0/18 with origin AS27893 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27893 in the RIR database for the space. |
| Route object: none | 190.170.76.0/22 | No route object for it. A route object for 190.170.64.0/18 with origin AS27893 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27893 in the RIR database for the space. |
| Route object: none | 190.170.80.0/23 | No route object for it. A route object for 190.170.64.0/18 with origin AS27893 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27893 in the RIR database for the space. |
| Route object: none | 190.170.88.0/21 | No route object for it. A route object for 190.170.64.0/18 with origin AS27893 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27893 in the RIR database for the space. |
| Route object: none | 190.170.96.0/20 | No route object for it. A route object for 190.170.64.0/18 with origin AS27893 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27893 in the RIR database for the space. |
| Route object: none | 190.170.68.0/22 | No route object for it. A route object for 190.170.64.0/18 with origin AS27893 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27893 in the RIR database for the space. |
| Route object: none | 190.170.72.0/22 | No route object for it. A route object for 190.170.64.0/18 with origin AS27893 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27893 in the RIR database for the space. |
| Route object: none | 190.170.82.0/23 | No route object for it. A route object for 190.170.64.0/18 with origin AS27893 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27893 in the RIR database for the space. |
| Route object: none | 190.170.84.0/22 | No route object for it. A route object for 190.170.64.0/18 with origin AS27893 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27893 in the RIR database for the space. |
| Route object: none | 190.170.112.0/22 | No route object for it. A route object for 190.170.64.0/18 with origin AS27893 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27893 in the RIR database for the space. |
| Route object: none | 190.170.116.0/24 | No route object for it. A route object for 190.170.64.0/18 with origin AS27893 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27893 in the RIR database for the space. |
| Route object: none | 190.170.121.0/24 | No route object for it. A route object for 190.170.64.0/18 with origin AS27893 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27893 in the RIR database for the space. |
| Route object: none | 190.170.125.0/24 | No route object for it. A route object for 190.170.64.0/18 with origin AS27893 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27893 in the RIR database for the space. |
| Route object: none | 190.170.127.0/24 | No route object for it. A route object for 190.170.64.0/18 with origin AS27893 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27893 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS27893 whose prefix no peer sees AS27893 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2800:a030::/32 | LACNIC | Valid |
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.