bgpreport

Network · data from 2026-11-12

AS272987 AS272987 - CABLE CAUCA COMUNICACIONES S.A.S.

Registry name: AS272987 - CABLE CAUCA COMUNICACIONES S.A.S., CO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272987, 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.53.0/24 No ROA Nonecovered by 38.224.52.0/22 672 100% 67
38.224.54.0/24 No ROA Nonecovered by 38.224.52.0/22 672 100% 67
38.224.55.0/24 No ROA Nonecovered by 38.224.52.0/22 669 99% 67
38.224.52.0/22 No ROA Other IRR onlyRADB 670 100% 67
38.224.52.0/24 No ROA Other IRR onlyRADB 26 4%low visibility 14
2803:d90:f000::/36 Valid Nonecovered by 2803:d90::/32 635 100% 68
2803:d90::/32 Valid RIR databaseLACNIC, RADB 634 100% 69

AS-SET

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

  • ROA: none5
  • Route object: none4
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none38.224.53.0/24No ROA covers it. Add a ROA for AS272987, maxLength 24.672 of 673
Route object: none38.224.53.0/24No route object for it. A route object for 38.224.52.0/22 with origin AS272987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272987 in the RIR database for the space.672 of 673
ROA: none38.224.54.0/24No ROA covers it. Add a ROA for AS272987, maxLength 24.672 of 673
Route object: none38.224.54.0/24No route object for it. A route object for 38.224.52.0/22 with origin AS272987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272987 in the RIR database for the space.672 of 673
ROA: none38.224.55.0/24No ROA covers it. Add a ROA for AS272987, maxLength 24.669 of 673
Route object: none38.224.55.0/24No route object for it. A route object for 38.224.52.0/22 with origin AS272987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272987 in the RIR database for the space.669 of 673
ROA: none38.224.52.0/22No ROA covers it. Add a ROA for AS272987, maxLength 22.670 of 673
Route object: RIR38.224.52.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.224.52.0/24No ROA covers it. Add a ROA for AS272987, maxLength 24.26 of 673
Route object: RIR38.224.52.0/24Route object only in RADB. Add it in the RIR database for the space.26 of 673
Route object: none2803:d90:f000::/36No route object for it. A route object for 2803:d90::/32 with origin AS272987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272987 in the RIR database for the space.635 of 636

Route objects not announced

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