bgpreport

Network · data from 2026-11-12

AS274162 AS274162 - CABLENORTV S.A.C. (CABLE VISION)

Registry name: AS274162 - CABLENORTV S.A.C. (CABLE VISION), PE · not in PeeringDB

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

Announced routes

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

45.4.93.0/24 Valid Nonecovered by 45.4.92.0/23 672 100% 67
45.4.92.0/24 Valid Other IRR onlyRADB 668 99% 67
45.4.92.0/23 Valid RIR databaseLACNIC 672 100% 67

AS-SET

AS274162 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.

  • Route object: none1
  • Route object: RIR1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none45.4.93.0/24No route object for it. A route object for 45.4.92.0/23 with origin AS274162 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274162 in the RIR database for the space.672 of 673
Route object: RIR45.4.92.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673

Route objects not announced

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

45.4.92.0/22RADBNo ROA
45.4.94.0/24LACNIC, RADBValid
45.4.95.0/24LACNICValid
2803:79d0::/32RADBNo ROA

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.