What IP are you getting back, I get 216.51.236.66 looks fine from here.
1 ge-10-ebr01.orlnd-stt.flhsi.com (208.90.219.1) 0.162 ms 0.095 ms 0.063 ms
2 fa0-3.na11.b001333-0.mco01.atlas.cogentco.com (38.104.88.65) 2.736 ms 1.180 ms 1.292 ms
3 te3-1.3501.ccr01.mco01.atlas.cogentco.com (66.250.12.61) 0.583 ms 0.698 ms 0.594 ms
4 te3-2.ccr01.tpa01.atlas.cogentco.com (154.54.29.213) 2.632 ms 2.600 ms 2.617 ms
5 38.104.150.70 (38.104.150.70) 4.526 ms 4.542 ms 4.622 ms
6 tpa.core.hivelocity.net (69.46.31.110) 3.187 ms 3.716 ms 4.262 ms
7 206.51.236.66 (206.51.236.66) 2.666 ms !X 2.626 ms !X 2.695 ms !X
On 3/17/2011 5:51 PM, Billy Vierra wrote:Just tried to resync our CentOS Mirror, however us-msync.centos.org is not responding to ping and is timing out in SSH... any issues?
-- Billy Vierra Senior System Engineer NetDNA™ The Science of Acceleration™ Email: bvierra@netdna.com P: 1.877.5-NETDNA (563-8362) ext 260 F: 1.323.417.4995 Follow Us Web: http://www.NetDNA.com Blog: http://blog.netdna.com Twitter @NetDNACDN_______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org http://lists.centos.org/mailman/listinfo/centos-mirror_______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org http://lists.centos.org/mailman/listinfo/centos-mirror
-- Billy Vierra Senior System Engineer NetDNA™ The Science of Acceleration™ Email: bvierra@netdna.com P: 1.877.5-NETDNA (563-8362) ext 260 F: 1.323.417.4995 Follow Us Web: http://www.NetDNA.com Blog: http://blog.netdna.com Twitter @NetDNACDN