Mirrors

Progress Linux is distributed all around the world using mirrors in order to provide users with better access to the archive and to reduce the load on the servers. All mirrors are automatically updated whenever there are updates to the archive-master.

CDN with GeoIP (default)

Progress Linux by default uses GeoIP to select the geographically closest server. All primary and secondary mirrors are participating in this mechanism.

Location Site Content Protocols
cdn.archive.progress-linux.org packages images HTTP HTTPS

Primary Mirrors

A primary mirror contains both the package archive and the images archive, supports all protocols (http, https, ftp, and rsync), and is operated by the Progress Linux association.

Location Site Content Protocols
Zurich, Switzerland1 archive.progress-linux.org packages images HTTP HTTPS FTP RSYNC
Paris, France (ready endy of 2014-02) fr.archive.progress-linux.org packages images HTTP HTTPS FTP RSYNC
Tel Aviv, Isreal (ready end of 2014-02) il.archive.progress-linux.org packages images HTTP HTTPS FTP RSYNC
Singapore sg.archive.progress-linux.org packages images HTTP HTTPS FTP RSYNC
London, United Kingdom uk.archive.progress-linux.org packages images HTTP HTTPS FTP RSYNC
Seattle, USA us.archive.progress-linux.org packages images HTTP HTTPS FTP RSYNC

Secondary Mirrors

A secondary mirror contains at least the package archive, supports most of the protocols (at least http; and any or none of https, ftp, and rsync), and is operated by volunteers.

Please contact System Administration if you want to operate a public secondary mirror with push mirroring.

Location Site Content Protocols
Beijing, China mirrors.ustc.edu.cn progress progress-images HTTP FTP RSYNC

1 The main server is used as a fallback whenever there is no better local mirror available. Note that the main server does not get updates any faster from the archive-master as any other mirror.