Network · data from 2026-11-12
AS10293 AS10293 - CANTV Servicios, Venezuela
Registry name: AS10293 - CANTV Servicios, Venezuela, VE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS10293, 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:1058:31::/48 | Invalid: origin | None | 19 3%low visibility |
| 2800:1058:32::/48 | Invalid: origin | None | 19 3%low visibility |
| 200.84.128.0/24 | Valid | Nonecovered by 200.84.128.0/19 | 671 100% |
| 200.84.129.0/24 | Valid | Nonecovered by 200.84.128.0/19 | 671 100% |
| 200.84.130.0/24 | Valid | Nonecovered by 200.84.128.0/19 | 670 100% |
| 200.84.132.0/24 | Valid | Nonecovered by 200.84.128.0/19 | 670 100% |
| 200.84.133.0/24 | Valid | Nonecovered by 200.84.128.0/19 | 670 100% |
AS-SET
AS10293 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 10 are in fix.csv.
- ROA: origin2
- Route object: none7
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2800:1058:31::/48 | ROAs covering it name AS8048, not AS10293. If AS10293 should announce it, add a ROA for AS10293. |
| Route object: none | 2800:1058:31::/48 | No route object for it. Add a route object with origin AS10293 in the RIR database for the space. |
| ROA: origin | 2800:1058:32::/48 | ROAs covering it name AS8048, not AS10293. If AS10293 should announce it, add a ROA for AS10293. |
| Route object: none | 2800:1058:32::/48 | No route object for it. Add a route object with origin AS10293 in the RIR database for the space. |
| Route object: none | 200.84.128.0/24 | No route object for it. A route object for 200.84.128.0/19 with origin AS10293 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10293 in the RIR database for the space. |
| Route object: none | 200.84.129.0/24 | No route object for it. A route object for 200.84.128.0/19 with origin AS10293 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10293 in the RIR database for the space. |
| Route object: none | 200.84.130.0/24 | No route object for it. A route object for 200.84.128.0/19 with origin AS10293 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10293 in the RIR database for the space. |
| Route object: none | 200.84.132.0/24 | No route object for it. A route object for 200.84.128.0/19 with origin AS10293 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10293 in the RIR database for the space. |
| Route object: none | 200.84.133.0/24 | No route object for it. A route object for 200.84.128.0/19 with origin AS10293 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10293 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS10293 whose prefix no peer sees AS10293 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 200.84.128.0/19 | 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.