bgpreport

Network · data from 2026-11-12

AS272992 AS272992 - CABLE & TV YOPAL S.A.S (INTERNET INALAMBRICO)

Registry name: AS272992 - CABLE & TV YOPAL S.A.S (INTERNET INALAMBRICO), CO · not in PeeringDB

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

Announced routes

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

131.221.43.0/24 Valid Other origin onlycovered by 131.221.40.0/22 671 100% 66
2803:8b80:111::/48 Valid Nonecovered by 2803:8b80::/32 634 100% 67
2803:8b80:104::/48 Valid Nonecovered by 2803:8b80::/32 633 100% 69
2803:8b80:113::/48 Valid Nonecovered by 2803:8b80::/32 632 99% 68
131.221.40.0/24 Valid Other IRR onlyRADB 672 100% 66
131.221.41.0/24 Valid Other IRR onlyRADB 672 100% 66
131.221.42.0/24 Valid Other IRR onlyRADB 671 100% 66
2803:8b80:100::/48 Valid Other IRR onlyRADB 633 100% 68
2803:8b80:102::/48 Valid Other IRR onlyRADB 633 100% 68
2803:8b80:108::/48 Valid Other IRR onlyRADB 633 100% 68
2803:8b80:101::/48 Valid Other IRR onlyRADB 632 99% 68
2803:8b80:103::/48 Valid Other IRR onlyRADB 632 99% 68

AS-SET

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

  • Route object: none4
  • Route object: RIR8
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none131.221.43.0/24Route objects for it name AS262186. A route object for 131.221.40.0/22 with origin AS272992 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272992 in the RIR database for the space.671 of 673
Route object: none2803:8b80:111::/48No route object for it. A route object for 2803:8b80::/32 with origin AS272992 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272992 in the RIR database for the space.634 of 636
Route object: none2803:8b80:104::/48No route object for it. A route object for 2803:8b80::/32 with origin AS272992 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272992 in the RIR database for the space.633 of 636
Route object: none2803:8b80:113::/48No route object for it. A route object for 2803:8b80::/32 with origin AS272992 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272992 in the RIR database for the space.632 of 636
Route object: RIR131.221.40.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR131.221.41.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR131.221.42.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2803:8b80:100::/48Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2803:8b80:102::/48Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2803:8b80:108::/48Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2803:8b80:101::/48Route object only in RADB. Add it in the RIR database for the space.632 of 636
Route object: RIR2803:8b80:103::/48Route object only in RADB. Add it in the RIR database for the space.632 of 636

Route objects not announced

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

131.221.40.0/22LACNIC, RADBValid
2803:8b80::/32LACNIC, RADBValid

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.