You can disregard that one. There is now a redirect HTTP 301 from latest to the relevant version, therefore, for example:
# curl -I -v http://installrepo.origin.kaltura.org/releases/latest/RPMS/x86_64/repodata/repomd.xml
* About to connect() to installrepo.origin.kaltura.org port 80 (#0)
* Trying 216.200.17.80... connected
* Connected to installrepo.origin.kaltura.org (216.200.17.80) port 80 (#0)
HEAD /releases/latest/RPMS/x86_64/repodata/repomd.xml HTTP/1.1
User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2
Host: installrepo.origin.kaltura.org
Accept: /< HTTP/1.1 301 Moved Permanently
HTTP/1.1 301 Moved Permanently
< Date: Tue, 01 Mar 2016 16:33:44 GMT
Date: Tue, 01 Mar 2016 16:33:44 GMT
< Server: Apache/2.2.15 (CentOS)
Server: Apache/2.2.15 (CentOS)
< Location: http://installrepo.origin.kaltura.org/repo/releases/11.9.0/RPMS/x86_64/repodata/repomd.xml
Location: http://installrepo.origin.kaltura.org/repo/releases/11.9.0/RPMS/x86_64/repodata/repomd.xml
If you're having issues, it is most probably, as usual, because the CDN edges did not yet update, this redirect, as opposed to a symlink, was actually made in an attempt to see if it will make the edges update faster but thus far, it does not seem to matter.
At any rate, just change /etc/yum.repos.d/kaltura.repo to use installrepo.origin.kaltura.org instead of installrepo.kaltura.org and it should work correctly. By tomorrow all edges will update and you can change back.
Thanks,