bgpreport

Network · data from 2026-11-12

AS265641 CIX BROADBAND

Registry name: AS265641 - TELECOMUNICACIONES ROCARLI C.A (CIX BROADBAND), VE · PeeringDB

10IPv4 routes 100.0% RPKI valid · 80.0% 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
1Route objects not announced registered with origin AS265641, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS265641, 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.159.124.0/24 Valid Nonecovered by 38.159.124.0/22 671 100% 67
38.159.125.0/24 Valid Nonecovered by 38.159.124.0/22 671 100% 67
38.159.127.0/24 Valid Other IRR onlyRADB 672 100% 67
170.254.174.0/24 Valid Other IRR onlyALTDB, RADB 672 100% 67
170.254.172.0/24 Valid Other IRR onlyALTDB 669 99% 67
170.254.173.0/24 Valid Other IRR onlyALTDB 669 99% 67
170.254.175.0/24 Valid Other IRR onlyALTDB 669 99% 67
38.159.124.0/22 Valid RIR databaseARIN, RADB 672 100% 67
170.254.172.0/22 Valid RIR databaseALTDB, LACNIC, RADB 672 100% 67
170.247.215.0/24 Valid RIR databaseLACNIC, RADB 668 99% 67
2803:6f40::/32 Valid RIR databaseALTDB, LACNIC, RADB 631 99% 68

AS-SET

PeeringDB's irr_as_set for AS265641: AS265641:AS-ALL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS265641 isn't in the set, or no route object for AS265641 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS265641 in itNot covered
AS265641:AS-ALL ALTDB 2114 Yes 0

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

  • Route object: none2
  • Route object: RIR5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none38.159.124.0/24No route object for it. A route object for 38.159.124.0/22 with origin AS265641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265641 in the RIR database for the space.671 of 673
Route object: none38.159.125.0/24No route object for it. A route object for 38.159.124.0/22 with origin AS265641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265641 in the RIR database for the space.671 of 673
Route object: RIR38.159.127.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR170.254.174.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR170.254.172.0/24Route object only in ALTDB. Add it in the RIR database for the space.669 of 673
Route object: RIR170.254.173.0/24Route object only in ALTDB. Add it in the RIR database for the space.669 of 673
Route object: RIR170.254.175.0/24Route object only in ALTDB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

2803:6f40:2::/48LACNICValid

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.