There is a new mirror setup at http://mirror.voxitas.com/centos
Connections are accepted on HTTP.
We are connected via Level3 and Verizon on Gig-E. Our customers will be able to download at 100Mbit and people accessing via the internet will be limited to 45Mbit.
We are synching from a Tier1 source twice daily.
The mirror is provided by Voxitas (www.voxitas.com) and the contact is Jonathan Creasy jcreasy(a)voxitas.com
I plan to add RSYNC access and hopefully increase the bandwidth cap soon.
Liquid Web, Inc. (http://www.liquidweb.com/) has set up a new public CentOS
mirror in order to give back to the project from which we have benefited so
greatly. The mirror is located at the following location.
http://mirrors.liquidweb.com/CentOS/
All architectures and releases are currently being mirrored, with
synchronization taking place four times per day. We currently have approximately
5 GBit of Tier 1 upstream bandwidth via Savvis, AT&T, Layer3, and MCI. The
mirror, however, will be limited during peak times (10am-6pm US Eastern time) to
10Mbit, and 75Mbit during off-peak times. I will update the list if these
restrictions change.
Thanks to all those that make CentOS happen!
--
Mike Neir
Liquid Web, Inc.
Senior Systems Administrator
Project Development
We have available bandwidth that we would like to donate to centos.org. The
mirror is synched at http://mirror.raystedman.org/centos via HTTP. We
mirrored all releases and architectures with updates performed four times
per day. This server is attached via two 100 Mbit/Sec connections into a
100 Gbit/Sec network infrastructure with multiple tier 1 providers.
We want to thank centos.org for taking the legacy of open systems software
to the next level with the CentOS Distribution.
Greg Sims
http://www.raystedman.org/
Hello,
I regret to inform that I will be decommissioning the following mirror:
ftp://mirror.daemonbox.net
Unfortunately, my company is doing away with employee colocation and, as a
result, I will have to remove my mirror server. I will keep this mirror up
for an additional week or so just so the few projects I've been mirroring
have time to remove the links from their sites.
Please let me know if you have any questions. Thanks.
-David
--
[root@fbsd ~]# fortune
Happiness is just an illusion, filled with sadness and confusion.
Hi,
Good day!
We would like to express our desire to mirror CentOS. Here are the
necessary information:
relevant URL's (ftp/http/rsync/?): http://mirror.psigrid.gov.ph/centos
how often: at least 2x a day
city/state/country: Quezon City, Philippines
bandwidth cap: 155Mbps
name: Advanced Science and Technology Institute
link to the sponsoring organization: http://www.asti.dost.gov.ph
Thank you very much.
--
/**
* @author Rey Vincent P. Babilonia
* @number +63 2 426 9760 local 1302
* @pgp 0x383454CF <at> pgp.mit.edu
* @project Philippine Bioinformatics Solutions
* @program Philippine e-Science Grid
* @division Research and Development Division
* @agency Advanced Science and Technology Institute
* @url http://www.psigrid.gov.ph
*/
Hi all,
Per the mirroring HowTo document (and with the prodding of tru_tru on
#centos) I've joined the list and would like to announce the
availability of a new mirror on the University of Oregon campus.
Here's the relevant information:
URL: http://mirror.nic.uoregon.edu/centos/
Interval: Every 6 hours at 16 minutes after the hour (16 */6)
City: Eugene
State: Oregon
Country: US
Versions: 4 5
Architectures: All
Bandwidth: Gigabit, unlimited (may be limited if it becomes an issue)
Organization: University of Oregon (http://www.uoregon.edu)
Sponsor: UO Neuroinformatics Center (http://www.nic.uoregon.edu)
--
Brandon Davidson
Systems Administrator
Neuroinformatics Center
University of Oregon
brandond(a)uoregon.edu
(541) 346-2417
Hey everyone,
Just a quick heads up since it seems to have come to be an issue -
Kernel.org is down one of the mirror machines due to an array trying to
get rebuilt after a failed drive. If your using kernel.org for syncing
expect delays, slowdowns and the inevitable
$ rsync mirrors.kernel.org::
rsync: connection unexpectedly closed (0 bytes received so far)
[receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(463)
[receiver=2.6.8]
which means we either are serving as many connections as we allow for
(I've upped it some) or we've exceeded our load threshold and are
denying new connections until the load drops.
We should have this settled soon - it's just taking us longer than we
expected.
- John 'Warthog9' Hawley