Network · data from 2026-11-12

AS273203 CABLE PAR, C.A.

Registry name: AS273203 - CABLE PAR, C.A., VE · PeeringDB

7IPv4 routes 100.0% RPKI valid · 71.4% with a route object

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 2 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS273203, seen from no peer

Announced routes

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


38.224.158.0/23	Valid	Nonecovered by 38.224.156.0/22	671 100%	67
38.224.156.0/23	Valid	Nonecovered by 38.224.156.0/22	664 99%	67
38.224.157.0/24	Valid	Other IRR onlyRADB	672 100%	67
38.224.158.0/24	Valid	Other IRR onlyRADB	666 99%	67
38.224.159.0/24	Valid	Other IRR onlyRADB	666 99%	67
38.224.156.0/24	Valid	Other IRR onlyRADB	664 99%	67
38.224.156.0/22	Valid	RIR databaseARIN	672 100%	67
2803:d4d0::/32	Valid	RIR databaseLACNIC, RADB	635 100%	67

AS-SET

AS273203's PeeringDB record names no 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.

Route object: none2
Route object: RIR4

Change	Prefix or set	Detail	Full-table peers
Route object: none	38.224.158.0/23	No route object for it. A route object for 38.224.156.0/22 with origin AS273203 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273203 in the RIR database for the space.	671 of 673
Route object: none	38.224.156.0/23	No route object for it. A route object for 38.224.156.0/22 with origin AS273203 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273203 in the RIR database for the space.	664 of 673
Route object: RIR	38.224.157.0/24	Route object only in RADB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	38.224.158.0/24	Route object only in RADB. Add it in the RIR database for the space.	666 of 673
Route object: RIR	38.224.159.0/24	Route object only in RADB. Add it in the RIR database for the space.	666 of 673
Route object: RIR	38.224.156.0/24	Route object only in RADB. Add it in the RIR database for the space.	664 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

38.224.158.0/23

No route object for it. A route object for 38.224.156.0/22 with origin AS273203 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273203 in the RIR database for the space.

671 of 673

Route object: none

38.224.156.0/23

664 of 673

Route object: RIR

38.224.157.0/24

Route object only in RADB. Add it in the RIR database for the space.

672 of 673

Route object: RIR

38.224.158.0/24

Route object only in RADB. Add it in the RIR database for the space.

666 of 673

Route object: RIR

38.224.159.0/24

Route object only in RADB. Add it in the RIR database for the space.

666 of 673

Route object: RIR

38.224.156.0/24

Route object only in RADB. Add it in the RIR database for the space.

664 of 673

Route objects not announced

Every route object with origin AS273203 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.